Fix STATUS_POLICY_OBJECT_NOT_FOUND 0XC000029A

Quick Answer for Advanced Users

gpupdate /force fails or you see 0XC000029A? Delete the corrupted policy object in C:\Windows\System32\GroupPolicy and reapply. If it's a domain issue, check dcdiag /test:sysvolcheck and fix SYSVOL replication.

Why This Happens

I've seen this error pop up in two flavors. First, on a standalone Windows 10 or 11 machine where the local Group Policy store gets scrambled by a bad update or a failed power outage during a policy refresh. Second, on domain-joined machines where SYSVOL replication on the domain controller is broken or a GPO itself got half-deleted by an admin who didn't know what they were doing. The error code 0XC000029A literally translates to 'STATUS_POLICY_OBJECT_NOT_FOUND' – Windows is looking for a policy file that should be there but isn't.

Let me be clear: this isn't a driver issue or a hardware fault. It's a corrupted policy store. Had a client last month whose entire print queue died because of this – the policy that mapped network printers got nuked, and every user on the domain hit this error at login. We spent an hour chasing print spooler logs before I checked the event viewer and saw the code.

Fix Steps

Open an elevated Command Prompt. Hit Win+X, select 'Command Prompt (Admin)' or 'Terminal (Admin)'. Don't skip this – fixes won't stick without admin rights.
Run gpupdate /force. If you see the error immediately, move to step 3. If the error doesn't appear yet, replicate it so you know what's broken.
Check Event Viewer for the exact policy path. Press Win+R, type eventvwr.msc, hit Enter. Go to Windows Logs > System. Look for an event with source 'Group Policy' and ID 1058 or 1059. It will list the missing file path – something like \\domain\sysvol\domain.local\Policies\{GUID}\Machine\registry.pol.
If it's a local machine, delete and rebuild the policy store. Run these commands one at a time:
```
DEL /F /S /Q C:\Windows\System32\GroupPolicy\*
RD /S /Q C:\Windows\System32\GroupPolicy
gpupdate /force
```
This clears everything and forces Windows to rebuild from scratch. Yes, you'll lose custom local policies – but you already lost them, so no real harm.
If it's a domain machine, check SYSVOL on the DC. On your domain controller, run dcdiag /test:sysvolcheck. If it fails, you've got replication issues. Fix with:
```
repadmin /syncall /AdeP
```
Then check the missing GPO path from step 3 – if the folder is gone, restore from backup or recreate the GPO.
Restart the Group Policy Client service. In the same admin prompt, run:
```
net stop gpsvc
net start gpsvc
gpupdate /force
```

Alternative Fixes If the Main One Fails

If you're still staring at 0XC000029A after those steps, try these in order:

Check file permissions. The policy folders need SYSTEM and Administrators to have full control. Right-click C:\Windows\System32\GroupPolicy, go to Security, make sure SYSTEM has 'Full control'. I've seen antivirus strip these permissions after a definition update.
Run SFC and DISM. System file corruption can cause this. Run:
```
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
```
Then reboot and try gpupdate again.
Reset the Group Policy database. This is rare but happens. Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History. Export it first, then delete everything under that key. Reboot and run gpupdate. Note: this clears policy history for all users and can cause temporary weirdness.
On a domain controller, force authoritative SYSVOL restore. This is advanced – only do this if you're sure the current SYSVOL is bad and you have a known-good backup. Stop the Netlogon service, delete the SYSVOL folder contents, then restore from backup, restart the service. Or use dfsradmin if you're using DFSR.

Prevention Tip

This error almost always comes from a botched policy update or a replication failure. To avoid it:

Never edit GPO files directly – always use Group Policy Management Console. I had a client who thought they could speed things up by copying registry.pol files manually. They learned the hard way.
Monitor SYSVOL replication with daily dcdiag tests if you have multiple DCs. Replication lag is the #1 cause of missing policies in domain environments.
Back up the GroupPolicy folder after any major policy change. On stand-alone machines, just copy C:\Windows\System32\GroupPolicy to a safe spot before running gpupdate after a risky change.