WSL: Cannot access Dev Drive files from WSL2 after Windows Update

Windows Version

Microsoft Windows [Version 10.0.26100.2152]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 24.04

Other Software

WSL version: 2.3.24.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2152

Repro Steps

For months I’ve been running WSL2/Ubuntu, and accessing folders on my Win11 Dev Drive through VS Code Remote.

My Win11 laptop rebooted last night, and then today I can’t access anything on that Dev Drive through VS Code/WSL2 Remote.

I’ve tried uninstalling the distro and reinstalling; tried remounting the drive… nothing works.

I see some older bugs similar to this, but they have been closed with no solution.

Expected Behavior

Same access to Dev Drive files using VS Code/WSL2.

Actual Behavior

My d: drive (Dev Drive) is no longer accessible through VS Code/WSL2.

Looking at the mounts, the d: drive is obviously messed up.

kirk@DEV-USSEASUR6:/mnt$ ls -l
total 0
drwxrwxrwx 1 kirk kirk 4096 Oct 11 15:28 c
d--------- 0 kirk kirk    0 Dec 31  1969 d
drwxrwxrwt 2 root root   60 Oct 11 16:13 wsl
drwxrwxrwt 7 root root  300 Oct 11 16:14 wslg

Here’s my wsl.conf:

kirk@DEV-USSEASUR6:/mnt$ cat /etc/wsl.conf
[boot]
systemd=true

Diagnostic Logs

Image

VS Code logs:

[2024-10-11 23:28:43.545] Extension version: 0.88.4
[2024-10-11 23:28:43.546] L10N bundle: none
[2024-10-11 23:28:43.575] authorityHierarchy: wsl+ubuntu
[2024-10-11 23:28:43.575] WSL extension activating for a local WSL instance
[2024-10-11 23:28:43.591] Resolving wsl+ubuntu, resolveAttempt: 1
[2024-10-11 23:28:43.591] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --status
[2024-10-11 23:28:43.638] WSL feature installed: true (wsl --status)
[2024-10-11 23:28:43.638] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --list --verbose
[2024-10-11 23:28:43.679] 1 distros found
[2024-10-11 23:28:43.680] Starting VS Code Server inside WSL (wsl2)
[2024-10-11 23:28:43.680] Windows build: 26100. Multi distro support: available. WSL path support: enabled
[2024-10-11 23:28:43.680] Scriptless setup: false
[2024-10-11 23:28:43.680] No shell environment set or found for current distro.
[2024-10-11 23:28:43.776] WSL daemon log file: 
[2024-10-11 23:28:43.778] Connecting to daemon started by other WSL window... 5.15.153.1-microsoft-standard-WSL2 Ubuntu
[2024-10-11 23:28:43.778] WSL resolver response: 127.0.0.1:51854
[2024-10-11 23:28:43.778] To debug connection issues, open a local browser on http://127.0.0.1:51854/version
[2024-10-11 23:28:43.792] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e /home/kirk/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '127.0.0.1', port: 34255 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-11 23:28:43.868] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e /home/kirk/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '127.0.0.1', port: 34255 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-11 23:28:44.090] Download in background is enabled

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 17
  • Comments: 36 (1 by maintainers)

Most upvoted comments

Omg, seriously guy, can we stop the +1 ? It is not helping. Tap on the emoji or the subscribe button will do!

Hi folks, thank you for the logs and feedback! We have investigated this error and believe we have found an initial fix for it. We’re looking at when and how we can service this out, and I will keep this thread up to date with any news once it’s available. Thank you!

To provide an update on this issue:

A recent bug was discovered that prevents access to Dev Drives from within WSL. The issue impacts the following updates:

• Windows 11 WIP Release Preview update KB5044384 (build 26100.2152) • Windows 11 WIP Dev update KB5044374 (build 26120.2122) and KB5044400 (build 26120.2130)

For users that have recently updated to the retail release of Window 11 24H2 (10.0.26100), we recommend you turn OFF “Get the latest updates as soon as they’re available.

If your system is impacted by this bug, your data will not accessible from within WSL. The dev drives and data are accessible from Windows.

The workaround is to uninstall the update, and turn off Updates until this is fixed.

A fix has been identified will be released in an upcoming servicing update.

I am also experiencing the same sudden loss of drive access. I’ve even created a new DevDrive to no avail. When I do a directory listing in /mnt it shows odd permissions:

barrettg@BARRETT-CORSAIR:/mnt$ ls -lh
total 0
drwxrwxrwx 1 barrettg barrettg 4.0K Oct 13 09:51 c
d--------- 0 barrettg barrettg    0 Dec 31  1969 d
d--------- 0 barrettg barrettg    0 Dec 31  1969 e
drwxrwxrwt 5 root     root      120 Oct 13 09:51 wsl
drwxrwxrwt 7 root     root      300 Oct 13 09:51 wslg

d and e being DevDrives. If I sudo su to the root user, I can access the mounts. I’ve tried changing the permissions and it makes no difference.

As @MatthewSteeples and @johnnykang mentioned, this is fixed in the latest update to 24H2 - KB5046617 (OS Build 26100.2314)

FYI - for folks on the Windows Insiders Dev Channel - the fix is in the latest flight 10.0.26120.2213.

https://blogs.windows.com/windows-insider/2024/11/04/announcing-windows-11-insider-preview-build-26120-2213-dev-channel/

@PhotoAtomic Looks like it’s today!

Upgraded and fixed

A fix has been identified will be released in an upcoming servicing update.

@AdamBraden is there any target date for the servicing update?

stumbled into this myself today DevDrive not accessible through WSL2, nor docker desktop “Access Denied”