When does this error actually show up?
You're working on a Windows 10 or 11 machine, maybe running a backup job, a disk cleanup tool, or even just trying to delete a folder and bam—you get the blue screen or an app crash with ERROR_INVALID_REPARSE_DATA (0x00001128). The exact message reads: The data present in the reparse point buffer is invalid.
One real scenario: last month I had a client whose Veeam backup agent kept failing on their Windows Server 2019 box. Every time it tried to snapshot the C: drive, it threw this error. Turns out, a symbolic link created by an old Dropbox install had gone rotten.
Another common trigger: you try to open a folder in Explorer and get an Access Denied or File Not Found error, even though the folder shows up fine in dir. That's your reparse point data being corrupt.
What causes this?
Reparse points are special NTFS structures—think symbolic links, junction points, or mount points. They contain metadata that tells Windows what to do when you access that file or folder. If that metadata gets corrupted—from a bad driver, a sudden power loss during a write, or a rogue third-party tool that mucks with filesystem metadata—Windows can't read the reparse data anymore. The result? Error 0x00001128.
The fix: step-by-step
Important: This error is almost always tied to a specific file or folder. Don't run off and reinstall Windows. Let's find the culprit first.
Step 1: Find the corrupted reparse point
Open Command Prompt as Administrator. Then run this command on the volume where the error occurs (adjust the drive letter as needed):
fsutil reparsepoint query C:If you already know the file or folder path, use that instead. For example:
fsutil reparsepoint query "C:\Users\Public\Dropbox"If the reparse point is corrupt, fsutil will return an error like The data present in the reparse point buffer is invalid. Note down that path.
Step 2: Delete the corrupted reparse point
Once you know the culprit, you need to remove it. You cannot just delete it normally because Windows can't even read the metadata. Use the del or rmdir commands with the reparse point flag. If it's a file symlink:
del /F /S "C:\Users\Public\Dropbox"If it's a directory symlink or junction:
rmdir /S /Q "C:\Users\Public\Dropbox"If those fail—and they often do—use the Sysinternals Handle tool to find which process has a lock on it. Download handle.exe from Microsoft, then run:
handle64 -a "C:\Users\Public\Dropbox"Kill that process, then retry the delete.
Step 3: Run a filesystem check
Even after deleting the corrupt point, run chkdsk to clean up any lingering metadata issues:
chkdsk C: /f /rThis will require a reboot. Let it run fully—it might take a while on a large drive, but don't skip it.
Step 4: Recreate the reparse point (if needed)
Sometimes the file or folder was important (like a junction point for a program). Recreate it using mklink or fsutil. Example for a directory symlink:
mklink /D "C:\Users\Public\Dropbox" "D:\Dropbox"If it still fails
Two things to check:
- Antivirus interference: Some AV tools scan reparse points aggressively and can corrupt them. Temporarily disable your antivirus and test the fix again.
- Disk hardware issues: A failing drive can corrupt filesystem metadata. Check your drive's S.M.A.R.T. status with tools like CrystalDiskInfo or
wmic diskdrive get status.
If you still can't delete the reparse point after all that, boot from a Windows PE or Linux live USB and delete it from outside the OS. I've had to do that exactly once in ten years—but it works.