Fix Error 0x800f0906 When Enabling Hyper-V in Windows 10

Error 0x800f0906 appears when Windows 10 fails to download the required Hyper-V feature files from Windows Update, and the fix is to either point the installer to a local source or repair the Windows Update component. This error typically occurs during the “Enabling Hyper-V” step in the Windows Features dialog, and it stops the installation before any virtual machines can be created. Below are the exact steps to resolve it, followed by background on why it happens and how to avoid it in the future.

Why This Error Occurs

When you enable Hyper-V through the Windows Features control panel, Windows 10 needs to add several system components. Some of these components are already present in the local installation, but others are downloaded from Windows Update. Error 0x800f0906 is a DISM (Deployment Imaging Service and Management Tool) error that means “The source files could not be downloaded.” This can happen for several reasons:

Windows Update service is stopped or disabled.
Network connectivity is blocked (firewall, proxy, or VPN).
Windows Update cache is corrupted.
Your Windows 10 version is out of date and the required feature files are no longer available in the current update branch.
Third-party antivirus software is interfering with the download.

In many cases, the fix is to provide the source files locally instead of relying on Windows Update.

Prerequisites Before You Start

Before attempting any fix, make sure your system meets the basic requirements for Hyper-V:

Windows 10 Pro, Enterprise, or Education (Hyper-V is not available on Home edition).
A 64-bit processor with SLAT (Second Level Address Translation).
At least 4 GB of RAM (8 GB or more is recommended).
Virtualization enabled in BIOS/UEFI (Intel VT-x or AMD-V).

You can check if virtualization is enabled by opening Task Manager > Performance > CPU and looking for “Virtualization: Enabled” under the graph. If it says Disabled, you’ll need to enable it in your system firmware before proceeding.

Fix 1: Use DISM with a Local Source

This is the most reliable fix because it bypasses Windows Update entirely. You’ll need a Windows 10 installation ISO or a USB drive with the same version (build) as your system. Here’s how:

Mount the Windows 10 ISO by right-clicking it and selecting “Mount,” or insert the USB drive.
Note the drive letter of the mounted ISO (e.g., D:).
Open Command Prompt as Administrator (right-click Start > Windows PowerShell (Admin) or cmd).
Run the following command, replacing D: with your actual drive letter:

dism /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V /All /Source:D:\sources\install.wim /LimitAccess

If your ISO contains an install.esd file instead of install.wim, you’ll need to extract the WIM from the ESD first. A simpler alternative is to use the install.wim from the “sources” folder of a Windows 10 installation media created with the Media Creation Tool.

If you don’t have an ISO, you can download the official Windows 10 media creation tool from Microsoft and create one. The tool is free and works on any Windows 10 PC.

Fix 2: Repair Windows Update Components

If you prefer to keep using Windows Update (or don’t have an ISO), you can try to repair the update service. Run these commands in an elevated Command Prompt, one at a time:

Stop the Windows Update service: net stop wuauserv
Stop the Background Intelligent Transfer Service: net stop bits
Rename the SoftwareDistribution folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Rename the catroot2 folder: ren C:\Windows\System32\catroot2 catroot2.old
Restart both services: net start wuauserv and net start bits

After that, try enabling Hyper-V again from Windows Features. If it still fails, run the Windows Update troubleshooter from Settings > Update & Security > Troubleshoot.

Fix 3: Use the DISM RestoreHealth Command

Sometimes the system image itself is corrupted, which prevents the feature installation. Run these commands in an elevated Command Prompt:

dism /Online /Cleanup-Image /RestoreHealth – this repairs the system image.
sfc /scannow – this checks and repairs system files.

Wait for both to finish (this can take 15-30 minutes). Then restart your PC and try enabling Hyper-V again.

Common Mistakes to Avoid

Using a 32-bit Windows 10 – Hyper-V is only available on 64-bit.
Using a Home edition – you must have Pro or higher.
Not enabling virtualization in BIOS – even if the error is different, it will eventually cause problems.
Running the command without Administrator privileges – DISM will fail with a different error.
Using an ISO from a different Windows version (e.g., using a 1903 ISO on a 21H2 system) – always match the build.

Frequently Asked Questions

Can I enable Hyper-V on Windows 10 Home?

No, Hyper-V is not available on Windows 10 Home. You can either upgrade to Windows 10 Pro or use an alternative like VirtualBox or VMware Workstation Player (both free for personal use).

Will this error damage my system?

No, the error is just a failed installation attempt. Your system remains unchanged and stable. You can safely retry after applying the fixes above.

Do I need to download the exact same Windows 10 build ISO?

Ideally yes. Using a different build might cause a different error (0x800f0907 or 0x800f081f). The safest is to use the Media Creation Tool, which will download the latest build for your system.

What if I don’t have an ISO and can’t download one?

You can try the Windows Update repair steps (Fix 2) or use the DISM RestoreHealth command. If those fail, you may need to perform an in-place upgrade repair using the Media Creation Tool, which keeps your files and apps.

Is there a way to enable Hyper-V using PowerShell?

Yes, you can use Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All in an elevated PowerShell window. But this will likely produce the same error if the source files are missing.

After fixing the error, do I need to restart?

Yes, Windows will require a restart to complete the Hyper-V installation. You’ll see a prompt to restart immediately after the feature is enabled.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →