Hyper-V Integration Services Update Required

Fix Hyper-V Integration Services Update Notice in 2024

Server & Cloud Intermediate 👁 5 views 📅 Jun 15, 2026

You see this notice when your VM's integration services are outdated. Here's the exact fix that works on Server 2022 and Windows 11.

Quick Answer

Run the setup file from C:\Windows\System32\vmguest.iso inside the affected VM. Restart the VM. That's it 90% of the time.

Why This Happens

You're running a Hyper-V host (maybe Server 2022 or Windows 11 Pro) and a virtual machine — could be a legacy Windows Server 2012 R2 guest, a Linux VM, or even a Windows 11 guest. The host's integration services have been updated via Windows Update, but the guest's Hyper-V Integration Services (also called Linux Integration Services or LIS on Linux) are still the older version. Hyper-V detects the mismatch and pops the notice in both the VM connection window and the host's Hyper-V Manager. This happens most often after you install a Windows cumulative update on the host that includes a new integration services package, or after upgrading the host OS from Server 2019 to Server 2022. The guest doesn't auto-update because it's isolated by design. So you get the yellow banner: "Integration Services Update Required." It's not a critical error, but ignoring it means you miss out on performance improvements, bug fixes, and sometimes live migration compatibility.

Fix Steps

  1. Log into the guest VM — open a Remote Desktop session or use the VM connection window. It doesn't matter which.
  2. Mount the integration services ISO if it's not already attached. From the Hyper-V host, right-click the VM, go to Settings > DVD Drive > Insert Disk, and choose Integration Services Setup Disk. On Windows hosts, this file lives at C:\Windows\System32\vmguest.iso. Linux hosts? You'll need the matching Linux Integration Services ISO from the Microsoft download center.
  3. Inside the VM, open the DVD drive in File Explorer. Double-click setup.exe (or install.sh for Linux). On Windows, you'll see a wizard that says "Hyper-V Integration Services".
  4. Click Install in the wizard. It will update all services: data exchange, guest services, heartbeats, shutdown, time sync, VSS, and the Hyper-V callout driver. Expect a progress bar that takes 30 to 90 seconds.
  5. When the wizard finishes — it will say "You must restart your computer". Click Restart Now.
  6. After the VM comes back up, open the VM connection window again. The yellow banner should be gone. If it's still there, reboot the VM one more time. Sometimes the service doesn't register until the second restart.
  7. Double-check the version by running Get-VMIntegrationService -VMName "YourVM" from PowerShell on the host. Look for PrimaryStatusDescription — it should say "OK" for all services.

Alternative Fixes If the Main One Fails

If the setup fails, here's what to try:

  • Disable antivirus temporarily inside the guest. Some AV software (especially older McAfee or Symantec products) blocks the driver installation. Turn it off, run setup, then turn it back on.
  • Run the setup from an elevated command prompt. Open cmd as Administrator, then run D:\setup.exe (where D: is your DVD drive). This bypasses some UAC issues.
  • On Linux guests, use the command line. For RHEL/CentOS 7/8, run sudo ./install.sh from the mounted ISO. If you get a kernel mismatch, update the kernel first with yum update kernel and reboot before trying again.
  • Check the host's Hyper-V version. Run Get-WindowsEdition -Online on the host. If you're on an ancient build like Server 2016 RTM, the vmguest.iso might be too old for modern guests. Upgrade the host first.
  • Disable and re-enable integration services from the host. In Hyper-V Manager, right-click the VM, go to Settings > Management > Integration Services, uncheck everything, click OK, then go back in and re-check them. Then run the update steps again.

Prevention Tips

You can avoid this notice entirely by keeping your VM templates up to date. When you build a new VM, always install the latest integration services from the host's vmguest.iso before deploying it. For existing VMs, make it a habit to check for updates quarterly — right after Patch Tuesday. You don't need to hunt for notifications; just run Get-VMIntegrationService on each VM from the host. If any show "Update Required" or "Not Responding", you know it's time. And if you're managing a fleet of VMs, consider using PowerShell to automate the update: mount the ISO, copy the setup file, run it silently with setup.exe /quiet /norestart, then schedule a reboot during maintenance windows. That's the real pro move.

Was this solution helpful?

Hyper-V Integration Services update integration services outdated Hyper-V VM update notice fix integration services Windows Server 2022 integration services update Hyper-V guest VM integration services install Hyper-V components update integration services version mismatch Hyper-V host guest compatibility Windows 11 Hyper-V integration Server 2022 Hyper-V fix integration services manual install Hyper-V update steps integration services download