How to Fix Claude Cowork or WSL Shared Folders Missing After Windows Update

If Claude Cowork suddenly cannot access your project folders, or your WSL folders disappear from Windows File Explorer after a Windows update, the problem usually comes from WSL services, Windows virtualization components, Explorer integration, or Claude Desktop losing access to a previously trusted folder.

This issue can be particularly confusing because WSL itself may still work perfectly from Ubuntu or another Linux terminal while \\wsl.localhost, the Linux section in File Explorer, or folders previously available to Claude are missing. Fortunately, reinstalling Ubuntu or deleting your WSL distribution is rarely necessary.

This guide explains how to fix Claude Cowork or WSL shared folders missing after a Windows update using safe troubleshooting steps for current Windows 11, WSL 2, and Claude Desktop installations.

Why Are Claude Cowork or WSL Shared Folders Missing?

WSL 2 runs Linux distributions inside a lightweight virtualized environment. Windows exposes those Linux files to File Explorer through special paths such as \\wsl.localhost and \\wsl$.

Claude Desktop can also work with local folders that you explicitly allow it to access. If a Windows update changes the state of WSL, virtualization services, Explorer integration, or the path Claude previously trusted, those folders may temporarily disappear.

Common causes include:

• WSL services not starting correctly after the Windows update.
• An outdated WSL package after Windows itself was updated.
• The Linux distribution being stopped.
• File Explorer losing its WSL navigation integration.
• Virtual Machine Platform being disabled or incorrectly registered.
• Claude Desktop losing access to a previously connected folder.
• The WSL folder path changing or becoming unavailable while Claude starts.
• A corrupted WSL or Claude Desktop process remaining active after the update.

The important thing is to determine whether the issue comes from WSL itself, Windows File Explorer, or Claude Desktop before making major changes.

1. Check Whether Your WSL Distribution Still Exists

Start by confirming that Windows still recognizes your Linux installation. Open PowerShell or Windows Terminal and run:

wsl –list –verbose

You should see something similar to Ubuntu, Ubuntu-24.04, Debian, or whichever distribution you previously installed.

The output also shows whether the distribution is running or stopped and whether it uses WSL 1 or WSL 2.

If your distribution appears normally, your Linux files are probably still intact. Do not reinstall or unregister the distribution just because it disappeared from File Explorer.

You can also check the overall WSL configuration with:

wsl –status

Then check the installed WSL component version:

wsl –version

2. Start WSL Manually

The \\wsl$ path normally depends on a WSL distribution being active. After some Windows updates or restarts, the distribution may simply remain stopped until it is launched.

Open Windows Terminal and run:

wsl

Alternatively, start a specific distribution:

wsl -d Ubuntu

Replace Ubuntu with the exact name shown by wsl –list –verbose.

Once the Linux terminal opens, leave it running temporarily and open File Explorer.

Enter this in the address bar:

\\wsl.localhost

You can also try:

\\wsl$

If your Linux distribution appears here, WSL is working and the problem is probably limited to File Explorer integration or Claude’s folder permissions.

3. Restart WSL Completely

A Windows update can leave the lightweight WSL virtual machine in an unusual state. Restarting only the Ubuntu terminal does not necessarily restart the underlying WSL environment.

Close Linux terminals and run this from PowerShell:

wsl –shutdown

Wait a few seconds and then launch WSL again:

wsl

Now reopen:

\\wsl.localhost

This simple restart fixes many cases where WSL folders disappear even though the distribution is still installed.

4. Update WSL After the Windows Update

Windows and WSL are updated separately on many current Windows installations. That means Windows can receive a major cumulative or feature update while an older WSL package remains installed.

Microsoft has also addressed File Explorer and WSL integration problems through WSL updates, so updating WSL should be one of the first fixes you try.

Open PowerShell as Administrator and run:

wsl –update

After the update completes, run:

wsl –shutdown

Then restart Windows.

After signing back in, launch your Linux distribution once and check File Explorer again.

5. Open the WSL Folder Directly Instead of Using the Linux Sidebar

Sometimes WSL continues working but the Linux entry in the File Explorer navigation pane appears empty or disappears after a Windows update.

This does not necessarily mean your files are gone.

Press Windows + E and enter:

\\wsl.localhost

If you know the distribution name, you can go directly to it. For example:

\\wsl.localhost\Ubuntu

A typical project might be located at:

\\wsl.localhost\Ubuntu\home\username\projects

Opening the UNC path directly can also cause Windows Explorer to rediscover the WSL distribution and restore the Linux section in the sidebar.

6. Restart Windows Explorer

If WSL works from Terminal and \\wsl.localhost opens correctly but File Explorer still does not show Linux folders properly, restart Explorer.

Press Ctrl + Shift + Esc to open Task Manager.

• Find Windows Explorer.
• Right-click it.
• Select Restart.

File Explorer will briefly close and reload. Try the Linux section again.

This is safer than reinstalling WSL and can fix Explorer shell integration that failed to refresh after an update.

7. Check Whether Windows Drives Are Still Mounted Inside WSL

If your problem is the opposite, where WSL opens but Windows folders such as C: or D: have disappeared inside Linux, check the /mnt directory.

Inside Ubuntu or your Linux terminal, run:

ls /mnt

You would normally see entries such as:

c

d

Your Windows user files should therefore normally be available under a path such as:

/mnt/c/Users/YourName/Documents

If the drives are missing, check your WSL automount configuration.

Run:

cat /etc/wsl.conf

If you previously changed WSL mounting settings, confirm that automount has not been disabled. Windows fixed drives are normally mounted automatically under /mnt.

After correcting a configuration problem, run wsl –shutdown from Windows before reopening the distribution.

8. Reconnect the Folder in Claude Desktop

If WSL folders work normally in File Explorer but Claude Cowork cannot see a project that previously worked, the problem may be Claude’s folder permissions rather than WSL.

Claude only reads and writes local folders that you have explicitly connected or trusted. Reconnect the project folder instead of assuming Claude can automatically access every directory on your computer.

Open the latest Claude Desktop application and check the local folder or project settings. Depending on the version you have, connected folders may appear under Trusted folders, project settings, or local file permissions.

Remove the inaccessible entry if necessary and add the folder again.

If your project is inside WSL, browse to it using a Windows-accessible path such as:

\\wsl.localhost\Ubuntu\home\username\project

Make sure the WSL distribution is running before attempting to reconnect the folder.

9. Check Claude’s Storage and Trusted Folders

Claude’s interface has changed significantly during 2026. Anthropic has been gradually combining the separate Chat and Cowork experiences, so some users may no longer see a dedicated Cowork selector.

This does not necessarily mean Cowork capabilities were removed.

In the newer experience, Claude can decide when a request requires task-style capabilities. Local folders previously granted to Cowork can be checked through Claude Desktop settings, including the Storage folder and Trusted folders areas where available.

If a Windows update caused a WSL path to disappear temporarily, Claude may no longer be able to reach that trusted folder until WSL is started again or the folder is reconnected.

10. Make Sure Claude Desktop Is Updated

Current Claude Cowork features on Windows require a recent version of Claude Desktop. Using an outdated build after Windows itself has been updated can introduce compatibility problems involving virtualization and local file access.

Update Claude Desktop to the latest available version and restart the application.

Also completely exit Claude from the system tray before reopening it. Closing only the visible window may leave background processes running.

After restarting Claude, reconnect your WSL folder and test file access again.

11. Check Virtual Machine Platform

Both WSL 2 and Claude’s Windows desktop task environment rely heavily on Windows virtualization technologies. A feature update can occasionally leave virtualization components disabled or improperly initialized.

Search Windows for:

Turn Windows features on or off

Make sure Virtual Machine Platform is enabled.

If WSL itself is affected, also verify that Windows Subsystem for Linux remains enabled.

You can check Virtual Machine Platform from an elevated PowerShell window with:

Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

If it is disabled, enable it with:

Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -All

Restart Windows afterward.

Use Restart from the Windows power menu rather than simply shutting the computer down and turning it back on. Fast Startup can sometimes prevent virtualization components from receiving a complete fresh initialization.

12. Check Claude Cowork Virtualization Errors

If Claude itself refuses to start Cowork-style tasks or reports virtualization, HCS, HNS, or VM-related errors, check Claude Desktop’s troubleshooting information.

In Claude Desktop, open Help > Troubleshooting > Show Logs if that option is available.

Problems involving services such as vmcompute or hns usually indicate that the underlying Windows virtualization stack is not running correctly.

You can check the relevant services from PowerShell:

Get-Service vmcompute, hns

If Windows cannot find the services even though Virtual Machine Platform should be installed, re-enabling the Windows feature followed by a full restart is generally safer than immediately reinstalling Claude or WSL.

13. Check Whether Hardware Virtualization Is Enabled

If neither WSL 2 nor Claude’s virtualized environment starts after the update, verify hardware virtualization.

Open Task Manager and go to:

Performance > CPU

Look for:

Virtualization: Enabled

If it shows Disabled, virtualization may need to be enabled in your computer’s BIOS or UEFI settings.

Do not randomly change other BIOS settings. Look specifically for options such as Intel Virtualization Technology, Intel VT-x, AMD-V, or SVM Mode.

14. Avoid Unregistering Your WSL Distribution

One of the most important troubleshooting precautions is to avoid running:

wsl –unregister Ubuntu

as an early fix.

Unregistering a distribution removes it from WSL and can delete its Linux filesystem. If important projects live inside /home, you could lose them.

If you eventually decide that reinstalling the distribution is necessary, create a backup first using WSL’s export functionality.

For example:

wsl –export Ubuntu ubuntu-backup.tar

Replace Ubuntu with your actual distribution name.

For most cases involving missing shared folders after a Windows update, updating WSL, restarting it, restoring Virtual Machine Platform, or reconnecting Claude’s trusted folder is enough.

Common Problems and Fixes

WSL Works but Linux Is Missing From File Explorer

Run WSL manually and enter \\wsl.localhost directly in File Explorer. Then restart Windows Explorer if the Linux navigation item remains empty.

\\wsl.localhost Does Not Open

Run wsl –list –verbose and confirm that your distribution still exists. Start it manually, update WSL with wsl –update, and restart WSL using wsl –shutdown.

Claude Cannot See a WSL Project

First confirm that the same directory opens from Windows using \\wsl.localhost. If it does, reconnect the folder through Claude Desktop’s local folder or Trusted folders settings.

Claude Cowork Disappeared From the Interface

This may be expected on newer Claude versions. During the 2026 rollout, Anthropic began combining Chat and Cowork into a single Claude experience for some users. Update Claude Desktop before assuming the feature is broken.

C: Drive Is Missing From Ubuntu

Check /mnt and review /etc/wsl.conf for custom automount settings. Restart WSL after making configuration changes.

WSL Stops Working After Every Restart

Update WSL, verify Virtual Machine Platform, confirm hardware virtualization is enabled, and install pending Windows updates. Persistent failures may indicate a damaged Windows virtualization configuration rather than a problem with the Linux distribution itself.

Frequently Asked Questions

Why did my WSL folders disappear after a Windows update?

A Windows update can restart or modify WSL components, File Explorer integration, virtualization services, or the WSL package itself. Your Linux filesystem usually remains intact even when it temporarily disappears from Explorer.

Where are WSL files visible in Windows 11?

Linux distributions can normally be accessed through the Linux section of File Explorer or through \\wsl.localhost and \\wsl$.

Does wsl –shutdown delete files?

No. The command stops running WSL distributions and the WSL 2 virtual machine. It does not delete your Linux installation or project files.

Should I reinstall Ubuntu if WSL folders are missing?

Usually not. First test wsl –list –verbose, start the distribution manually, run wsl –update, restart WSL, and check \\wsl.localhost. Reinstallation should be a later troubleshooting option.

Can Claude access files stored inside WSL?

Claude Desktop can work with local folders that you explicitly connect and permit it to access. If a WSL directory is exposed to Windows and accepted by the folder picker, it may be accessible through its \\wsl.localhost path. The WSL distribution needs to remain available while Claude accesses those files.

Why can Claude access normal Windows folders but not WSL folders?

This usually means Claude itself is working but the WSL path is unavailable, the distribution is stopped, or the previous trusted-folder permission needs to be recreated. Verify the directory in File Explorer before troubleshooting Claude further.

Final Thoughts

If Claude Cowork or WSL shared folders are missing after a Windows update, avoid immediately reinstalling WSL or unregistering your Linux distribution. In most cases, your files are still present and Windows has simply lost access to the running WSL environment or its Explorer integration.

Start by checking wsl –list –verbose, launching the distribution, opening \\wsl.localhost, updating WSL, and performing wsl –shutdown. If Claude alone cannot access the folder, update Claude Desktop and reconnect the project through its Trusted folders or local folder permissions.

If both WSL and Claude fail, check Virtual Machine Platform and hardware virtualization next. These steps address the underlying Windows virtualization layer while protecting your Linux files and development projects from unnecessary deletion or reinstallation.