Share via

WSL error 0xc03a0014 – Virtual disk support provider not found on Windows 11

Anonymous
2025-05-29T17:23:26+00:00

Hi everyone, I'm trying to install Ubuntu on Windows 11 using WSL, but I constantly get this error:

Installing, this may take a few minutes...

WslRegisterDistribution failed with error: 0xc03a0014

Error: 0xc03a0014 Cannot find a virtual disk support provider for the specified file.

BlueStacks and VirtualBox fail as well, which makes me think this is a system-level problem with virtual disk (VHD/VHDX) handling.

What I’ve already tried:

  • Virtualization is enabled in BIOS and Task Manager
  • Enabled “Windows Subsystem for Linux” and “Virtual Machine Platform” features
  • Disabled Memory Integrity and Controlled Folder Access in Windows Defender
  • Ran sfc /scannow and DISM → no integrity issues
  • Tried uninstalling and reinstalling WSL and Ubuntu
  • Mounting a VHDX manually → fails
  • systeminfo shows: "A hypervisor has been detected"

Is there any known fix for this error? Can I restore virtual disk support without reinstalling Windows?

Thanks in advance 🙏

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2025-05-30T13:30:58+00:00

    Hi Laura Frasarin,

    Thank you for posting here in Community.

    That error is definitely frustrating, and I can see you've already done a thorough job troubleshooting. The fact that both BlueStacks and VirtualBox are failing suggests a deeper issue with virtual disk handling on your system.

    Here are some additional steps you can try to restore virtual disk support without reinstalling Windows:

    1. Restart the Virtual Disk Service

    • Open Services (Win + R, type services.msc, and press Enter).
    • Locate Virtual Disk in the list.
    • Right-click and select Restart.
    • Try running WSL again.

    2. Check Hyper-V and Virtualization Features

    Since systeminfo detects a hypervisor, ensure Hyper-V is properly configured:

    • Open PowerShell as Administrator and run:

    powershellGet-WindowsOptionalFeature -Online | Where-Object { $_.FeatureName -match "hyper" -or $_.FeatureName -match "linux"}

    • If Hyper-V or WSL features are disabled, enable them using:

    powershellEnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -NoRestart Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart

    • Restart your PC and try again.

    3. Reinstall the Virtual Disk Driver

    • Open Device Manager (Win + X, then select Device Manager).
    • Expand Storage controllers.
    • Locate Microsoft Virtual Disk Provider (or similar).
    • Right-click and select Uninstall device.
    • Restart your PC—Windows should automatically reinstall the driver.

    4. Manually Repair the Virtual Disk System

    • Open Command Prompt as Administrator and run:

    cmdchkdsk /f /r

    • Then, reset the virtual disk system with:

    powershelldism /online /cleanup-image /restorehealth

    5. Check Event Viewer for Errors

    • Open Event Viewer (Win + R, type eventvwr, and press Enter).
    • Navigate to Windows Logs > Application.
    • Look for errors related to Virtual Disk Service or Hyper-V.

    6. Consider Creating a New Virtual Disk

    If your system is failing to mount VHDX files, you might need to create a new virtual disk:

    • Open Disk Management (Win + X, then select Disk Management).
    • Click Action > Create VHD.
    • Select a location and size, then initialize the disk.

    If none of these steps resolve the issue, you may need to check for Windows updates or consider a repair installation. Let me know how it goes!

    Best regards,

    Bo | Microsoft Community

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-06-03T17:27:00+00:00

    Hi Laura Frasarin,

    This my 2nd follow-up regarding your issue on this post. We would like to know if the issue you have raised to us is still on-going. If yes, please reply to the thread so we can continue troubleshooting your concern.

    Thank you.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-06-02T22:16:48+00:00

    Hi Laura Frasarin,

    We have noticed that you have not replied to our last response. We would like to know if the issue you have raised to us is still on-going. If yes, please reply to the thread so we can continue troubleshooting your concern. 

    Thank you.

    Was this answer helpful?

    0 comments No comments