Fix STATUS_OBJECT_PATH_SYNTAX_BAD 0XC000003B on Windows

This error means Windows can't parse a file path — usually a corrupted symlink, junction, or a path with illegal characters. It's common with backups, antivirus scans, or old apps.

Quick answer (for the impatient)

Run chkdsk /f C: from an elevated command prompt, then reboot. If it persists, delete the broken junction or symlink using rmdir /s /q \\?\path\to\broken\folder. 90% of the time, that's it.

Why you're seeing this

Error 0XC000003B — STATUS_OBJECT_PATH_SYNTAX_BAD — means Windows tried to traverse a directory path and hit something it couldn't parse. The culprit here is almost always a corrupted reparse point: a junction, symbolic link, or mount point that points to a deleted or nonexistent location. Think of it like a shortcut on your desktop that leads to a folder you already deleted — except NTFS's version of that shortcut is now unreadable.

This happens most often after:

Restoring files from backup software (Veeam, Acronis, Windows Backup) that didn't handle junctions cleanly
Running disk cleanup tools that delete junction targets
Antivirus scans that quarantine junction targets mid-scan
Moving folders across drives with junctions left behind
Old Windows 10 installs upgraded to 11 that carried over broken Application Data links

I've also seen it on Windows Server 2019/2022 when DFS replication stumbles on junction points. Don't bother with sfc /scannow first — it rarely helps here because this isn't a system file corruption, it's a metadata corruption on disk.

Step-by-step fixes

Step 1: Run chkdsk to find and fix the damage

Open Command Prompt as Administrator. Type:

chkdsk /f C:

If it asks to schedule at next reboot, type Y and restart. Let it run — on large drives (2TB+) this can take an hour. When it finishes, log back in and test your backup or app that threw the error.

If the error's gone, you're done. If not, move to step 2.

Step 2: Identify the broken junction or symlink

You need to find where the bad path lives. If you know the file or folder that triggered the error, start there. Open an elevated command prompt and navigate to its parent folder. Then run:

dir /al /s

This lists all reparse points (junctions, symlinks, mount points) in current directory and subdirectories. Look for entries where the target path doesn't exist anymore — they'll show up with a <SYMLINKD> or <JUNCTION> flag. If you see something like C:\Users\OldUser\AppData\Local\Temp [C:\Users\DeletedUser\... — that's your suspect.

Step 3: Delete the broken junction

Do not delete it with a simple del or rd — that'll fail. Use the extended-length path syntax to force it:

rmdir /s /q \\?\C:\Users\OldUser\AppData\Local\BrokenJunctionName

Replace the path with yours. The \\?\ prefix tells Windows to bypass path parsing — exactly what you need when the path parser itself is broken. If that throws an error, try the same thing but add \\?\ to the full UNC path. I've had to do this on Server 2016 plenty of times.

Once deleted, verify with dir /al again. Then retry your original operation that crashed.

Step 4: Recreate the junction if needed

If the broken junction was part of a system function (like User Shell Folders or a backup target), recreate it pointing to a valid directory. For example, to recreate a missing temp junction:

mklink /j C:\Users\YourUser\AppData\Local\Temp C:\Temp

Don't recreate it if you don't know what it was for — you'll just create a new problem.

If the main fix fails

Sometimes the junction is in use by a system process. In that case:

Boot into Safe Mode or Windows Recovery Environment (hold Shift while restarting, then Troubleshoot > Advanced Options > Command Prompt).
Run the rmdir command from there. No system processes running means you can delete anything.
After reboot, run chkdsk /r C: to scan and recovery bad sectors that might've caused the corruption.

If you're still stuck, check the Application and System event logs (Event Viewer) for event ID 157 or 98 from source Ntfs — those log specific corruptions. Google the exact file path you find there.

Prevention tips

Stop using junctions for critical app paths unless you absolutely have to. They're brittle. Prefer symbolic links (mklink without /j) or just move the folder and update the app config.

If you're a backup admin: configure your backup software to skip reparse points by default. Veeam has a checkbox for this — check it. Acronis calls it 'Preserve junctions' — uncheck it.

And for the love of god, don't run third-party disk cleaners like CCleaner on systems with junction-heavy user profiles. I've seen it nuke Application Data junctions on Windows 10 20H2 and force a full profile rebuild.

Final thought: error 0XC000003B is a metadata bug, not a hardware failure. Don't replace your disk until you've tried these steps. I've seen admins RMA drives over this — don't be that guy.