Repository navigation
[BUG] - WSL fails to launch with ERROR_PATH_NOT_FOUND #1615
Description
Before continuing...
- I agree to follow Atlas' Code of Conduct
- I have searched our issue tracker to verify that the issue hasn't been reported already
- I have searched the Atlas documentation beforehand for a solution
- I am on the latest version of Atlas, and didn't do an unsupported upgrade
Description
wsl --install Ubuntu
Downloading: Ubuntu
Installing: Ubuntu
The system cannot find the path specified.
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/ERROR_PATH_NOT_FOUND
I get this no matter what, I've checked
BIOS virtualization settings
uninstall/reinstall WSL from microsoft store
uninstall/reinstall from powershell
uninstall/reinstall Hyper-V and all other virtualization-related optional windows components
Atlas Toolbox Troubleshooting / Repair Windows Components
wsl.exe --update
Docker doesn't work either, similar error message.
out of ideas...
Steps to reproduce
go to powershell
run 'wsl --install Ubuntu' (for instance)
Expected behavior
WSL should install and launch Ubuntu distro
Actual behavior
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/ERROR_PATH_NOT_FOUND
Atlas Version
Atlas v0.5.0 for Windows 10 22H2
Desktop information
AMD Ryzen AI+ 395
Asus Rog Flow Z13
Additional content
No response
Activity
stariluz commentedon Apr 2, 2026
@coreym I had just the same problem. It seems resolved after installing the latest release of WSL.
After that, running
wsl --install Ubuntuworked without problems and after restarting my computer docker stopped asking to update wsl.MaxFrei91 commentedon Apr 3, 2026
Sadly, doesn't works for me. -_-
coreym commentedon Apr 3, 2026
ah that's unfortunate, I ended up reinstalling windows, testing WSL, then running the latest AtlasOS playbook. Can't remember which options I selected, but it's working... maybe when I setup WSL before running the playbook it installed some components that can't be installed after running the playbook?
Stensel8 commentedon Apr 27, 2026
This is becase Atlas messes up your Virtualization Based Security and Core Isolation when you select some of the "mitigations". WSL2 relies on these.
Did you disable VBS or any other modern virtualization related options? Since they tend to break features like Docker and WSL2.
Stensel8 commentedon May 19, 2026
Related to: #1647
But since that suggestion is not implemented, this can not be solved automatically and needs to be solved manually by enabling Virtualization Based Security (VBS).
Note that this is something completely different than VBScript, which is a deprecated predecessor of Powershell.
MaxFrei91 commentedon May 26, 2026
Emm... As everyone here I catch this problem, but I forgot how I solved it. I think llm suggests to install ubuntu manually trough downloading reps from official site and through some commands. I did that with deepseek or qwen on win with deleted store, so that was painful, but was possible.
Everything was working before on same system, and was suddenly, after couple of month, without changes in vbs or virtualizations , stops, and I was - wah? I ended up that they temporary messed something like path links, but if it's still the problem - I don't know what it is. :) Yeah, was fixed with manual download of ubuntu rep and installing it.
Stensel8 commentedon May 26, 2026
Weird. I dunno what is happening on your side without seeing logs/errors or enabled features and regkeys.
Probably has to do with: #1647
Vasault commentedon Jul 7, 2026
having the same issue and tried every solution described here in the section, and still getting that error after running wsl --install Ubuntu
Stensel8 commentedon Jul 8, 2026
What hardware are you using?
What Windows version?
And do you have all security and virtualization settings enabled?