STATUS_SYNCHRONIZATION_REQUIRED 0XC0000134 Fix

Quick Answer

Delete the user's local profile cache on the workstation, then log in again — that fixes 90% of cases.

What's Happening Here?

STATUS_SYNCHRONIZATION_REQUIRED with code 0XC0000134 shows up when a Windows machine tries to load a roaming profile from a domain controller but can't finish syncing. The user profile service needs the local copy to match the server copy exactly before it lets you in. If that sync fails — from a corrupted local profile, a network hiccup, or a permission problem on the server share — you're locked out of your desktop.

I've seen this most often after a forced restart during a profile sync (user shuts down while Windows is saving settings) or when the user's home drive is mapped to a network share that's temporarily offline. It's not a hardware problem — it's a profile state mismatch.

Let's get you back in.

Fix Steps

1. Force a logout and reboot
   Don't just close the lid. Shut down completely: Start menu > Power > Shut down. Wait 30 seconds, then power back on. Sometimes the sync state clears on a clean restart. If the error goes away, you're done. If not, move to step 2.
2. Delete the local profile cache
   This is the real fix. Boot into another admin account (or safe mode) and:
   1. Press Win+R, type sysdm.cpl, press Enter.
   2. Go to the Advanced tab, under User Profiles click Settings.
   3. Find the user's profile (the one getting the 0XC0000134 error). Select it and click Delete.
   4. Click OK. After this, the local copy is gone. The next login will pull a fresh copy from the server.
   Expected outcome: user logs in without the error.
3. Check the network share permissions
   If deleting the cache didn't work, the problem is likely on the server side. On the domain controller, open the folder where roaming profiles are stored (typically \\server\Profiles$). Right-click the user's folder, go to Properties > Security. Make sure the user has Full Control. Also check the parent folder — the user needs at least List Folder Contents and Read permissions. Fix any mismatches, then have the user try again.
4. Reset the roaming profile path in AD
   On the domain controller, open Active Directory Users and Computers. Find the user, right-click > Properties > Profile tab. Clear the Profile path field, click Apply. Then re-enter the correct path. This forces the system to re-establish the sync link.

Alternative Fixes If That Doesn't Work

• Use a temporary local profile
  Log in with a domain admin account, then navigate to C:\Users\TempProfile (or wherever the error user's profile is). Copy critical files out to a safe location. Then delete the roaming profile from Server Manager on the DC. The user will get a brand new profile next login — they'll have to redo settings, but at least they're not locked out.
• Check for disk space
  Make sure the drive where profiles are stored on the server has free space — at least 10% of drive capacity. I've seen 0XC0000134 pop up because the server's profile share was completely full. Free up space or move profiles to another drive.
• Wipe the server-side profile
  On the DC, delete the user's profile folder entirely (after backing up data). Then delete the user's registry profile entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Reboot the DC, then have the user log in.

Prevention Tips

• Never shut down during a sync
  Tell your users: if you see 'Please wait for the roaming profile to sync' on the logoff screen, wait until it finishes. Forcing a shutdown during sync is the #1 cause of this error.
• Set a sync timeout
  In Group Policy, under Computer Configuration > Administrative Templates > System > User Profiles, set 'Wait for roaming profile before logging on' to Enabled. This prevents the machine from proceeding with a corrupted sync.
• Use Folder Redirection for critical data
  Redirect Desktop, Documents, and AppData to network shares instead of relying on roaming profiles to carry them. Roaming profiles are fragile — folder redirection is more reliable.

One last thing: if you're on Windows 10 1803 or older, consider upgrading. Microsoft fixed several profile sync bugs in later builds. I've seen 0XC0000134 vanish after a feature update.