Fix NTFS 0XC0000281: Directory is a Reparse Point

Quick answer: Run fsutil reparsepoint delete "C:\Path\To\Folder" as admin, then delete the folder normally.

This error shows up when a directory is marked as a reparse point—think of it as a shortcut that's supposed to point somewhere, but the target is gone or corrupted. I've seen this most often with OneDrive stubs that got disconnected during a sync conflict, or after restoring a folder from a backup that didn't preserve the reparse data. A client last month had this on a shared drive after a botched migration from Dropbox to local storage. The folder looked normal in Explorer, but any attempt to open it—even trying to delete it—threw error 0XC0000281. The root cause is always the same: the reparse tag is still attached to the directory entry, but the link data is missing or invalid.

What's actually happening under the hood

NTFS allows folders to wear a "reparse point" tag. This tag tells Windows: "Hey, don't treat this like a normal folder—run a specific filter driver to interpret it." Common uses: symbolic links, junction points, OneDrive placeholder files, or third-party cloud sync stubs. When the filter driver can't resolve the link (maybe the target was deleted, or the driver's corrupted), the OS returns 0XC0000281. The folder is still there, but it's essentially in limbo.

Fix steps (do these in order)

Open Command Prompt as Administrator. Hit Start, type cmd, right-click it, and choose "Run as administrator."
Identify the exact path. Navigate to the folder's parent. For example, if the broken folder is D:\Projects\OldSync\, note the full path. Use double quotes if there are spaces.
Delete the reparse point. Run:
```
fsutil reparsepoint delete "D:\Projects\OldSync"
```
If it succeeds, you'll see "Reparse point data deleted successfully." If it fails with "Access denied," you're not running as admin—double-check that.
Now delete the folder. The folder should now behave like a regular directory. Try:
```
rmdir /s /q "D:\Projects\OldSync"
```
If that still fails, use del /f /s /q on any files inside first.
If the folder won't go away: Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4). Repeat steps 1-4 in Safe Mode.

Alternative fixes (when the main one doesn't work)

Use the Sysinternals Handle tool

Sometimes a process is locking the reparse point. Download Handle from Microsoft, then run:

handle -a "D:\Projects\OldSync"

Kill the PID that's holding the handle (taskkill /f /pid [PID]), then retry the fsutil command.

Robocopy to wipe the folder

Create an empty folder, say C:\Empty. Then run:

robocopy C:\Empty "D:\Projects\OldSync" /mir

This mirrors the empty folder over the broken one, effectively erasing it. It often bypasses reparse point restrictions.

Third-party tool: LockHunter

If you're stuck, LockHunter (free) can force-delete a folder and its reparse tags. Right-click the folder, choose "What's locking this folder?", then "Delete it." It works on Windows 10 and 11.

Prevention tip: avoid broken cloud sync stubs

The main cause of this error is incomplete cloud sync setups. If you're using OneDrive or Dropbox with placeholder files ("Files On-Demand" or "Smart Sync"), make sure you fully sync before disconnecting or switching providers. When you disconnect, the stubs turn into dead reparse points. I always tell clients: before removing a sync folder, right-click it, choose "Free up space" or "Make available offline" first, then wait for sync to finish. Also, never restore a synced folder from a backup that wasn't taken with the sync software running—those stubs will break immediately.

If you see this error on a system drive (e.g., C:\Users\...), consider running chkdsk c: /f after fixing the reparse point, just to clean up any leftover corruption. But 9 times out of 10, the fsutil command alone solves it.