Hyper-V Integration Services Won't Install or Update

When This Error Shows Up

You're running a Windows Server 2019 or Windows 10 VM on Hyper-V host (Windows Server 2016 or 2019). You go to the VM, click Action > Insert Integration Services Setup Disk. Installation starts but stops with error 0x800f080C. No other details. The VM might have pending updates from Windows Update.

What's Actually Happening

The Integration Services update needs a specific OS update to run. The error 0x800f080C means Windows can't find a required component—usually a servicing stack update or a .NET framework patch. Microsoft doesn't make this clear. You're stuck because the VM's OS is too old for the Integration Services version on your host.

The Fix: Step by Step

Step 1: Check the VM's OS version

1. Inside the VM, open Command Prompt as Administrator.
2. Run:

   winver

3. Write down the version number (like 1809 or 20H2).

Step 2: Check the Hyper-V host version

1. On the host machine, open PowerShell as Administrator.
2. Run:

   Get-WindowsEdition -Online

3. Look for the edition string. If it says Server 2019, your Integration Services ISO is from that build.

Step 3: Update the VM's OS first

1. In the VM, go to Settings > Update & Security.
2. Click Check for updates. Install all pending updates. This includes servicing stack updates. Reboot if needed.
3. Repeat until no more updates are found.

Step 4: Reboot the VM

1. Shut down the VM completely:

   shutdown /s /t 0

2. Wait 30 seconds. Start it back up.

Step 5: Install Integration Services again

1. In Hyper-V Manager, select the VM.
2. Click Action > Insert Integration Services Setup Disk.
3. Inside the VM, open File Explorer, go to the DVD drive.
4. Run setup.exe as Administrator.
5. Follow the wizard. It should complete now.

What to Check If It Still Fails

If the error comes back, here's what to try:

• Manually install the servicing stack update. Go to Microsoft Update Catalog and search for the latest Servicing Stack Update for your VM's version. Download and install it. Then retry step 5.
• Use powershell to check for blocked updates. In the VM, run:

  DISM /Online /Get-CurrentState

  Look for any components showing as pending or corrupt. If you see corruption, run:

  DISM /Online /Cleanup-Image /RestoreHealth

  Then try again.
• Check the host's Integration Services ISO. On the host, go to C:\Windows\System32\vmguest.iso. That's the file Hyper-V uses. If it's corrupted (rare, but happens after a host update), you may need to reinstall the Hyper-V role on the host.

I've seen this error three times in the last year. Every time, it was the VM needing updates first. Skip the fancy fixes—just get the VM fully patched.