Windows 11 Update Breaks Linux File Sharing and Claude Cowork
A recent security patch has disrupted critical file sharing features for developers and AI users, leaving many without a working solution.
A recent security update for Windows 11 has introduced a significant disruption for developers and users of artificial intelligence tools. The patch, identified as KB5124008, interferes with how the operating system shares folders between Windows and virtual Linux environments. This interference prevents essential applications from accessing necessary files, effectively halting workflows that rely on this cross-platform connectivity.
The issue specifically targets Plan9 host folder shares, a mechanism that allows virtual machines to read and write data to the host system. When these shares fail to mount, applications that depend on them throw errors indicating that no drives are available. As reported by XDA Developers, this single update has simultaneously broken two popular tools: the Windows Subsystem for Linux and Claude Cowork.
Core file sharing mechanisms fail
Plan9 is a protocol used to share files between a host operating system and guest virtual machines. For many users, this is the bridge that allows Linux-based tools to interact with Windows files seamlessly. The latest update appears to have broken this bridge, causing shared folders to become invisible to the virtual environment. This is not a minor glitch; it stops the fundamental data transfer that these applications require to function.
Popular development tools are affected
The Windows Subsystem for Linux, often used by software engineers to run Linux commands directly within Windows, is one of the primary victims. Without access to shared folders, the subsystem cannot read project files or configuration data. Claude Cowork, an AI collaboration tool, faces a similar fate. Both applications display errors stating that no Plan9 drive shares are mounted, rendering them unusable for tasks that depend on local file access.
No immediate workaround exists
Microsoft has acknowledged the problem by listing it on its official known issues page for Windows 11 version 25H2. However, the company has not released a patch to fix the error, nor has it provided a manual solution for users to resolve the issue on their own machines. This leaves affected users in a limbo where they must wait for a future update. The lack of a temporary fix means that productivity losses are inevitable until Microsoft ships a correction.
