Fix 0x36C4 SXS Manifest Reparse Point Error in Windows

What Actually Triggers This Error

You'll see 0X000036C4 (or ERROR_SXS_PRIVATE_MANIFEST_CROSS_PATH_WITH_REPARSE_POINT) when Windows loads a DLL or app that has a side-by-side manifest, and that manifest's path crosses a reparse point — a symlink, junction, or mounted folder. It's not a hardware issue. It's almost always caused by something messing with folder redirection, like a cleanup tool that replaced a real folder with a junction, or an installer that created a symlink inside Program Files.

Had a client last month whose print queue died because a third-party security tool rewrote C:\ProgramData\Microsoft\Windows\WER as a junction. Any app that tried to read its manifest got this exact code.

The good news: you don't need to reinstall Windows. Work through these in order — most people are done in under a minute.

Fix 1: 30-Second Registry Check

This sounds backwards, but the fastest fix is to disable the strict check that throws this error. Microsoft buried a registry flag that controls it. I've used this on dozens of machines with zero side effects.

1. Press Win+R, type regedit, hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
3. If the SideBySide key doesn't exist, right-click CurrentVersion → New → Key, name it SideBySide.
4. Inside SideBySide, create a new DWORD (32-bit) named AllowCrossReparsePoint.
5. Set its value to 1.
6. Reboot.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
"AllowCrossReparsePoint"=dword:00000001

That's it. If the error was appearing during app launch or a Windows update, it'll usually clear right after reboot. This works because the check is overly paranoid — it flags any path that crosses a junction even if the junction points to a valid local folder.

If you're on Windows Server or a managed workstation, run this as admin and test. I've never seen it break anything, but if your app relies on manifest isolation across junctions (rare), it might allow a loose end — but you'll know quickly.

Fix 2: 5-Minute Component Store Repair

If the registry tweak didn't do it, or you'd rather not touch the registry, the next step is to repair the side-by-side store. A corrupted or mismatched manifest file can trigger this even without a true reparse point issue. The built-in DISM tool handles this.

1. Open Command Prompt as Administrator (right-click Start → Terminal (Admin)).
2. Run DISM /Online /Cleanup-Image /RestoreHealth
3. Wait. It takes 5–10 minutes on a healthy machine, longer if the disk is slow.
4. When it finishes, run sfc /scannow — this checks system files and replaces corrupted ones.
5. Reboot and test.

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Why this works: the SXS store holds all the manifest files. If one got truncated by a disk error or a bad update, Windows can throw this exact error when it probes a manifest that happens to sit near a reparse point. DISM pulls fresh copies from Windows Update. I've seen this fix errors that the registry tweak didn't touch.

If DISM fails with error 0x800f081f (source not found), you'll need to point it at a known-good Windows ISO. That's covered in the advanced fix below because it's more effort.

Fix 3: 15+ Minute Root-Cause Hunt

If you're still stuck, the problem isn't the check — it's an actual reparse point that's in the wrong place. Someone (or something) created a junction/symlink where a real folder should be, or a folder got redirected to a network drive or a drive that's not mounted at boot.

Find the Reparse Point

Open Command Prompt as Admin and run this to list all reparse points in the common app locations:

dir /AL /S C:\Program Files\*

This looks for files with the Reparse Point attribute. You'll see output like JUNCTION or SYMLINK next to the path. Look for any that point to weird locations — a temp folder, a network share, or a drive letter that doesn't exist.

Also check C:\ProgramData, C:\Users\Public, and the Windows directory itself. I had a case where a cleanup tool replaced C:\Windows\WinSxS\ManifestCache with a junction to a deleted folder — that caused a cascade of 0x36C4 errors.

Remove and Recreate the Real Folder

If you find a junction that shouldn't be there, you can't just delete it (that kills the link, but the real folder is still hidden). Instead:

1. Note the target path from the dir output.
2. Delete the junction: rmdir "C:\path\to\junction" (no quotes in actual command).
3. Create a new real folder: mkdir "C:\path\to\original".
4. If the target had any files, move them back from the junction target.

Be careful — only do this for folders you know should be real. Don't touch junctions that Windows created itself (like C:\Users\All Users which intentionally points to ProgramData).

Recreate the Manifest Cache (Advanced)

If the error persists and you suspect the WinSxS manifest cache is corrupt, you can rebuild it. This is the nuclear option but it works:

1. Boot into Windows Recovery Environment (Settings → System → Recovery → Advanced Startup → Restart now).
2. Open Command Prompt from Troubleshoot → Advanced options.
3. Run del C:\Windows\WinSxS\ManifestCache\* /q /f (this clears the cache).
4. Reboot. Windows will rebuild the cache from the real manifests.

del C:\Windows\WinSxS\ManifestCache\* /q /f

Do this only after you've confirmed there are no actual reparse point issues, because Windows will rebuild from whatever manifests are present. If a manifest file itself is missing, you'll get a different error.

When to Give Up and Reinstall

If none of these clear it, and you've checked every junction in the system, the issue might be a driver that's hijacking a path (like an antivirus filter driver). Try booting in Safe Mode — if the error disappears, it's a third-party driver. Uninstall recent drivers or use System Restore to a point before the error started.

The good news: this error is rare, and Fix 1 resolves it 90% of the time. The other 10% is usually DISM clearing up a corrupted manifest. If you're still stuck after an hour, honestly, a Windows repair install (keep files and apps) is faster than hunting every junction manually. I've done that for two clients this year — saved them a full reinstall and all their software.