# Recent Cursor update breaks WSL remote — “File system provider … not available” / “VS Code Server for WSL closed unexpectedly” **URL:** \ **Category:** Bug Reports\ **Created:** [May 16, 2025, 3:16am UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443 "2025-05-16T03:16:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![QuicksilverSlick](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/quicksilverslick/32/54799_2.png) [@QuicksilverSlick](https://forum.cursor.com/u/QuicksilverSlick)\ **Post date:** [May 16, 2025, 3:16am UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443/1 "2025-05-16T03:16:27Z")
Here’s the updated bug report, now including **every** step we’ve tried so far: * * * ## Bug Report: Cursor → WSL Ubuntu fails to reconnect (“VS Code Server for WSL closed unexpectedly”) **Cursor Version:** 0.50.4 (user setup) **VS Code Version:** 1.96.2 (Commit 8ea935e…) **Electron/Chromium/Node:** 34.3.4 / 132.0.6834.210 / 20.18.3 **OS:** Windows 10 Pro (10.0.19045) on “QUICKSILVER” (Intel i9-12900K, 128 GB RAM) **Default WSL Distro:** Ubuntu (WSL 2) ### 🐞 Description After updating Cursor, opening a new WSL:Ubuntu window shows the Ubuntu filesystem in the tree, but _any_ attempt to open a project folder immediately fails with: ```auto File system provider for vscode-remote://wsl+ubuntu/home/dreamforge is not available. VS Code Server for WSL closed unexpectedly. Check WSL terminal for more details. ``` ### 🧪 Steps We’ve Tried 1. **Confirmed WSL health** 2. **Ensured Node & npm installed in WSL** 3. **Installed Claude Code CLI into user‐local prefix** 4. **Removed stale global installs** 5. **Launched project from WSL** 6. **Installed Microsoft’s Remote-WSL extension** 7. **Set Ubuntu as default WSL distro** 8. **Removed any Docker-Desktop WSL integration** 9. **Restarted everything repeatedly** 10. **Verified environment variables** * * * ### ➕ **Additional Steps** We Just Tried 1. **Deleted `~/.cursor-server`** 2. **Reinstalled WSL extension in Cursor** 3. **Performed a clean Cursor reinstall** 4. **Unregistered & reinstalled Ubuntu** 5. **Checked Alpine dependencies error** * * * ### 🔄 Reproduction 1. Open Cursor → click **Remote WSL: Ubuntu** (or open folder under `\\wsl$\Ubuntu\home\dreamforge…`). 2. The window loads but immediately shows “File system provider … is not available” and refuses to mount files. ### 📷 Screenshots & Logs _(Attached in the ticket)_ - The “Attempting to reconnect…” dialog - The Alpine dependency error for libstdc++ - Full `$PATH` dump - `wsl --list --verbose` output - System Info (Windows 10 Pro, 19045, 128 GB RAM) * * * ### 🚫 Impact Cursor is unusable for WSL-based projects, blocking all editing/testing workflows inside Ubuntu. * * * If there’s any other diagnostic you’d like us to capture—logs, config files, or a Screen­Cast—just let us know. Thanks for looking into this! ![same error even in wsl ubuntu](https://us1.discourse-cdn.com/cursor1/original/3X/b/e/be65c833ffd3c4b4f38162fdecff69d0a4ebf9ab.png) ![got this error when opening a new remote wsl window](https://us1.discourse-cdn.com/cursor1/original/3X/a/9/a98d34d81003113b17d312d27748cc7636654282.png) ![it wont connect for me to try the cinfirm wsl is alive](https://us1.discourse-cdn.com/cursor1/original/3X/a/a/aa3f45a19e43190eda8ef6be8555da0823cefd78.png) ---
**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\ **Post date:** [May 16, 2025, 11:50pm UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443/2 "2025-05-16T23:50:37Z")
Hi! Could you try switching to the Anysphere Remote WSL extension? You can find it by searching for `@id:anysphere.remote-wsl` (attaching a screenshot). Please share whether this works for you! ![image](https://us1.discourse-cdn.com/cursor1/original/3X/0/7/07e9cf4438218cc0d60d1f6a916a25fd644923a6.png) ---
**Author:** ![QuicksilverSlick](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/quicksilverslick/32/54799_2.png) [@QuicksilverSlick](https://forum.cursor.com/u/QuicksilverSlick)\ **Post date:** [May 20, 2025, 11:25am UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443/3 "2025-05-20T11:25:44Z")
I will try this. What make sit different? ---
**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\ **Post date:** [May 20, 2025, 3:31pm UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443/4 "2025-05-20T15:31:23Z")
We’ve been getting a # of reports about connection issues with the VSCode Remote extensions, so we rebuilt them from the ground up. The functionality itself should be the same as before, but the connection (and reconnection) logic is improved and more robust. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [June 19, 2025, 3:32pm UTC](https://forum.cursor.com/t/recent-cursor-update-breaks-wsl-remote-file-system-provider-not-available-vs-code-server-for-wsl-closed-unexpectedly/92443/5 "2025-06-19T15:32:04Z")
Closed on June 19, 2025, 3:32pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.