WSL: Error: 0x80070003
-
Your Windows build number: 10.0.17134.48
-
What you’re doing and what’s happening: executing
wsland receiving Error: 0x80070003 -
What’s wrong / what should be happening instead: Ubuntu should start up just like it did before the latest Windows update
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 26 (2 by maintainers)
Alright, not sure about Google, but this was the first result on Duck Duck Go, so I wanted to post my own solution I just found.
Alright, so I’m not sure what’s up, but on my fresh installation of redstone 4, I set my apps to install by default on a second drive. Usually for these distros, the windows store overrides that setting and tells you you can only install it on your C: drive (where your Windows is installed).
Well for some reason on Ubuntu and Ubuntu 16.04 (as far as I’ve tested) it’s not installing it on the C drive but instead just going ahead and installing it on your default set drive, thus leading to the error.
To fix this, go to Settings > Apps and find the distro, and move it to your C: drive.
Doing this instantly made them work. I don’t think this is related to OP’s issue, but I figured it’d be a good easy tutorial to put here for anyone who finds this on search engines… it’s good to have solutions for all the little quirks and edge cases that pop up.
Edit: also wanted to mention I found this out because strangely enough, Ubuntu 18.04 from the store prompts about the drive install location, and then upon install works entirely fine… but Ubuntu and Ubuntu 16.04 don’t for some reason.
Deleting C:\Users\username\.wslconfig worked for me
I got error 0x80070003 after manually deleting the Ubuntu folder and starting WSL.
I used that command to unregister.
wslconfig.exe /u UbuntuAfter that I was able to reinstall Ubuntu and start it without any problems.
(I downloaded Ubuntu manually from https://aka.ms/wsl-ubuntu-1604)
Yes,after set Settings > Apps and find the distro, and move it to your C: drive it works.
@UberActivist Your solution rocks!!!
Marking as duplicate of #2576.
Worked for me because it seemed to have added a test kernel line which I know specifically I never did, I removed only that line which had a reference to c:// and left my ram limit in place.
Deleted C:\Users\username\.wslconfig and now everything works as it used to. I had also created the .wslconfig file to allocate CPUs/RAM:
Is using .wslconfig no longer supported or is there a problem with its contents??
@UberActivist Pure awesome! If only they could fix that.