-
Notifications
You must be signed in to change notification settings - Fork 848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Only 2.1.5.0] Error code: Wsl/Service/CreateInstance/MountVhd/HCS/E_ACCESSDENIED #11323
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
/logs |
same problem |
Same problem, downgrading didn't help UPD1: Update to 2.2.4 helped |
I have the same problem: Failed to attach disk 'D:\Development\Ubuntu2204\ext4.vhdx' to WSL2: Access is denied. WSL version: 2.1.5.0 Please help |
i solved: |
I had the same problem, and was able to just grant full control to "Hyper-V Administrators" for the VHD itself to fix this issue. A little less invasive then granting everyone permissions to the entire drive. |
Windows Version
10.0.19045.4170
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
0.15.146.1-2
Distro Version
Ubuntu 22.04 (from imported vhdx)
Other Software
Both Docker and my own distro
Repro Steps
Update from an old WSL version to 2.1.5.0, then starting any of WSL distros will get the Error code:
Wsl/Service/CreateInstance/MountVhd/HCS/E_ACCESSDENIED
Downgrading to 2.1.4.0 fully solved it.
Here is another report on StackExchange(not mine) that is same as my issue and is consistent with my solution
Expected Behavior
Run successully
Actual Behavior
Error code: Wsl/Service/CreateInstance/MountVhd/HCS/E_ACCESSDENIED
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: