0XC0000022

General System STATUS_ACCESS_DENIED Applies to: Windows 7, Windows 10, Windows 11

What it means

A related but technically distinct code from the more common 0x80070005 — this is the NTSTATUS-style access-denied error, most often seen when a program can't open a file, DLL, or registry key it needs at startup, or when Windows activation specifically fails because the Software Protection Service can't start.

Also seen as: 0xC0000022, c0000022, Access Denied {NTSTATUS}

Quick fix steps

  1. If it appeared during Windows activation specifically, check the Software Protection service: press Windows+R, type services.msc, find "Software Protection," and try starting it — if it also shows "Access is denied," that confirms this as the specific cause.
  2. Try running the affected app as administrator first — right-click its shortcut or icon and choose "Run as administrator."
  3. Check whether antivirus software is blocking or sandboxing the app rather than a genuine permissions problem — temporarily disabling third-party antivirus as a diagnostic test is worth trying.
  4. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin Command Prompt — this can repair permissions on system files that a previous malware cleanup or an aggressive "permission repair" tool may have stripped, alongside fixing file corruption.
  5. If this is tied to a specific non-critical background service (some users see it referencing something like "Cloud Files Diagnostic Event Listener," a OneDrive-related component) and everything else is working normally, it can often be safely ignored rather than actively chased down.
  6. As a last resort for a persistently broken user profile, creating a new Windows user account and checking whether the same app works there helps confirm whether the issue is specific to your current profile's permissions.
For the full step-by-step walkthrough, see sfc /scannow Explained: What It Does and How to Read the Results.

Frequently Asked Questions

Is this the same as the more common 0x80070005 error?
They mean the same general thing (access denied due to permissions) but are technically different code formats used in different contexts — 0xC0000022 shows up more in activation, app-launch, and service-startup scenarios, while 0x80070005 is more common in installer and Windows Update contexts.
Does this mean malware damaged my Windows installation?
Not necessarily malware itself — it's more often an overly aggressive "PC cleaner" or permission-repair tool that stripped correct access rights from system files, or a genuine antivirus false positive, rather than an active infection.
Is it safe to run sfc and DISM even if I'm not sure this is the cause?
Yes — both are official Microsoft repair tools that only check and fix, they don't remove your files or programs, so running them as a diagnostic step carries no real risk.

Other error codes