Forum Discussion
[Windows Server 2025 Host] KB5062553 (and June’s) Breaks GPU-P to Windows 11 VM
I'm running Windows Server 2025 as my Hyper-V host, with RTX A4500 20GB, and using GPU Partitioning (GPU-P) to assign GPU resources to a Windows 11 24H2 VM. Everything worked flawlessly before the last two cumulative updates - June’s and now July’s KB5062553. After either update, all the old issues come back:
- VM freezes at boot or right after login
- Remote Desktop disconnects or becomes unresponsive
- Assigning a GPU partition to the VM triggers hangs and instability
- Rolling back the update restores stability, but Windows keeps trying to push these updates, have to manually hide it. After that VM working great.
It’s not just the July update - June’s cumulative update caused the same problems. I know Microsoft claims to have fixed some GPU/VM bugs, but for me (and apparently others), the issues persist when running GPU-P from a Server 2025 host to a Windows 11 guest.
- Anyone else running into this with Server 2025 Hyper-V and GPU-P to Windows 11 VMs after recent updates?
- Any way to reliably block these updates or workaround for GPU-P?
- Has Microsoft acknowledged this for Server 2025 hosts, or are we just waiting for a real fix?
For now, I’m snapshotting before every update and rolling back as needed, but this obviously isn’t sustainable.
Would love to hear if anyone else is fighting this battle - or has found a way to keep GPU-P working from Server 2025 to Windows 11 after the June/July updates!
If this is in the wrong section, mods please move this. Thanks.
7 Replies
This has been fixed by disabling the Hyper-V Video adapter and installing the Virtual display driver by MikeTheTech.
This ended up working.
However, what i did at first is try to connect it straight from the Windows Server Hyper-V management. Spoiler: DON'T do that.
Instead open up another remote session and connect straight to the VM, this works.... For now.
Thank you! 3 months of troubleshooting ended here.
Here's an off-roading solution: replace dxgkrnl.sys with an earlier version. The problematic version is 10.0.26100.4652. I started a new VM and updated it to 2025-03 and I copied dxgkrnl.sys (v. 10.0.26100.3912) to a VM that was not working and it booted without issue. See below for the now working vm with 2025-07 installed. Since this problem is related to dxgkrnl, it will probably be up to GPU manufacturers to update drivers. This solution is likely very unstable. The preferred approach would be to update a VM to 2025-04 and disable updates until Microsoft or Nvidia fix the problem.
This actually destroyed my VM, it cannot boot anymore.
Yes, GPU-P for Nvidia GPU on Hyper-V Windows 11 guest has been broken since the June update. This is independent of host OS and no known workaround available at this time.
Yes, GPU-P with Nvidia GPU on Windows 11 guest is broken since the June update. The issue is not specific to the host machine OS - seen this on Windows server hosts as well as Windows 11 hosts. Currently there's no known way to workaround this issue, you'd either revert these cumulative updates or disable GPU-P through Remove-VMGpuPartitionAdapter.
Unfortunately Microsoft cannot manage their own updates and has been creating all kinds of mess.
Yeah, tried with 2025-10 cumulative update, no fix.
Tried with 25H2, no fix :(
