Fix NTFS error 0xC0000275 file not a reparse point

This error means Windows can't access a file or folder because it's missing its reparse point tag. It usually happens after a failed move, a corrupt junction, or a bad symbolic link. Here's how to fix it.

What’s going on with error 0xC0000275?

You try to open a file or folder, and Windows throws back the error: "The file or directory is not a reparse point" with code 0xC0000275. This happens when Windows expects a special tag—called a reparse point—on a file or folder, but that tag is missing or corrupted.

Reparse points are used for things like symbolic links, junctions, mount points, and OneDrive's placeholder files. When the tag gets stripped—maybe after moving a folder, a failed OneDrive sync, or a disk error—Windows can't read the normal file data underneath.

I've seen this most often after someone tries to copy a junction folder with a tool that doesn't understand reparse points, or after a OneDrive "Files On-Demand" hiccup. The file itself is still there, but the metadata that tells Windows how to treat it is broken.

Let's walk through the fixes, from simplest to most involved. Stop when your file becomes accessible again.

Quick 30-second check: Restart Explorer or reboot

Sometimes the error is a temporary glitch in the shell. Before you dig deeper, do this:

Press Ctrl+Shift+Esc to open Task Manager.
Find Windows Explorer in the list.
Right-click it and choose Restart.
After the desktop refreshes, try accessing the file again.

What you should see: The file or folder opens normally. If not, restart your computer completely. A full reboot clears cached file handles and can fix transient reparse point issues. If the error persists, move to the next section.

5-minute moderate fix: Use fsutil to delete or recreate the reparse point

This fix works when the file or folder has a partial reparse point—meaning Windows sees it as special, but the tag is too damaged to read. The tool fsutil can strip that broken tag and let you delete or access the file.

Warning: This permanently removes the reparse point. If this was a symbolic link or junction, the link itself is gone. The underlying data (if any) stays intact, but the special behavior is lost.

Here's how:

Open Command Prompt as Administrator. Press Win+X and choose Command Prompt (Admin) or Terminal (Admin).
If you get a User Account Control prompt, click Yes.
Run this command, replacing C:\path\to\problem\file with the actual path to the item giving the error:
```
fsutil reparsepoint delete "C:\path\to\problem\file"
```
Press Enter. What you should see: A message saying "The operation completed successfully" or "Reparse point deleted." If you see an error about access denied or the command not recognizing the file, proceed to the advanced fix below.
Now try to open or delete the file normally. In most cases, it will behave like a regular file or folder again.

If fsutil fails with "The file or directory is not a reparse point"—yes, the same error—that means Windows can't even see the reparse point metadata. That's when you need the advanced fix.

Advanced fix (15+ minutes): Use chkdsk or third-party tools

When the file metadata is so corrupted that even fsutil can't touch it, you have two options: let chkdsk try to fix the file system, or use a tool like LockHunter or Unlocker to force-delete the file.

Option A: Run chkdsk on the drive

This is the safer path. chkdsk scans the drive's Master File Table (MFT) and can repair orphaned or mismatched reparse points. It can also find and fix bad sectors that might have caused the corruption.

Open Command Prompt as Administrator.
Type this, replacing D: with the letter of the drive where the problem file lives:
```
chkdsk D: /f /r
```
Press Enter. If the drive is in use (usually C: is), it'll ask to schedule a scan at next reboot. Type Y and press Enter, then restart your computer.
Let chkdsk run. It can take 15 minutes to an hour on large drives. What you should see: Messages like "Repairing corrupt reparse point records" or "Correcting errors in the MFT." When it finishes, reboot again.
Try accessing the file. Often chkdsk will have fixed the reparse point or converted the item back to a normal file.

Option B: Force-delete with a third-party tool

If chkdsk didn't help, or you just want the file gone, use LockHunter (free, no ads). This tool can delete files that Windows says are locked or corrupted, even with reparse point errors.

Download and install LockHunter from lockhunter.com.
Right-click the problem file or folder in File Explorer.
Choose What is locking this file? from the context menu.
In LockHunter's window, click Delete It! in the bottom right.
Confirm the deletion. What you should see: A message saying the file was deleted or will be deleted on reboot. If it says it will delete on reboot, restart your computer.

After the file is gone, you can recreate it or restore it from backup. I've used LockHunter dozens of times on broken reparse points that chkdsk and fsutil couldn't touch. It works because it bypasses normal file I/O and directly manipulates the MFT entry.

What if none of this works?

If the error still appears after all three fixes, the file system may have deeper corruption. Back up any important data from the drive immediately, then consider reformatting the drive. That's the nuclear option, but it guarantees the reparse point problem is gone.

For what it's worth, I've only seen that once—on a drive that was physically failing. Run a SMART test with CrystalDiskInfo or HD Tune to check the drive's health. If you see yellow or red warnings, replace the drive.

You don't have to be a filesystem expert to fix this error. Start with the quick reboot, try fsutil, and if that fails, let chkdsk or LockHunter do the heavy lifting. One of these steps will get your file back.