Windows long-path delete failures: DeepSeek Harness

Windows cannot delete dsh node_modules mainly because the path exceeds MAX_PATH 260: DeepSeek Harness profile dependencies live inside node_modules, which is deep and long, and combined with the project directory it goes over, so deletion reports path too long / path not found / directory not empty (source).

This guide covers three steps: why deletion fails, four ways to break through in order, and verifying plus preventing it. Per-platform leftover locations are in DeepSeek Harness uninstall paths by platform; this article focuses on Windows long-path delete failures.

Windows cannot delete dsh node_modules: MAX_PATH 260 and deep directories

The traditional Windows path limit is MAX_PATH 260 characters; DeepSeek Harness profile dependencies live inside node_modules, whose path is already long, and combined with user directories and nested projects it easily goes over, so deletion fails (source).

Confirm it is a long path issue first:

1. Read the error message — "path too long", "path not found" or "filename or extension too long" point to long paths. Expected: the long-path direction is set.
2. Measure the path length — Paste the target path into a text editor and count; over 260 means it exceeds the limit. Expected: the exact over-limit directory is identified.
3. Check whether long paths are enabled — Run reg query "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled. Expected: a value of 0x1 means enabled, 0x0 or missing means not.
4. Check for a directory-not-empty error — Sometimes it reports "the directory is not empty". Expected: this is the long path preventing the delete from recursing all the way down; same root cause.

Step 3's result decides the route: with long paths enabled, delete directly from the deep directory first; without it, either enable long paths or go straight to the mirror method that does not depend on long paths.

Four ways to break through the Windows long-path delete limit

The four routes go from cheapest to costliest: enable LongPathsEnabled, delete deepest-first, mirror an empty directory with robocopy /MIR and delete, then rename to shorten the path; robocopy's mirror processes items one by one and is not bound by one long path (source).

Try them in order, each with a verifiable expectation:

1. Enable long paths — In an elevated terminal run reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /f, then restart the process or system. Expected: long-path-aware apps handle paths over 260 characters and rd /S /Q deletes deep directories.
2. Delete deepest-first — Navigate into the deepest subdirectory in Explorer or a terminal and delete inward out, keeping each path segment short. Expected: after emptying layer by layer, upper paths shorten and become deletable.
3. Mirror an empty directory with robocopy — Create an empty directory, run robocopy <empty-dir> <target-dir> /MIR, then rmdir /S /Q <target-dir>. Expected: the mirror empties the target and the now-empty directory deletes successfully.
4. Rename to shorten the path — Rename a middle parent directory to a 1-2 character name. Expected: the whole path shortens markedly and deletes right after.

Step 3 is the most universal fallback: robocopy /MIR compares source and target item by item and removes extra files and subdirectories in the target, working with relative paths rather than being bound by one long path in a command-line delete, so it clears what rd cannot. Step 4's rename is a "physical shortening" of the path, simple and direct for a single remaining long directory.

Verifying the delete and preventing a repeat

After deleting, confirm the directory is truly gone and consider putting $DSH_HOME on a short path; placing the data root in a short drive-root directory and avoiding deeply nested projects greatly reduces triggering the 260 limit again (source).

Finish in order:

1. Confirm the directory is gone — Run dir or check Explorer for the target directory. Expected: it is gone with no leftovers.
2. Check parent directories — Walk upward for empty leftover directories. Expected: empty scoped directories are cleaned too.
3. Reinstall on a short path — If moving the data root to a short path, complete the migration first. Expected: node_modules additions stay far from the 260 limit.
4. Reinstall plugins and check — Return to the DSH Plugin Hub installed list to reinstall as needed. Expected: plugins are restored and no delete failure recurs.

Step 3 is the cure: the path problem is not a flaw in the delete method but a structural cause — the path is simply too long. Keeping $DSH_HOME on a short path and projects in shallow directories beats working around it on every delete.

Notes on deleting long-path dsh directories on Windows

1. Confirm it is a long path: path too long, path not found, directory not empty with a path over 260 all point to it.
2. Order methods by cost: enable long paths, delete deepest-first, robocopy mirror, then rename.
3. robocopy is the universal fallback: /MIR an empty directory to empty the target, then delete the shorter directory.
4. Renaming is powerful: shrink one middle directory name and the whole path shortens immediately.
5. Short paths cure it: keep $DSH_HOME and projects in shallow directories to reduce repeats.

After cleaning leftovers, use the DSH Plugin Hub installed list to reinstall plugins on demand, more reliably than pulling a pile of dependencies by hand.

Sources: Microsoft Docs: Maximum Path Length Limitation, Microsoft Docs: robocopy, DeepSeek Harness CLI README (official repository)