Steve Galloway | Comstat | Ruthin, North Wales

Index of articles

by Steve Galloway | Aug 12, 2026

Click open the Index headers below to browse FAQ

Our support articles address the most common issues we deal with “in the field” about Windows, Microsoft 365 Business, web server support, and web design. Click open the accordion sections below to look for self-serve help. Often, issues rely on a knowledge of IT concepts and language. Also, Microsoft, cPanel, and other software houses featured in these articles often update practice notes and procedures without notice. We review our pages regulalry, however you are advised to contact us for further help about these articles especially concerning issues around sovereign account identity and Multifactor Authentication (MFA).

Microsoft Windows 11

Microsoft 365 setup, licensing and user management

Microsoft 365, Exchange Online and Outlook

Microsoft 365 configuration and user tips and tricks

The following articles can be found using <Search> or scrolling through our list of articles. Procedures may have changed since and therefore this content is either being eidted or deprecated. So, although we are editing this content, you might still find useful information to help with issues.

– Exchange Online – room and equipment resources
– Reset Office 365 password expiration policy
– Exchange Email – EOP antivirus/spam
– Exchange Online Protection – EOP
– Microsoft 365 Exchange Email – data leakage & loss protection
– Microsoft ActiveSync

cPanel - web server | email |DNS

cPanel - Sitejet web design software

Microsoft OneDrive DLL Error: How to Fix a Corrupted DLL Using a OneDrive Reset

by Steve Galloway | Aug 12, 2026

Microsoft OneDrive DLL Error: How to Fix a Corrupted DLL Using a OneDrive Reset

A client recently reported a startup error on a Windows 11 laptop. The message referenced a corrupted DLL file within the Microsoft OneDrive installation directory:

C:\Users\*user-name*\AppData\Local\Microsoft\OneDrive\Codecs\8.1.2\acutil-60.dll

The error stated that the DLL was either not designed to run on Windows or contained an error. Following additional restart attempts, the client believed Windows itself had become unusable.

Seemingly terminal error messages of this kind are not usually a fatal error message concerning Windows operating system or hardware.

At first glance, this appeared to be a serious operating system failure. However, investigation showed that the issue was most likely a corrupted OneDrive component rather than a broader Windows or hardware problem.

Click open the headers below to learn how to interpret a DLL error message using this case study for repairing a corrupted OneDrive DLL. Support options are available for professional assistance. You can return to our Index of Articles by clicking here.

Understanding the OneDrive DLL Error

DLL files, or Dynamic Link Libraries, contain code and resources used by Windows applications. If one of these files becomes corrupted, Windows may generate a Bad Image error during startup or when launching an application.

A corrupted DLL can occur for several reasons:

Interrupted software updates
File system corruption
Unexpected shutdowns
Third-party security software interference
Storage issues affecting application files

Although the error appeared severe, there was no immediate evidence that Windows itself was damaged.

First Rule: Identify the Application

When you receive a DLL error message, put concern to one side and first determine which application owns the file before taking further action.

In this case, the directory structure clearly indicated Microsoft OneDrive:

C:\Users<username>\AppData\Local\Microsoft\OneDrive

This meant troubleshooting could focus on OneDrive rather than immediately considering a Windows rebuild or hardware replacement.

As a general rule, DLL files found after:

AppData\Local

usually belong to user-installed applications or application components rather than the operating system itself.

The Fix: Reset OneDrive

Microsoft includes a built-in reset mechanism for the OneDrive client.

Using Command prompt, or even by typing <run> in the Windows Search tool on the Windows task bar, this command, the following command can be performed.

%localappdata%\Microsoft\OneDrive\OneDrive.exe /reset

The easiest way to run this command is:

Press Windows + R
Paste the command
Press Enter

Enter Use Windows search to open the utility, and enter the code.

The command stops the OneDrive client, rebuilds local configuration files, clears cached information and restarts the synchronisation engine. Windows may take a minute to execute the reset stages, so we allowed a short while for the computer to process instructions. Depending on your instance of Windows, this command might need modifying. Contact us for help in this case.

In this case, the result was immediate. The client regained normal access to Windows, and the OneDrive DLL error disappeared. This strongly suggested that the underlying problem was a corrupted OneDrive component rather than a damaged Windows installation.

Additional Checks After Fixing the Error

Even when a DLL reset resolves the issue, it is important to verify that deeper corruption does not exist elsewhere.

Open an elevated Command Prompt (use Run in the first instance) and run:

sfc /scannow

System File Checker scans protected Windows files and replaces incorrect versions with known good copies.

If corruption is reported, run:

DISM /Online /Cleanup-Image /RestoreHealth

This command repairs the Windows component store used by System File Checker.

Check the Disk for Problems

Whenever a corrupted DLL is discovered, it is worth checking the storage device for underlying faults.

Run:

chkdsk C: /f

If prompted, schedule the scan for the next restart.

For a more comprehensive examination:

chkdsk C: /f /r

This scans for bad sectors and attempts recovery where possible.

Although the OneDrive reset resolved the immediate issue, disk diagnostics remain an important step because file corruption can sometimes be an early sign of storage problems.

Why This Works for Other Microsoft DLL Problems

This case involved OneDrive, but the same troubleshooting principles apply to many Microsoft applications including:

Outlook
Teams
OneNote
Microsoft 365 Apps
Edge
Windows components

When a DLL error references a file within an application’s own folder structure, a repair, reset or reinstall of that application is often more effective than making direct changes to the DLL itself.

Downloading replacement DLL files from third-party websites is strongly discouraged. These files may not match the installed software version and can introduce security risks.

Instead:

Identify the owning application.
Use the application’s repair or reset function.
Run SFC and DISM if required.
Perform a disk health check.
Reinstall the application only if the problem persists.

Summary

This case demonstrates that not every DLL error indicates a failing computer.

A startup error referencing a corrupted OneDrive DLL initially appeared to be a potentially serious Windows failure. In reality, resetting OneDrive reset restored normal operation within minutes.

For IT professionals and home users alike, the key lesson is straightforward: identify the application responsible for the DLL, use the application’s repair tools first, and then verify overall system health with SFC, DISM and CHKDSK.

In many cases, that approach resolves the issue without requiring a Windows reinstall, profile rebuild or hardware replacement.

Key Takeaway

If you encounter a OneDrive DLL Error, start by resetting OneDrive using:

%localappdata%\Microsoft\OneDrive\OneDrive.exe /reset

Then follow up with SFC, DISM and CHKDSK checks to confirm that the corruption was isolated and not part of a larger storage or operating system issue. This simple process can save hours of troubleshooting and quickly return a Windows PC to normal operation.

Comstat provides independent advice on business IT choices that reduce risk, protect continuity, and support long‑term growth. If you need help managhing email, please get in touch, or use our contact page to organize an appointment which suits your timetable. You can return to our Index of Articles by clicking here .

Microsoft Entra Passkeys: Why Microsoft Is Retiring SMS Authentication and What You Need to Do

by Steve Galloway | Aug 11, 2026

Why Microsoft Is Retiring SMS Authentication and What You Need to Do

Microsoft Entra Passkeys are being enforced for business users in ealry 2027. This significantly reinforces account security at a time when phishing attacks and malicious intrusion is mushromming. Microsoft-provided SMS and voice authentication for Microsoft Entra ID will retire on 1 February 2027, with passkeys becoming the preferred authentication method.

If you are a Micrsoft 365 tenancy owner you need to be ready for this change. For instance, business owners may need to help staff update their sign-in routine. Recently, some users who only consider themselves Microsoft account holders have received notifications about this as well. This has led to understandable confusion about who is affected and whether any action is required.

The good news is that the change is straightforward once you understand the difference between a Microsoft account and a Microsoft Entra tenant. Also, this article will help you understand how you can determine if you need to action anything if you do not believe you are affected by this.

Click open the headers below to learn more about how Microsoft Entra Passkeys to prepare for Microsoft’s new credential system. Support options are available for professional assistance. You can return to our Index of Articles by clicking here.

What Are Microsoft Entra Passkeys?

A passkey is a modern authentication method designed to replace traditional passwords and SMS verification codes.

Instead of receiving a text message or entering a password, users authenticate using a trusted device such as:

Windows Hello
Face recognition
Fingerprint authentication
A security key
A mobile device linked to the account

Microsoft Entra passkeys are classed as phishing-resistant authentication. This means they are far more difficult for attackers to steal, intercept, or misuse than passwords, voice verification, or SMS codes.

As cybercriminals increasingly rely on phishing campaigns, Microsoft and other major technology companies are moving towards authentication methods that do not depend on passwords or mobile text messages.

Why Is Microsoft Retiring SMS Authentication?

SMS authentication has served organisations well for many years, but it has several weaknesses.

Attackers can:

Trick users into revealing authentication codes
Conduct SIM-swap attacks
Intercept messages in some circumstances
Use social engineering to bypass protections

Passkeys solve many of these problems because authentication occurs directly between the device and Microsoft’s identity platform.

From Microsoft’s point of view, Microsoft Entra passkeys provide a much stronger security baseline for business and organisational accounts. The company is therefore encouraging all affected users to transition before the retirement date.

Who Is Affected?

If you manage a Microsoft 365 Business tenant, Microsoft Entra tenant, Azure subscription, or related cloud services, you should assume that this announcement applies to you.

Even if you already use Microsoft Entra Passkeys using Microsoft Authenticator, you might have some users who still rely on SMS-based multi-factor authentication (MFA). Often, this is because handsets are too old for tools like Microsoft Authenticator to operate on. Those users will need to migrate to a phishing-resistant authentication method before February 2027.

If you only use services such as:

Outlook.com
Hotmail
Xbox
OneDrive Personal
Microsoft 365 Personal
Microsoft 365 Family

you might not be affected.

However, there is an important exception.

Some people created Microsoft cloud services years ago and unknowingly obtained a Microsoft Entra tenant in the background. Microsoft may therefore send administrative notifications to accounts that appear to be ordinary Microsoft accounts.

How to Check If You Have a Microsoft Entra Tenant

If you receive one of these notifications and are unsure whether it applies to you, perform a simple test.

Visit the Microsoft Entra Admin Centre:

Option 1: No Access to a Tenant

If Microsoft reports that you do not have access to a tenant or administrative resources, the notification is unlikely to require any action.

In most cases, personal Microsoft account users can safely disregard the message.

Option 2: Access to a Tenant

If the portal opens and displays tenant information, directory details, or administrative options, Microsoft considers you to have responsibility for an Entra environment.

You should review your authentication methods before the retirement deadline.

Option 3: A Forgotten Trial or Subscription

It is surprisingly common to discover an old Azure trial, Microsoft 365 test tenant, or developer environment that was created years ago.

If one exists, determine whether it is still required. If it remains in use, the transition to Microsoft Entra passkeys should be planned.

What Should You Do?

If you own a Microsoft 365 tenancy, or if your email addressis implicated in Microsoft services listed above which list you in Microsoft Entra, you should begin preparations well before 2027. Recommended actions include:

Review authentication methods currently in use.
Identify users relying solely on SMS or voice authentication.
Check that mobile devices are able to install Microsoft Authenticator app
Enable Microsoft Entra passkeys where appropriate.
Encourage Windows Hello or FIDO2 security key adoption.
Communicate upcoming changes to users.
Test authentication workflows before enforcement begins.

Early adoption reduces the risk of support calls and avoids users being surprised by registration prompts later.

Benefits Beyond Compliance

The move to Microsoft Entra passkeys is not simply another administrative requirement. Identity theft is increasing sinificantly and improved security is not just for business users. In fact, if you are a consumer user and you believe your security is satisfactory even with SMS Authentication, you are in a high risk target group.

Imagine waking up one morning to discover that a malicious party has appropriated control of your online retail and banking accounts, and that they are using your identity to buy expensive luxury watches at auction houses for which payment is intended to be drawn against your savings? If this sounds like fiction, think again. This is just one such situation we have dealt with this year, and the trend is escalating.

Microsoft 365 users enjoy Microsoft Entra ID passkeys that offer:

Better protection against phishing attacks
Reduced password-related support requests
Improved user experience
Faster sign-in processes
Stronger regulatory compliance

In practice, passkeys represent one of the most significant improvements to account security since multi-factor authentication became mainstream. Even if you are not a Microsoft 365 user, we suggest you think very carefully about improving secured access to email. Once an identity is stolen. building a new identity means significant costs and trouble.

Summary

Microsoft Entra passkeys are becoming the future of authentication across Microsoft’s cloud services. While many personal Microsoft account users will not need to take action, anyone responsible for a Microsoft 365 or Entra environment should review their authentication strategy now.

If you receive a notification about the retirement of SMS authentication, the first step is simple: sign in to the Microsoft Entra Admin Centre and determine whether you have access to a tenant. Once you know your status, you can take the appropriate action long before Microsoft’s February 2027 deadline.

Comstat provides independent advice on business IT choices that reduce risk, protect continuity, and support long‑term growth. If you need help with improving your ID security, please get in touch, or use our contact page to organize an appointment which suits your timetable. You can return to our Index of Articles by clicking here .

cPanel Disaster Recovery Backups: Ownership responsibility

by Steve Galloway | Jun 1, 2026

cPanel Disaster Recovery Backups: your data is yours to protect

Comstat maintains disaster recovery backups for your web server content and data strictly for our own administrative and disaster recovery purposes. This article sets out our backup policy which, in common with industry convention, relies on the principle that responsibility for data protection rests with the owner of the virtual server or hosting account.

This article explains how our disaster recovery backups are used within our hosting and virtual server environments — and just as importantly, how they are not used.

Click open the headers below to learn more about our policy regarding disaster recovery backups. Support options are available for professional assistance, and at the end of the article you can find links to guidance and help for implementing backups. You can return to our Index of Articles by clicking here.

Data is the responsibility of the owner

In all hosting environments managed by Comstat, the responsibility for data protection rests with the owner of the virtual server or hosting account.

That includes, but is not limited to:

Website content and uploads
Databases
Email data
Application‑specific files
Configuration changes made by the account holder

This is in line with Internet Service Provider (ISP) practice. For instance, neither Google nor Outlook.com undertake to back up your email or files. Although Microsoft 365 guarantees service level availability, data remains the responsibility of the owner.

Every website owner should maintain their own backup strategy that aligns with their business, regulatory, and operational needs. This may include one or more of these approaches:

cPanel backup (provided with your server)
Backup utilities like Backuply which you can install using WordPress or cPanel Softaculous library
off‑platform backups
third‑party backup services
or application‑level backup tools

We are glad to help you decide what is the best solution for your needs.

Importantly, although we do keep temporary backups which may be helpful as a last resort, our platform is not positioned as a primary backup service for end users.

Who Is Responsible for Data?

Responsibility for data protection rests with the owner of the virtual server or hosting account. In the case of the services we provide to you, this includes but is not limited to:

Website content and uploads
Databases
Email data
Application‑specific files
Configuration changes made by the account holder

Every website owner should maintain their own backup strategy. This makes sense because your strategy needs to align with your business, regulatory, and operational needs. This might include using:

solutions available to you with your hosting (e.g. Backuply, Softaculous WordPress Manager)
solutions provided to you by agreement with your agents
off‑platform backups
third‑party backup services
application‑level backup tools

Our data recovery backups are designed to cope with force majeure risks that your hardware is exposed to. Therefore, our platform is not positioned as a primary backup service for end users.

Why Comstat Takes Backups at All

Although responsibility for content and data ownership lies with an account holder, Comstat performs disaster recovery backups for clear and limited reasons:

Platform‑level disaster recovery
Server migration
Administrative resilience
Infrastructure failure scenarios
Major security incidents

In this way, our backup regime exists to protect the integrity of the hosting platform as a whole, not to replace user‑managed backup solutions.

Our backup framework is designed to support hardware management and recovery in exceptional circumstances—not routine file restoration or historical data retrieval.

How Our Backup Policy Works

Unfortunately, web site owners do not always deal with backups. In this situation, our operational backups might be able to restore a recent working configuration. However, this might not accomplish a most recent known working configuration. Also, our backup library extends to a 90-day rolling window.

Backup Scope

Full cPanel account backups
Incremental – file changes made since baseline/last increment
No guarantee of granular file‑level recovery
No long‑term archival storage
System files are excluded

Retention Model

Daily backups: retained for 7 days
Weekly backups: retained for 4 weeks
Monthly backups: retained for 3 months

This schedule provides a maximum recovery window of approximately 90 days, which is appropriate for disaster recovery while avoiding unnecessary data retention.

Backup Access

Backups are governed using native WHM and cPanel tools
Restore actions are typically administrator‑controlled
In some cases, backups may be visible to account holders in cPanel
Access is provided only as a last resort, not as a service guarantee

This model ensures that cPanel disaster recovery backups remain predictable, auditable, and aligned with platform boundaries.

Why We Use Native WHM Backups

Firstly, it helps to understand how a web server operates.

WHM – Web Host Manager

Web server (platform) administrators use an operating system called WHM (Web Host Manager) to manage servers. Think of WHM as an equivalent of Microsoft Windows (admin user). Usually, web site owners do not have access to this hierarchy level. This is because WHM requires specialist knowledge

cPanel – where daily work happens

Web site owners typically use cPanel (Windows standard user) to manage their web site, email, etc.cPanel provides a broad toolset to deal with web sites, email, file management, and many other end-user features. Like a Windows (standard) user, cPanel users have daily control of the web server for email, WordPress, and other features. However, some functions are omitted because they are not likely to be needed, and pose elevated security or operational risk.

How our backup policy fits

We operate backups at WHM level. These backups are executed by a WHM admin account which is not available to the web site owner. Using WHM’s built‑in backup utilities offers several advantages, but some limitations, too:

Tight integration with cPanel account structure
Correct handling of permissions and metadata
Well‑tested restore paths during emergencies
Clear separation between platform and user responsibility

Custom or script‑based backup systems can introduce ambiguity, complexity, and increased operational risk. For disaster recovery, reliability and predictability matter more than flexibility. This also means that because our backups are executed at an “admin” level, restoration of data usually requires adjustment to ownership and read/write permissions. This is why owner-operated backups work more efficiently. Also, restoration from our WHM environment entails cost.

What This Means for Website Owners

In practical terms:

You must maintain your own backups
You should not rely on platform backups for routine “restores”
Platform backups may help in exceptional circumstances
No backup availability is guaranteed beyond the defined retention window

This approach keeps expectations clear and ensures that responsibility is properly aligned.

Summary - Next Steps

If you have questions about suitable backup strategies for your workload, we are always happy to discuss best practices. Backup utilities are already available to you at cPanel level, including Backup for cPanel which allows you to download and store your site in a backup file. WordPress can be backed up using plugins like Backuply, and your installation can also be backed up using Softaculous WordPress Manager. This is available on your server too. Lastly, we publish articles about options like:

We continually introduce new content to our support section, so please do check our How To pages periodically.

Bear in mind that different solutions have their own merits. For instance, Softaculous WordPress Manager is great for ease of use. If you want to export your WordPress website to a new server, though, it is not a viable option. For that eventuality the second article in the list above is desirable. Admittedly, this approach is seemingly daunting, and you may need to contact us about this methodology. So, when you plan a backup strategy, you should define what the backups need to accomplish.

Remember, ownership of the data remains exactly where it should be: with you.

If you need help adopting this workflow, or you need disaster recovery planning or assistance, please get in touch, or use our contact page to organize an appointment which suits your timetable. You can return to our Index of Articles by clicking here .

Email System Audit and Recovery Review: What It Includes and Why It Matters

by Steve Galloway | May 10, 2026

What Is an Email System Audit and Recovery Review?

An email system audit and recovery review is a structured assessment of your company’s email environment. It examines how your system is configured, how secure it is, and how well it can recover from failure or attack.

Most modern businesses rely on platforms such as Microsoft 365. These systems are powerful, but they are also complex. Over time, settings drift, risks increase, and gaps appear. An audit brings clarity.

A proper email system audit and recovery review answers three key questions:

Is the system secure?
Is it configured correctly?
Can it recover quickly if something goes wrong?

Click open the headers below to learn more about how a professional email system audit helps meet IT compliance standards. Support options are available for professional assistance. You can return to our Index of Articles by clicking here.

What Does an Email System Audit Cover?

An email system audit and recovery review focuses on several core areas. Each one plays a role in protecting your business.

Security and Access

This aspect of an email system audit includes checks on:

Multi-factor authentication (MFA)
Admin permissions and access levels
Legacy protocols such as IMAP or POP
Conditional access policies

The goal is to reduce the risk of account compromise, which is one of the most common entry points for attackers.

Mail Flow and Protection

At this stage of an email system audit we review how email enters and leaves your system:

SPF, DKIM, and DMARC records
Anti-spoofing protection
Anti-phishing and malware filtering
A well-configured system stops threats before they reach users.

Mailbox and Data Configuration

As your email system audit progresses, the focus of this exercise deals with how data is stored and managed:

Mailbox permissions and shared access
Retention policies
Archiving and audit logging

Often, businesses discover that data is either not protected enough, or kept longer than needed.

What Is a Recovery Review?

While the audit looks at your current state, the recovery element looks at your future resilience.

A strong email system audit and recovery review will assess:

Backup and Restore Capability

Microsoft 365 includes retention, but it is not a full backup solution. Other email systems make no provision for retention or broader backups at all. A review checks:

Whether backups exist
How quickly data can be restored
How granular recovery is (single emails vs full mailboxes)

Incident Response Readiness

If an account is compromised, speed matters. The review looks at whether you can:

Revoke sessions quickly
Reset access securely
Remove malicious rules or forwarding

Business Continuity

You should also know what happens if:
DNS settings fail
A widespread outage occurs

Few organisations have a good understanding of these areas.

Why This Matters for Modern Businesses

Email is still the backbone of business communication. It is also a primary attack vector. A thorough email system audit and recovery review helps to:

Reduce the risk of phishing and account takeover
Protect sensitive client data
Protect sensitive client data
Improve compliance and record keeping
Provide confidence for directors and stakeholders

In many cases, it also highlights unused features within your existing licensing—especially in Microsoft 365—that can improve security without increasing cost.

A Practical Approach: Audit in Stages

Many assume an audit must be a large, one-off exercise. In reality, a staged approach is often more effective.
An email system audit and recovery review can be delivered in phases:

Phase 1: Security Baseline

Address critical risks such as MFA, admin access, and mail spoofing.

Phase 2: Configuration and Data

Review policies, permissions, and retention settings.

Phase 3: Recovery and Resilience

Assess backup, monitoring, and incident response processes.

This staged model allows work to be budgeted and managed over time. It also reflects how systems evolve, rather than treating the audit as a fixed snapshot.

A useful comparison is financial accounting. Accounts show a position at a moment in time. By contrast, an email system audit and recovery review can act as an ongoing process, adapting as your business grows and risks change.

What You Should Expect from an Audit

A professional email system audit and recovery review should deliver:

A clear findings report
Risk ratings (critical, high, medium, low)
Plain English explanations
A prioritised action plan

The aim is not just to highlight issues, but to give practical steps that improve your system.

Summary

An email system audit and recovery review is not just a technical exercise. It is a way to protect your operations, your data, and your reputation.

Handled correctly, a dsicipline like this provides both immediate improvements and a long-term roadmap. Whether delivered in one piece or in stages, it helps ensure your email system is secure, resilient, and fit for purpose.

« Older Entries