Error: 0x80070005 after installing on Win10 Skip Ahead build 17618 #3020
Comments
|
Could you collect logs? https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
|
@benhillis, I believe I'm having the same problem. I've collected the ETL logs. Shall I attach them here, or do you want me to send them to you another way? Problem: attempting to launch Ubuntu on Windows 10 Version 1803 (OS Build 17133.1) fails with "Error: 0x80070005". Repro steps:
Expected results: Prompted to set username and password. Actual results: |
|
Tickle. I have logs for the repro running I also have a repro with logs trying to run |
|
@chwarr, out of curiousity, did you try using |
|
|
|
Good suggestion, @Biswa96: elevated vs. unelevated doesn't appear to matter. The run in my previous comment was unelevated. Here's an elevated run: |
|
Shouldn't need to run elevated for extraction, very odd. Ok so just to verify this isn't a dupe/regression, how about restarting the LXSS service (if you even see it running). What would be ironic is if the issue is simply because all the Store apps updated to use the updated launcher from https://github.com/Microsoft/WSL-distrolauncher. Of course the only way to test that is to manually compile it yourself. |
|
@DarthSpock: I found a service with short name "LxssManager". Restarting that doesn't fix the access denied error. |
|
Just got force upgraded to OS Build 17134.1 and I'm still seeing this behavior. My outstanding offer to send logs or get you access to the machine in question still stands: I just need to know how you'd like me to submit them. |
|
Logs would be useful, here are the instructions: https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
|
I e-mailed the logs to InsiderSupport@microsoft.com. The e-mail contains:
|
|
@chwarr - Thanks for providing the logs. I took a look and it looks like something is blocking access to the lxcore driver. I will follow up with you via email to see if we can diagnose this further. |
|
Turning off device guard, credentials guard and HyperV fixed this issue for me |
|
@GuyGoldenberg - is it possible for you to narrow down which of those three components was causing the issue so I can follow up with them? |
|
I've been consistently seeing this issue, and what I found on my system upgraded to RS4 was that turning off Driver Signature Enforcement via the advanced boot menu made everything work fine (no more permission denied), knowing that, is there anything of a remedy or workaround, at least for this case? I've had the error consistently without hypervisor/device guard/etc enabled at all. I'd really rather not be forced into a reinstall. |
|
@chwarr dropped by my office today and I was able to identify the issue and will be working on a fix to backport to 1803. |
|
@TheGoddessInari any other workaround ? turning off |
|
This is fixed in 17672. We are currently working with the servicing team to get this backported to 1803, bear with us! |
|
The issue is with configurations that have user mode code integrity (UMCI) is enabled via a WDAC policy. |
|
So I didn't have UMCI enabled, are we sure it's not VBS? Believe when i saw this (before I rebuilt w/ 1803) that I only had WDAG and Cred Guard enabled. No WDAC, but possibly could have been in audit mode. |
|
Windows 10.0.17134.81 (1803) |
|
@BeErikk Try this solution #3304 (comment) |
|
@therealkenc Can you reopen this issue? I'm hitting it within Fast Ring. |
|
Can confirm the issue with Hyper-V.
|
|
I still have this problem, and alas now routinely use Cygwin again. I installed via the store, and running "powershell get-cipolicyinfo" gives me ...which looks like I don't have UMCI on. Perhaps a fresh install might work, but some advice on whether I can retrieve my files from the failed disk image would be useful. This would give some assurance in case this were to happen again in future. |
|
I still have this with Debian from Store. Windows 10 Pro C:\Windows\System32\CodeIntegrity\SIPolicy.p7b does not exist Reinstalling Hyper-V didn't help. |
|
A side note for others who encounter this problem; one of the above comments triggered me to the fact that I was trying to install this in a system folder. When I moved it to a user folder it worked fine. For anyone who's trying this that might be an easier solution to test than some of the above. |
|
I just figured out that the following solved the problem for me: Invoke the Since then I can use WSL / |
|
Bizarrely I had this problem again on a different computer with a more recent Windows build and my own solution above didn't work. The new solution was to give my user account full read/write rights to the folder and then, bizarrely, to run bash in a non-administrative window. Apparently my admin rights weren't sufficient for this but once I'd used that admin account to give my non-admin account rights it could then run fine. |
|
I had the same problem with Ubuntu1804.
into
and run ubuntu1804.exe from
The problem is gone. It has been working fine with all kinds of commands. |
|
I'm getting this with a fresh install of 1903 and 1803 with ubuntu 18.04. I don't have the command |
|
I just started getting this today after installing some updates to my Windows 10 1803 (Build 17134) machine. Initially ubuntu just stopped working and reported 80070040 and then when I tried to reinstall by re-running Ubuntu under an elevated command prompt. I got 8007005. I seem to be stuck now. |
|
@benstaniford Can you please try this: #3020 (comment) |
|
@agowa338 Hmm, that doesn't seem to have worked. I didn't have Hyper-V enabled at all previously so I guess that's become a pre-req quite recently? However, enabling it, rebooting, and re-running the ubuntu18-4.exe process still shows an access denied HRESULT. Oddly I can simply run bash.exe from a standard command prompt to gain access to WSL but the console that comes with Ubuntu no longer works. Running wsl or wslbridge also no longer work and VS Code can no longer show the WSL terminal. I tried figuring out the cause of the access denied with procmon. This shows that when I run wsl as a normal user, an svchost gets an access denied on c:\Program Files\Ubuntu\rootfs. I've also just realized that running wsl as an administrator does work. I may have screwed this up when I was trying to recover from the initial Windows update issues when I deleted my WSL installation and tried to get it working again. Update: I was able to fix my issues by having my limited user take ownership of my C:\Program Files\Ubuntu folder. I guess my WSL rootfs shouldn't really be there, but I couldn't use the store to install Ubuntu because I have a corporate policy on my machine so it looks as though I've ended up screwing my permissions. |
This right here worked all miracles. THIS GOES TO ALL OF YOU WITH LATEST WINDOWS 10. |
|
Definitely not fixedin1809. |
|
:( this is back again after Windows Insider build 20231.re_prelease.201002-1444 Can't install Alpine Linux.: ~ $ alpine
Temporary directory: C:\Users\zenobius\AppData\Local\Temp\wsl_Alpine_setup
Downloading : http://dl-cdn.alpinelinux.org/alpine/v3.9/releases/x86_64/alpine-minirootfs-3.9.0-x86_64.tar.gz
To local file : install.tar.gz
The current working directory is: C:\Users\zenobius\AppData\Local\Temp\wsl_Alpine_setup
File successfully deleted
Mime type available
Begin download
Cache filename available
100% [====================]
End download
Downloaded OK
Hash of file install.tar.gz is: f82efed1a80c9af86c38bed10f3541c5588453b97684d767a5a3b0f3fa0e3f09
Verifying Hash: OK
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070005
WslRegisterDistribution failed
Error: 0x80070005 Access is denied.
Press any key to continue...Info~ $ wsl -l -v
NAME STATE VERSION
* docker-desktop-data Running 2
docker-desktop Running 2~ $ npx envinfo
npx: installed 1 in 1.852s
System:
OS: Windows 10 10.0.20231
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 20.79 GB / 31.86 GB
Binaries:
Node: 8.9.0 - C:\Program Files (x86)\Nodist\bin\node.EXE
Yarn: 1.3.2 - C:\Program Files (x86)\Nodist\bin\yarn.CMD
npm: 6.0.1 - C:\Program Files (x86)\Nodist\bin\npm.EXE
Managers:
pip2: 19.0.3 - C:\Python27\Scripts\pip2.EXE
pip3: 20.2 - C:\Python38\Scripts\pip3.EXE
Utilities:
Git: 2.27.0.
Virtualization:
Docker: 19.03.13 - C:\ProgramData\DockerDesktop\version-bin\docker.EXE
SDKs:
Windows SDK:
AllowDevelopmentWithoutDevLicense: Disabled
IDEs:
VSCode: 1.49.3 - C:\Program Files\Microsoft VS Code\bin\code.CMD
Languages:
Python: 3.8.1
Browsers:
Chrome: 86.0.4240.75
Edge: Spartan (44.20231.1000.0), Chromium (Login Succeeded), ChromiumDev (Login Succeeded)
Internet Explorer: 11.0.20231.1000submitted feedback, but the feedback app decided to not give me a link... T_T |
|
Windows Insider broke permisions and no have rollback. [ @InsiderSupport@microsoft.com] I_nstalling, this may take a few minutes... Press any key to continue..._ |
This solved my problem as well. Thanks a lot. |
This worked for me but make sure you copy it to a folder on the system drive per the following MS documentation. https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#installation-issues Regards, Paul |
|
People in here #6744 reported that this issue only exists with the store version and vanishes when WSL is installed without the Store and The windows store probably causes this permission issue. |
and others
Installed the new Kali build yesterday and received the following, on a Skip Ahead Insider build:
Installing, this may take a few minutes...
Installation Failed!
Error: 0x80070005
Press any key to continue...
Also bash from PowerShell throws teh same
The text was updated successfully, but these errors were encountered: