Hyper-V VM Integration Services Won't Update: 3 Fixes

What's actually happening here

When you see error 0x800f0950 while trying to update Integration Services in a Hyper-V VM, it's not a random glitch. The error means Windows couldn't find or apply a needed component package. Usually, the VM's Windows Update component is broken, or the host's Hyper-V tools don't match the VM's OS build. I've seen this most often on Windows Server 2019 VMs running on a Windows 11 host — the host has newer Integration Services packages than the old VM can handle.

Fix 1: 30 seconds — Restart the Integration Services service inside the VM

This fixes a common stale state where the service goes zombie.

1. Inside your VM, open PowerShell as admin.
2. Run Restart-Service -Name vmicguestinterface
3. Then try the update again from Hyper-V Manager.

If that works, you're done. If not, the service is fine — the problem is elsewhere.

Fix 2: 5 minutes — Run DISM and SFC to repair the component store

The error 0x800f0950 is often a corrupted component store. DISM can fix that.

1. In the VM, open PowerShell as admin.
2. Run DISM /Online /Cleanup-Image /RestoreHealth
3. Let it finish — takes 2-5 minutes.
4. Then run sfc /scannow
5. Restart the VM.
6. Retry the Integration Services update from Hyper-V Manager.

This fixes 80% of cases. The reason step 3 works: DISM replaces corrupted system files by pulling fresh copies from Windows Update or the local source.

Fix 3: 15+ minutes — Reinstall Hyper-V Integration Services from the host using an ISO

If DISM didn't work, the VM's component store is too broken to self-heal. You need to push the files from the host directly.

1. On the Hyper-V host, create an ISO of the Integration Services package:

# Find the path to vmguest.iso
Get-ChildItem -Path "$env:SystemRoot\System32\vmguest.iso"

# Mount it
Mount-DiskImage -ImagePath "$env:SystemRoot\System32\vmguest.iso"

2. Note the drive letter, e.g., D:.
3. Inside the VM, browse to D:\ and run setup.exe as admin.
4. Follow the wizard — it reinstalls Integration Services cleanly.
5. Reboot the VM.

If that still fails, check the VM's configuration version. Run this on the host:

Get-VM -Name "YourVMName" | Select-Object Version

Version 9.0 is for Server 2012 R2, 10.0 for 2016, 11.0 for 2019/2022. If your VM is too old (like version 8.0 from Server 2012), the host's Integration Services package won't be compatible. You'd need to upgrade the VM configuration version first — but that's a bigger project.

When to just give up and use the host's Insert Integration Services Setup Disk option

If the ISO method also fails, close Hyper-V Manager. Open it again, right-click the VM, select Insert Integration Services Setup Disk. This mounts the correct ISO for that VM's generation. Then inside the VM, run F:\setup.exe (replace F: with whatever drive it mounted). This bypasses any version mismatch because the host picks the right files for the VM's OS.

One last sanity check

Make sure your VM's time and date are correct. If they're off by more than a few minutes, Windows Update and DISM will reject certificates and fail. I spent an hour on this once before noticing the VM thought it was 2023.