# Quick summary
# Why this happens WSL 2 runs inside a lightweight VM. Windows exposes Linux files through special network-style paths like \\wsl.localhost and \\wsl$. If a Windows update alters WSL services, disables virtualization features, or leaves processes in a bad state, the Explorer integration or Claude's trusted-folder connection can break while the distribution itself remains intact.
# Step-by-step fixes you can try now 1) Check whether Windows still recognizes your distribution
- Open PowerShell or Windows Terminal and run: wsl --list --verbose
- If your distro appears (Ubuntu, Debian, etc.) your files are likely safe. Don't unregister or reinstall yet.
- Run wsl --shutdown to stop WSL and its VM, then start a distro again. This forces services to reinitialize.
4) Update WSL after the Windows update
- Confirm wsl --version and run the WSL update command if available. An outdated WSL package after a Windows update can cause Explorer integration problems.
- Instead of relying on the Linux sidebar, try accessing \\wsl.localhost\ or \\wsl$\ directly in File Explorer to verify visibility.
- From your distro, confirm Windows drives are still mounted at /mnt/c etc. If mounts are missing, restart WSL and check Windows-side settings.
8) Reconnect the folder in Claude Desktop
- If Claude lost access to a previously trusted folder, re-add or reconnect that folder inside Claude's storage/trusted folders UI.
9) Check Claude Desktop updates and VM state
- Ensure the Claude Desktop client is updated. If Claude uses a local VM image, a restart or local VM state reset (via Claude UI options) can restore access without reinstalling.
10) Verify Windows virtualization features and hardware virtualization
- Confirm Virtual Machine Platform is enabled in Windows Features and that CPU virtualization (VT-x / AMD-V) is enabled in firmware. Some updates can unset or break these components.
# What to avoid
- Don't immediately unregister or reinstall WSL distributions. If wsl --list shows your distro, your files remain present and these targeted steps usually restore visibility.
# When to escalate If these steps fail after checking WSL status, Virtual Machine Platform, and Claude's trusted-folder settings, consider capturing exact error messages, checking Windows Update details for known regressions, or consulting Claude Desktop support with logs showing the missing-folder behavior.