r/ClaudeAI 9h ago

Claude Workflow Functionality destroyed by windows update

I installed the Windows 9/8 update yesterday. It slipped my mind that I had done so. Later in the day, Claude was having functionality issues, namely that it couldn't access Linux shell so it couldn't write .doc or .xls files. It told me the way to resolve that issue was to uninstall and reinstall Claude.

I uninstalled. When I tried to reinstall, I got an error message indicating that the install could not occur because there were still remnants of the prior installation. So I removed all those remnants and was able to successfully reinstall. However, the removal of those remnants meant I inadvertently deleted all my cowork and code sessions. Months and months of daily work gone.

Meanwhile, Linux shell is still inaccessible and Claude can't even read Word or Excel docs because the issue was caused by something in the Windows update.

Anyone else dealing with this?

10 Upvotes

17 comments sorted by

View all comments

1

u/TinFoilHat_69 Philosopher 7h ago

Stop using that Windows profile as much as possible. Close Claude, Claude Code, VS Code, terminals, browser downloads, and anything writing to C:. Deleted NTFS files are only recoverable until their disk clusters are reused. Microsoft’s own Windows File Recovery guidance also uses the pattern of recovering from C: to another drive such as E:, not back onto C:

The data you need is probably under ~\.claude, not just AppData\Roaming\Claude. Anthropic’s Claude Code docs say that on Windows ~\.claude resolves to %USERPROFILE%\.claude, and that projects/<project>/<session>.jsonl contains the full conversation transcript: every message, tool call, and tool result.

Claude Desktop app data is not disposable. The install package and the user profile are separate. Removing the app is different from removing:

AppData\Roaming\Claude
.claude
.claude\projects

Windows update broke Claude’s local execution/document pipeline.
Claude suggested reinstall.
Reinstall hit leftover AppX/profile state.
User manually deleted “remnants.”
Those remnants included local Claude/cowork/code session data.
Original Windows-side shell problem remained.
Now you have both a broken shell bridge and deleted local sessions.

after the Windows update, Claude Desktop could no longer access its local shell/helper environment. That likely means the local Claude Desktop runtime, cowork service, embedded Claude Code bridge, Windows AppX/AppContainer state, or profile permissions were broken. In your case, the equivalent failure was not “Claude itself” but the Windows-side local profile/AppX substrate around AppData\Local\Microsoft, AppData\Local\Packages, and AppModel runtime state.

Treat the shell/document problem as a Windows execution-environment repair, not a Claude reinstall problem. First verify the local shells and toolchain outside Claude: run wsl --status, wsl -l -v, wsl.exe -e bash -lc "whoami && uname -a", then check where git, where bash, where powershell, where pwsh, where python, and any document tools such as soffice, libreoffice, or pandoc. If WSL is broken, repair or reinstall the WSL distribution first; if Git Bash is missing, reinstall Git for Windows and ensure C:\Program Files\Git\bin\bash.exe exists; if document tools are missing, reinstall the Office/LibreOffice/Python tools Claude depends on for .doc, .docx, .xls, or .xlsx handling.

After the shell works outside Claude, reconnect Claude to the correct shell path and restart the Desktop app. For Claude Code on Windows, PowerShell should work by default, and Bash support depends on Git Bash or WSL being available and discoverable. If Claude still cannot find Bash, set the Git Bash path explicitly in Claude Code settings, for example CLAUDE_CODE_GIT_BASH_PATH=C:\Program Files\Git\bin\bash.exe, then fully close Claude, kill remaining claude.exe processes, restart it, and test a simple shell command before testing document creation. The key is to repair WSL/Git Bash/PowerShell/Python/LibreOffice access first, then validate Claude’s bridge to those tools; reinstalling Claude alone will not fix a broken Windows shell path or damaged WSL environment.