{"version":"2.1.285","anchor":"wsl-mount-table-error-message-reworded","canonical_anchor":"wsl-mount-table-error-message-reworded","heading":"WSL mount table checks: malformed lines block cloud sessions, clearer error text","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/wsl-mount-table-error-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### WSL mount table checks: malformed lines block cloud sessions, clearer error text\n\nOn WSL, a malformed \/proc\/self\/mounts line now blocks cloud sessions until fixed, and the unreadable-mounts error is reworded\n\n**What**\n\nOn WSL (Windows Subsystem for Linux, which runs Linux inside Windows), Claude Code reads the file `\/proc\/self\/mounts` to learn which Windows drives are attached. This release changes how it handles problems with that file:\n\n- A new check spots a line in `\/proc\/self\/mounts` that is incomplete, repeats an option, or names a drive only as its device. Claude Code reports the line number and serves no cloud session until the line is fixed. Before, only a mount table that could not be read at all was reported.\n\n- The existing `mount_table_unreadable` error has new wording. It now says the list of mounted drives could not be read in full, and suggests checking the debug log if it fails again. It used to say it could not read which Windows drives WSL has mounted.\n\n**Why**\n\nIf you use Claude Code on WSL and cloud sessions stop starting, an unusual entry in your mount table may be the cause. The message now points to the exact line to fix, and to the debug log for more detail.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}