0x1126: Not a Reparse Point—Fix It Now

This error hits when you try to read or set a junction, symlink, or mount point on a file or folder that isn't one. Real-world trigger: accessing a symbolic link that's been replaced by a real file.

When This Error Shows Up

You're trying to delete a folder or read a symbolic link and get ERROR_NOT_A_REPARSE_POINT (0x00001126). This usually happens after a backup restore or a failed move. I had a client last month whose entire accounting file structure broke because a backup tool replaced a junction with a real folder but left the reparse tag. Every time QuickBooks tried to follow the junction, it hit this error and locked up the company file.

Root Cause in Plain English

A reparse point is a special marker on a file or folder that tells Windows to redirect I/O elsewhere—like a shortcut for the file system. Symlinks, junctions, and volume mount points all use reparse points. When you get error 0x1126, it means the file or directory has a reparse tag in its metadata but the actual data isn't a valid reparse point. This is like having a sign that says "turn left" but no road on the left. Windows can't follow it, and can't remove it normally.

The most common causes:

Restoring a symlink or junction from a backup that didn't preserve reparse point data correctly.
Running a tool like mklink on a file that already had a different reparse type.
Copying a reparse point to a filesystem that doesn't support it (like FAT32 or an older network share).

Fix It: Steps That Actually Work

Skip the GUI. File Explorer will just keep throwing the same error. You need command-line tools that talk directly to the NTFS master file table.

Step 1: Identify the Bad Reparse Point

Open an elevated Command Prompt—right-click Start > Command Prompt (Admin) or Terminal (Admin). Run:

fsutil reparsepoint query "C:\Full\Path\To\FileOrFolder"

If it says "The file or directory is not a reparse point," that's the error. If it shows a reparse tag but then errors, the tag is corrupted.

Step 2: Delete the Reparse Tag Directly

You can't use del or rmdir because Explorer blocks it. Use fsutil to nuke the tag:

fsutil reparsepoint delete "C:\Full\Path\To\FileOrFolder"

This removes the reparse tag without touching the underlying file or folder data. If it succeeds, you can now delete or rename normally.

Step 3: Use PowerShell If fsutil Fails

Sometimes fsutil won't work because the reparse point is in a weird state. I've seen this on Windows Server 2019 with deduplication enabled. Try:

Remove-Item -LiteralPath "C:\Full\Path\To\FileOrFolder" -Force

The -LiteralPath flag is critical—without it, PowerShell tries to follow the broken reparse point and fails.

Step 4: As a Last Resort—Use Disk Structure Tools

If the above still gives 0x1126, you need to go even lower. The chkdsk command can sometimes clean orphaned reparse tags. Run:

chkdsk C: /f

This schedules a disk check on next reboot. Restart and let it run. After that, try the fsutil delete step again. I've had this work on a corrupted junction left behind by a botched Robocopy.

What to Check if It Still Fails

Permissions: You need Full Control over the file and folder. Right-click > Properties > Security > check your user has Modify or Full Control.
Antivirus interference: Some AV tools (looking at you, McAfee) lock reparse operations. Temporarily disable real-time protection.
File system type: The drive must be NTFS or ReFS. If it's FAT32 or exFAT, reparse points aren't supported at all. Copy the data off and reformat the drive.
Backup software hooks: If you use VSS-based backup, the Volume Shadow Copy service may hold a lock. Restart the VSS service or reboot clean.

If nothing works after trying all four steps, the file's MFT entry is likely hosed. Your safest bet is to boot from a Windows install USB, open Command Prompt (Shift+F10), and run fsutil from there—the OS isn't using the file, so the delete usually sticks.