Fix 0XC0000433 STATUS_ENCOUNTERED_WRITE_IN_PROGRESS

Quick Fix – Unlock the File (30 Seconds)

Nine times out of ten, this error is just a file lock that didn't get released. A backup job or an antivirus scan grabbed the file, something else tried to write to it, and you got the collision.

1. Close any program that might be using the file. If you're copying to a USB drive, close Explorer windows pointing at it. If it's a database file, stop the database service.
2. Run Process Explorer or Handle from Sysinternals. Run it as admin, press Ctrl+F, type the file name or part of it. Look for handles – you'll see which process has the write lock. Kill that process (right-click → Kill Process) or close the handle.
3. Retry the operation. If it works now, you're done.

Still broken? Move to the next step.

Moderate Fix – Disable Real-Time Protection & Backup Software (5 Minutes)

The culprit here is almost always antivirus real-time scanning or backup software that hasn't released the file handle properly. I've seen this with Veeam, Acronis, and even Windows Defender.

Step 1: Temporarily disable real-time AV

For Windows Defender:

powershell -Command "Set-MpPreference -DisableRealtimeMonitoring $true"

For third-party AV, disable the real-time shield from the tray icon. Don't forget to re-enable it after testing.

Step 2: Check for backup jobs

If you use Veeam, Acronis, or any volume snapshot-based backup, they often hold write locks on VSS (Volume Shadow Copy). Open the backup console, check if a job is running, and either stop it or wait for it to finish.

Step 3: Identify the process with Handle.exe

Download Handle from Sysinternals. Run this from an elevated command prompt:

handle.exe -a -u -p <PID_of_writing_process>

Replace <PID> with the process ID that's failing. Look for the file path in the output – you'll see which process is holding the lock.

If the lock is from a system process (like System PID 4), that's trickier. See the advanced fix.

Advanced Fix – Registry Lock or Driver Conflict (15+ Minutes)

When the error isn't about a file but about a registry key, you're dealing with a different beast. This happens when Windows tries to write a registry value and another process already has it open for writing. Common with group policy updates, driver installs, or buggy third-party kernel drivers.

Step 1: Check the Event Viewer

Open Event Viewer → Windows Logs → System. Look for Event ID 0xC0000433 or 26 (Source: Application Popup). The log will usually tell you which registry path or file caused the collision. Write that path down.

Step 2: Use Process Monitor to capture the lock

Download and run Procmon from Sysinternals. Set a filter:

1. Filter → Path → contains → the registry key or file path from the Event Viewer
2. Look for IRP_MJ_WRITE with result SHARING_VIOLATION or WRITE_IN_PROGRESS
3. Note the Process Name and PID that's blocking the write

Step 3: Kill or restart the blocking process

If the blocking process is a driver (like hmpalert.sys from HitmanPro Alert), you'll need to uninstall that software. If it's a system process (PID 4), you might have a driver that's hanging. Run Driver Verifier:

verifier /standard /all

Wait for a blue screen – that's actually good. It tells you which driver is misbehaving. Then boot into Safe Mode and remove that driver.

Step 4: Registry fix for persistent locks

If the error keeps coming back for a specific registry key (common with HKLM\SYSTEM\CurrentControlSet\Services), the key might be corrupt. Boot into Safe Mode with Command Prompt and run:

reg load HKLM\TempHive C:\Windows\System32\config\SYSTEM
reg delete "HKLM\TempHive\ControlSet001\Services\ProblematicService" /f
reg unload HKLM\TempHive

Replace ProblematicService with the service name from your error logs. Reboot normally.

If Nothing Works – Last Resort

You've tried everything above and the error still appears? Time to check if you're dealing with a corrupted NTFS volume or a failing disk.

1. Run chkdsk C: /f from an elevated command prompt. If it reports bad sectors, the disk is failing. Replace it.
2. Check the S.M.A.R.T. status with CrystalDiskInfo. If you see reallocated sectors, stop writing to that drive and back up everything now.

I've seen this error on drives with 80+ pending sectors. The write lock was a symptom of the drive trying to relocate data and failing. New drive fixed it.

One more thing: if the error only happens with Windows Update or Store apps, run the Windows Update troubleshooter from Settings → Update & Security → Troubleshoot. It's rare but sometimes the update service gets stuck holding a write lock.