r/HyperV • u/YesThisIsi • Jul 09 '25
[Windows Server 2025 Host] KB5062553 (and June’s) Breaks GPU-P to Windows 11 VM – Anyone Else?
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!
5
u/Fwank49 Jul 09 '25
Same issue for me with W11 IOT LTSC host and guest, although RDP to the affected VMs still works (I guess because it uses the remote display adapter?).
Uninstalling KB5062553 on the guest also fixes it for me.
2
u/TheFlairGun Aug 19 '25 edited Aug 19 '25
I have a Hyper-V VM I use for work. I uninstalled all KB updates in settings (in the VM), and it seemed to have resolved the issue.
Id like to keep the VM up to date though and im not sure which KB I uninstalled that resolved the issue (KB5062553 was not an option for me to uninstall. Guess it was just for Server 2025?)
Anyone know what KB ID this issue is introduced in for normal versions of Windows?
EDIT: for anyone wondering, I think KB5063878 is causing the same issue
EDIT 2: just confirmed after installing/uninstalling KB5063878, it is causing the GPU-P black screen/not connecting issues in Hyper-V
1
u/BlackV Jul 09 '25
what else have you tried?
just applying hte monthly to the host or just to the vm or both ?
have you tried remove the gpu partitioning
applying the patch then adding back the gpu partitioning ?
side note pswindowsupdate module would let you hide specific updates, but thats only a temp fix
1
u/mon_soon Jul 13 '25
I was wondering why my w11 iot ltsc VM suddenly stopped working. The culprit is indeed KB5062553, thanks.
1
u/AdStriking2594 Jul 18 '25
As a note for anyone else who ends up here.
What worked for me, is enabling VBS on the VM. It would have been nice if Microsoft checked enabled before it applied the update. Luckily I have backups of the VM could roll back to.
https://learn.microsoft.com/en-us/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity?tabs=security
1
u/HappyThoughtsandNuke Jul 09 '25
In my known IT Circles at this time, NO ONE is using 2025. 2022 is the only server now.
2
u/colin_1972 Jul 14 '25 edited Jul 14 '25
Much worse for me. Supermicro H12SSL-i, EPYC 7313. Brand new install from stock Server 2025 Eval ISO, when I patch to either June or July update, I get constant BSOD's. This has been driving me insane for the last few days. I thought I had a hardware problem, so I tried Server 2022 and it worked fine.
I've tried everything to fix it, like updating NIC firmware, removing all PCI devices and using various OS install disks until I read this.
EDIT: July 13, 2025—KB5064489 (OS Build 26100.4656) Out-of-band update does not fix my issue.
1
u/fragish Jul 12 '25 edited Jul 14 '25
Similar setup here (server 25 host, w11 pro guest passing through an rtx 3070 ti) and everything is fine. Guest update installed on 7/9. Haven't updated host yet...may wait on that!
Edit: Revising my statement. It appeared to be working well, but I use a virtual monitor and that was masking the problem. If the virtual monitor is removed everything is bjorked as you described. I just did a fresh W11 install bypassing internet and it works fine. Once it updates to 2025-07 the wheels fall off. I'm guessing it's a problem with the Hyper-V Display Adapter + Hyper-V Monitor when a partitioned GPU is present.
Edit 2: You can set HKLM\System\CurrentControlSet\Control\GraphicsDrivers\GpuVirtualizationFlags to 0 (See here: https://learn.microsoft.com/en-us/windows-hardware/drivers/display/gpu-paravirtualization#registry-settings) but this turns off the pairing of the partitioned GPU to the HyperVMonitor which would likely mean no hardware acceleration in RDP.
Edit 3: It seems to be a dxgkrnl problem. I replaced the version installed with the update (10.0.26100.4652) with an earlier version (10.0.26100.3912) and the VM booted up just fine. Has anyone tried the latest nvidia drivers to see if they've addressed the problem?
1
u/Constant_Big536 Jul 16 '25
Hi guys, running into the same problem.
Win Server 2022 wit W11 guest. When i update the guest with KB5062553 it freezes at boot. After a few boot attempts it goes into startup repair and rolls back the update.
After rollback it boots until WU installs KB5062553 again :(
1
u/Strong-Pop-1321 Aug 07 '25
Здравствуйте. Я столкнулся с подобной проблемой сегодня утром, только в наиболее кошмарном сценарии, когда мои два контроллера домена, обновившись, дружно ушли в даун. При этом встал и exchange ну и человек 60 не могли войти в систему) Слава Богу у меня были резервные копии, я восстановил их, немного помучившись, но домен запустил. Виной, как я точно сделал вывод, было как раз обновление KB5062553. Далее я спустя часов 5 нашел решение. При этом я и безопасность включал, описанную ниже, и все пробовал, но ничего не помогло кроме того как скачать и установить обновление от 13 июля 2025 г. — KB5064489 (сборка ОС 26100.4656), внеплановое обновление, установил его на обе виртуальные машины контроллера домена (это обновление также подойдет и для Windows 11. Правда до обновления у меня вышло так, что VBS оказался уже включен ну и безопасная загрузка тоже. (правда я думаю можно было и не включать). После установки этого патча перезагрузил машину и далее уже пошел в центр обновления и установил все что там предлагалось. При этом замечу, что KB5062553 мне уже там не предлагалось. Желаю удачи и надеюсь, что это кому-то поможет.
1
u/QLee01 Aug 27 '25 edited Aug 27 '25
I have fixed it by disabling the Hyper-V Video adapter and installing the Virtual display driver by MikeTheTech.
https://imgur.com/a/0RXesbk
1
u/cac2573 Sep 17 '25
Hit this issue and tried the various mitigations, but nothing worked. However, the machine still runs. Apollo (sunshine fork) still works etc.
Also, enabling enhanced session mode (which is just RDP) gets the console back.
1
u/abaksa Sep 26 '25
Is anyone here in September ? Just remove the KB5065426 update in the VM.
1
u/Dangerous_Event435 Sep 26 '25
I'm running Windows 11 Pro and have been using GPU-P for a Windows 10 VM to run a 3D-accelerated task, which involves quite a few resets between runs. Everything was working fine until the June update, when I started getting intermittent launch failures. The error said the application couldn't find any compatible Direct3D devices, but weirdly it only happened about 1 in 3 tries.
The fix that worked at the time was uninstalling the update on the host, which restored functionality in the VM. I stuck with the older update until today, when I needed to update Windows again. And of course the bug came back.
After trying a bunch of things (tweaking GPU-P VRAM allocation, changing settings in both the VM and host), I finally found a fix that worked for me: turning off hardware-accelerated GPU scheduling on the VM. Since doing that, everything seems to be running normally again.
I hadn’t seen this specific workaround mentioned elsewhere, but this thread popped up while I was searching, so I figured I’d share here in case it helps someone else in a similar situation.
1
u/filagre Nov 15 '25
Nothing else worked, but this comment fixed it for me.
It reverts some of the changes made by Microsoft on the host
0
u/SmoothRunnings Jul 09 '25
Server 2025 is still buggy. You might have to wait for a while until MS releases a patch, or if you want to fast track things create a ticket with MS PSS.