BitLocker 0XC0210022: RAW Access Mode Fix

That RAW Access Error is Infuriating—Here's the Fix

I know seeing STATUS_FVE_RAW_ACCESS (0XC0210022) when you're just trying to encrypt your drive feels like a punch. The message literally says "no action was taken"—which is the last thing you want. This tripped me up the first time too, especially on Windows 10 Pro machines that suddenly started throwing it after a BIOS update. The fix is straightforward, and you don't need to wipe anything.

First, Kill RAW Access Mode

The core problem: BitLocker's getting confused because the drive is flagged for raw sector access (often used by disk imaging tools or backup software). Windows sees that flag and says "nope, I'm not touching this."

Option A: Group Policy (Windows Pro/Enterprise)

1. Press Win + R, type gpedit.msc, hit Enter.
2. Navigate to: Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption.
3. Find "Allow access to BitLocker-protected fixed data drives from earlier versions of Windows"—double-click it.
4. Set it to Disabled. (Yes, disabled. You don't want RAW access.)
5. Click OK, close Group Policy Editor.

Option B: Registry (Works on All Editions)

If you're on Windows 10/11 Home, Group Policy isn't available. Registry to the rescue.

reg add "HKLM\SYSTEM\CurrentControlSet\Control\FVE" /v RawAccess /t REG_DWORD /d 0 /f

This sets RawAccess to 0, which disables raw access for BitLocker. Run that in an elevated Command Prompt (right-click > Run as administrator).

Restart and Retry Encryption

After changing the policy or registry, reboot. I've seen people skip this and wonder why nothing changed—restart is non-negotiable here. Once you're back in, open BitLocker Drive Encryption from Control Panel, and you should be able to turn it on without the error.

Why This Works

BitLocker holds the RawAccess flag to prevent conflicts when third-party tools try to read the encrypted drive at the sector level. When that flag is set to 1 (or enabled via policy), BitLocker throws error 0XC0210022 to protect the drive's integrity. By disabling it, you're telling BitLocker—and Windows—that no external tool needs raw access, so encryption can proceed normally. Think of it as a safety lock that sometimes gets stuck. You're just turning the key.

Less Common Variations

Sometimes you'll see this error pop up after installing software like Acronis True Image, Macrium Reflect, or Veeam Agent. Those tools request raw disk access for backups. If the error appeared right after installing one of those, uninstalling the tool can also fix it—but the registry fix above is faster and doesn't break your backup software.

Another rare trigger: a corrupted Group Policy object that forces RAW access even when you didn't set it. If the registry fix doesn't stick after reboot, check the HKLM\SYSTEM\CurrentControlSet\Control\FVE key again—if it's back to 1, chase down the policy that's re-applying it. Run gpresult /h gpresult.html to see applied policies.

Preventing This in the Future

Two things: first, if you use disk imaging or backup tools, install BitLocker first, then the backup software. That way the tool asks for raw access properly, and Windows doesn't get its wires crossed. Second, never set the RawAccess registry key to 1 manually—it's only useful in very specific enterprise scenarios where you're moving encrypted drives between systems. For normal desktop use, keep it at 0 (or policy disabled).

You're good now. That error won't come back unless something explicitly flips the flag—and you know exactly how to fix it if it does.