STATUS_ACCESS_DENIED 0xC0000022: Quick Fix Guide

Quick Answer (for advanced users)

Right-click the app or file > Properties > Security > Advanced > Change owner to your account. If that doesn't work, create a new local user profile and migrate your data. The error means the system can't validate your token for that resource.

What Actually Causes 0xC0000022

This error pops up when you're running an app or accessing a file and Windows hits the brakes. The kernel says "nope, you don't have the right token." It's not a virus, not a driver issue — it's a permissions mismatch. I've seen it most often after a Windows update changes file ownership, or when you copy an app from another user's folder. The real culprit is almost always one of three things: corrupted user profile, broken file permissions, or UAC blocking a process that needs admin rights.

You'll see it with games, old business software, or even Windows utilities like Task Scheduler. The error code itself is 0xC0000022, but the message might say "Access is denied" or "STATUS_ACCESS_DENIED." Don't waste time scanning for malware — start with permissions.

Step-by-Step Fix (Start Here)

These steps work on Windows 10 (all versions) and Windows 11. You don't need any special tools.

Step 1: Run the App as Administrator

This is the quickest test. Right-click the executable or shortcut, select "Run as administrator," and click Yes on the UAC prompt. If it works, you know the problem is a rights issue. You can set it permanently: right-click > Properties > Compatibility tab > check "Run this program as an administrator" > Apply. After clicking Apply you should see the box stay checked. Then try launching normally.

Step 2: Take Ownership of the File or Folder

If running as admin doesn't work, the file itself might have its owner set to SYSTEM or TrustedInstaller. You need to take ownership.

1. Right-click the file or folder that triggers the error. Choose Properties.
2. Go to the Security tab. Click Advanced at the bottom.
3. In the Advanced Security Settings window, look at Owner. It likely says "TrustedInstaller" or "SYSTEM." Click Change.
4. In the box that opens, type your username (e.g., YourName) and click Check Names. If it underlines it, click OK.
5. Back in Advanced Security, check the box "Replace owner on subcontainers and objects" (if it's a folder). Then click Apply.
6. You should see a Windows Security popup — click OK. Then click OK again to close.

After taking ownership, give yourself Full Control: right-click again > Properties > Security > Edit > select your user > check Full Control > Apply. Restart the app. This fixes about 70% of 0xC0000022 cases.

Step 3: Check User Profile Integrity

If ownership didn't help, your user profile might be damaged. This happens after a failed Windows update or disk error. Here's how to test it:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
3. Look for folders starting with S-1-5-21-. Each one is a user profile. Click each one and check the State value on the right — it should be 0. If it shows 2, that profile is corrupted.
4. Also check RefCount — it should be 0. If it's anything else (like 1), the profile is in use by a ghost process.

If you see a corrupted profile, you'll need to create a new local user account and move your data. Don't delete the old one until you've copied everything.

Alternative Fixes (If the Main One Fails)

These are less common but work when the above doesn't.

Fix 1: Disable User Account Control Temporarily (Test Only)

I don't recommend leaving UAC off, but disabling it can confirm if UAC is the blocker. Type UAC in Start, open "Change User Account Control settings," drag the slider to Never Notify, restart, and test the app. If it works, you know UAC was blocking it. Turn UAC back on after testing. The real fix is adjusting the app's compatibility settings or its executable permissions, not killing UAC.

Fix 2: Repair System Files

Corrupted system files can cause permission checks to fail. Open Command Prompt as admin and run:

sfc /scannow

This scans and replaces damaged files. After it finishes (can take 15 minutes), restart and test. Also run DISM /Online /Cleanup-Image /RestoreHealth to fix the image source. Both commands together cover corruption that might trigger 0xC0000022.

Fix 3: Reset App Permissions via PowerShell

For Windows Store apps or modern apps, reset the permission store. Open PowerShell as admin and run:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This re-registers all built-in apps. It takes about a minute. Restart after.

Prevention Tip

The easiest way to avoid 0xC0000022: never copy installed applications between user folders. Each app has ACL entries tied to the original user. Always uninstall and reinstall from the original installer. Also, run Windows Update regularly — Microsoft quietly ships permission fixes in cumulative updates. Set updates to install automatically and you'll dodge half the access-denied errors.

Still stuck? Try booting into Safe Mode with Networking (hold Shift while clicking Restart > Troubleshoot > Advanced Options > Startup Settings > Restart > 5). If the error doesn't appear there, the problem is a third-party service or driver interfering with permissions. Disable non-Microsoft services via msconfig and narrow it down.