dsh-win32

Fix DSH on Windows. No WSL.

Official PowerShell. Workspace Write. One command.

npx dsh-win32 setup

Current DeepSeek Harness already includes persistent PowerShell and a Windows ACL sandbox. dsh-win32 checks that official stack, finds known Windows failures, applies the repairs it can prove safe, and creates a desktop shortcut.

It does not install Git, PowerShell, busybox, WSL, or another DSH bundle on the current path.

Use the standalone CLI above on current DSH. Do not run dsh plugin --profile web add dsh-win32 for this workflow: that installs the legacy bundle, not the current Windows setup path.

中文 · Windows evidence and legacy details

Using a coding agent? Copy the setup and verification request. For a guided walkthrough, see Windows troubleshooting in Chinese.

Start with the Windows first-run walkthrough if DSH will not launch or a check fails. It follows one problem from diagnosis through the next verification step. Share your first-run result, including attempts that are still blocked.

Need to disable or uninstall the old plugin, even when DSH cannot start? See disable / uninstall / remove. From 0.17.14, npx [email protected] disable --profile web previews offline deactivation; after stopping DSH, add --apply to back up the manifest and disconnect only the old bundle.

See the current setup

Reproduced setup flow. This is not a screen recording.

The command checks the official persistent PowerShell and Workspace Write packages, creates the shortcut, and leaves the profile on the stock Minimal preset.

What setup does

• Checks the latest published DSH Windows package contract
• Checks PowerShell 7 and known broken koffi runtimes
• Creates a DeepSeek Harness desktop shortcut for the Web profile
• Leaves the official profile and preset unchanged
• Shows the exact next steps for a first session

After setup, open DSH, add a workspace, choose the stock Minimal preset, and keep Workspace Write enabled.

Use another profile without creating a shortcut.

npx dsh-win32 setup --profile desktop --no-shortcut

--sandboxed remains accepted for old notes and scripts. Current DSH already provides the sandbox, so the flag makes no extra change.

Live verification of an installed stack

From 0.17.12, opt in to setup followed by one installed-stack check:

npx dsh-win32 setup --verify

Use --profile NAME --no-shortcut when appropriate. Ordinary setup is unchanged; --legacy --verify is rejected. Setup and component acceptance are reported separately, and a failed or unsupported verification makes the command exit nonzero. This does not install DSH or prove a complete Desktop/Minimal session. For a check without setup or JSON output, use the standalone command:

npx dsh-win32 verify
npx dsh-win32 verify --json

…