-
Notifications
You must be signed in to change notification settings - Fork 850
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
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/ERROR_PATH_NOT_FOUND & WslRegisterDistribution failed with error: 0x80070003 #12535
Comments
View similar issuesPlease 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! Open similar issues:
Closed similar issues:
Diagnostic information
|
Another thing to note is the "DXCore version: 10.0.26100.1-240331-1435.ge-release" - where I'm seeing most people are using a DXCore tag with 'onecore' somewhere in the middle. Maybe it's related? Scouring online doesn't yield a lot of documentation, but the most common DXCore version I've seen is something along the lines of this: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp |
Thank you for reporting this @structuredstanza. Does the |
Yes, it exists with the following content: I've also noticed something else troubleshooting - the HyperV Virtual Machine Bus Provider & HyperV Virtual Disk Server both have issues with init: Device ROOT\storvsp\0000 had a problem starting.
Device ROOT\VMBus\0000 had a problem starting.
|
Windows Version
Microsoft Windows [Version 10.0.19045.5371]
WSL Version
WSL version: 2.4.8.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
Other software that may be impacting the installation includes only Docker Desktop
Repro Steps
Installing any distro, through either .wsl files or through --install -d lead to the following errors:
Looking through the logs, I'm noticing that OneCore is failing to init or even call VM functions:
[Virtual machine 3C72BF82-0280-495A-A41F-0E6A239AF878] onecore\vm\worker\vmb\virtualmotherboard.cpp(7511)\vmwp.exe!00007FF6D0FF4A1C: (caller: 00007FF6D0FF2D4A) LogHr(1) tid(2c34) 80070003 The system cannot find the path specified. CallContext:[\VmInitialize\VmbInitialize\VdevOperation]
[Virtual machine 3C72BF82-0280-495A-A41F-0E6A239AF878] onecore\vm\worker\vmb\virtualmotherboard.cpp(646)\vmwp.exe!00007FF6D0FF4820: (caller: 00007FF6D0FF49F7) ReturnHr(1) tid(2c34) 80070003 The system cannot find the path specified. Msg:[onecore\vm\worker\vmb\virtualmotherboard.cpp(581)\vmwp.exe!00007FF6D0FF44E7: (caller: 00007FF6D0FF49F7) Exception(1) tid(2c34) 80070003 The system cannot find the path specified. Msg:[VDEV Microsoft VmBus ID D41A1872-3740-41CE-A1EE-4522AB82F991] CallContext:[\VmInitialize\VmbInitialize\VdevOperation] ] CallContext:[\VmInitialize\VmbInitialize\VdevOperation]
I've tried forcibly reinstalling the OneCore Windows capability, DISM re-installing WSL & Virtual Machine Platform. Seems like a disconnect between OneCore & WSL?
WSL version: 2.4.8.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.5371
Expected Behavior
Full installation of desired distro
Actual Behavior
EVENTS:
[Virtual machine 3C72BF82-0280-495A-A41F-0E6A239AF878] onecore\vm\worker\vmb\virtualmotherboard.cpp(7511)\vmwp.exe!00007FF6D0FF4A1C: (caller: 00007FF6D0FF2D4A) LogHr(1) tid(2c34) 80070003 The system cannot find the path specified. CallContext:[\VmInitialize\VmbInitialize\VdevOperation]
[Virtual machine 3C72BF82-0280-495A-A41F-0E6A239AF878] onecore\vm\worker\vmb\virtualmotherboard.cpp(646)\vmwp.exe!00007FF6D0FF4820: (caller: 00007FF6D0FF49F7) ReturnHr(1) tid(2c34) 80070003 The system cannot find the path specified. Msg:[onecore\vm\worker\vmb\virtualmotherboard.cpp(581)\vmwp.exe!00007FF6D0FF44E7: (caller: 00007FF6D0FF49F7) Exception(1) tid(2c34) 80070003 The system cannot find the path specified. Msg:[VDEV Microsoft VmBus ID D41A1872-3740-41CE-A1EE-4522AB82F991] CallContext:[\VmInitialize\VmbInitialize\VdevOperation] ] CallContext:[\VmInitialize\VmbInitialize\VdevOperation]
Diagnostic Logs
WslLogs-2025-01-31_15-50-35.zip
The text was updated successfully, but these errors were encountered: