Hyper-V Integration Services Won't Install or Update

Quick answer

Run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow in the guest VM, reboot, then retry the Integration Services setup from Hyper-V Manager.

Context — why this happens

Hyper-V Integration Services gives you the good stuff: mouse pointer integration, time sync, backup support, and proper shutdown from the host. When it fails to install or update, the error code is usually 0x800f0986, which translates to “servicing stack is messed up”. I've seen this on Windows Server 2016, 2019, and 2022 VMs that were cloned from a base image or had their Windows Updates interrupted mid-way. The servicing stack is the low-level component that handles Windows Update and driver installation. If it's corrupted, Integration Services can’t register its drivers and services.

Here's the specific scenario: you're in Hyper-V Manager, you click “Insert Integration Services Setup Disk”, the guest installs the ISO, then after a few seconds you get a rollback with no explanation. Event Viewer shows 0x800f0986. The fix is not to reinstall the VM — it's to fix the servicing stack first.

Fix steps

1. Open an elevated command prompt in the guest VM. Right-click Start, select Command Prompt (Admin) or PowerShell (Admin).
2. Run DISM to repair the servicing stack. Type:

   DISM /Online /Cleanup-Image /RestoreHealth

   This will scan the component store and replace any corrupted files. It might take 15–30 minutes. Don't cancel it mid-way.
3. After DISM completes, run SFC. Type:

   sfc /scannow

   This fixes OS file corruption that DISM might have missed. Takes about 10 minutes.
4. Reboot the VM. You need a clean state before Integration Services can install.
5. Reinstall Integration Services. In Hyper-V Manager, select the VM, go to Action > Insert Integration Services Setup Disk. In the guest, open File Explorer, go to the virtual DVD drive (usually D:), right-click setup.exe, and select Run as administrator. Follow the prompts.
6. After install finishes, reboot again. The VM will load with the new drivers and services.

Alternative fixes

If the main fix didn't work, here are other things to try:

• Check the guest OS version. Integration Services for Windows Server 2022 won't work on Windows Server 2012 R2. Make sure you're using the correct version of Hyper-V host. If you're running Hyper-V on Windows 10/11, the ISOs are tied to the host build. You can download the latest Integration Services ISO from Microsoft separately for older hosts.
• Manually extract the ISO and run the service installer. Sometimes setup.exe fails silently. Mount the ISO, browse to D:\Support\x64\ (or x86 for 32-bit guests), right-click vmguest.iso, and run setup.exe from there. Yes, it's an ISO inside an ISO — Microsoft's idea.
• Turn off automatic VM updates temporarily. If you have Windows Update running in the background, it can block the installation. Go to Settings > Updates & Security > Pause updates for 7 days. Then try the Integration Services install again.
• Check the guest's disk space. Integration Services needs about 500MB free on the system drive. Low space causes silent failures.

Prevention tip

The root cause — servicing stack corruption — usually comes from using sysprepped images from unreliable sources, or from restoring a VM from a backup that had partial Windows updates. To avoid this, always build your base VMs with a clean Windows installation, apply all updates before cloning, and never delete the SoftwareDistribution folder manually. Let Windows Update handle it. If you clone, run DISM /Online /Cleanup-Image /CheckHealth before locking the image. This catches corruption early and saves you an hour of troubleshooting later.