microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
16.93k stars 799 forks source link

WSL: A virtual disk support provider for the specified file was not found. #8551

Open r2sakib opened 2 years ago

r2sakib commented 2 years ago

System info:

WSL version: 0.60.0.0 WSLg version: 1.0.34 Kernel version: 5.10.102.1 Windows version: 10.0.22621.1

Logs

WslLogs-2022-06-30_21-55-31.zip

benhillis commented 2 years ago

/logs

ghost commented 2 years ago

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

r2sakib commented 2 years ago

Logs added. @benhillis

xcskilab commented 1 year ago

I'm seeing the same issue.

Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0xc03a0014 Error: 0xc03a0014 A virtual disk support provider for the specified file was not found.

gsharratt commented 1 year ago

I have the identical problem with Windows 11. When invoking Ubunto from the Microsoft Store:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xc03a0014
Error: 0xc03a0014 A virtual disk support provider for the specified file was not found.
gsharratt commented 1 year ago

My problem just magically went away without my doing anything. A few System Devices (Hyper-V and something else) installed themselves, and my Ubuntu now works.

Gnani-Codes commented 1 year ago

Even i am getting the same error when launching Ubuntu and Docker from my Windows 11, I have tried multiple methods from online but nothing worked out. I have attached my log files below...

WslLogs-2023-05-11_12-11-53.zip

earlbellinger commented 1 year ago

I am also having this problem. It only just started after (more or less) working for a while.

Doc94 commented 1 year ago

same issue here i try disable and enable again all but nothing the error still show.

karimMogh commented 1 year ago

same issue, I tried everything.

karimMogh commented 1 year ago

I found a way to replicate the same issue, maybe this will help if finding the fix. I'm installing WSL2 on around 20 machines, When installing WSL for the first time by executing the WSL --update command, the CMD request an admin access after donning 90% of installation, at this point if I cancel and redo again the whole process, this issue will happen and I will not be able to install WSL 2 on this machine anymore, for the other machines I ensured to run the cmd as admin and to provide an admin user and pass when prompting me and everything has worked fine for me.

JOY commented 8 months ago

Same issue happened suddenly today.

DAFRAYAL commented 8 months ago

I get this error after updating some device drivers on machine. Either it is ACPI computer to DMA or anything else even though Virtual Drive Enumerator is enabled. I get it just to mount VHD. It could be ImDisk software device driver being enabled and so on, see if you can use different command or software that device drivers may be overlapping each other to mount the VHD as for VHD mounting

neokofg commented 4 months ago

https://github.com/microsoft/WSL/issues/10555#issuecomment-1937980344

biosaio commented 4 months ago

#10555 (comment)

I also have the issue. Tried this and many other solutions found on the internet. I even formatted my PC, but nothing works. logs: WslLogs-2024-03-05_17-59-45.zip

JOY commented 4 months ago

#10555 (comment)

I also have the issue. Tried this and many other solutions found on the internet. I even formatted my PC, but nothing works. logs: WslLogs-2024-03-05_17-59-45.zip

Hi. Just to update that my issue was caused by the mainboard issue. I replace the mainboard from the seller and it is back to work.

biosaio commented 4 months ago

Solved as well! I uninstalled the last windows update and everything went back to normal