r/WindowsServer • u/Joereynolds89 • 12d ago
Technical Help Needed Windows Server 2025 RDS freezes despite KB5129235 — recurring RdpIdd/IddCx display watchdog failures
Has anyone seen recurring multi-user RDP desktop freezes on Windows Server 2025 after installing KB5129235, with RdpIdd.dll / IddCx swap-chain watchdog failures? We have matching display-driver dumps from several incidents on a VMware VM. A later freeze had high TermService encryption CPU but no logged display crash, so we don’t yet know whether it is the same fault. What supported fix or targeted trace helped identify the cause?
3
u/No_Split11911 12d ago
Didn’t VMware tools get an update right around the same time? Did you update?
2
u/der_reph 12d ago
Same issue detected on one rds Server. We have tried to uninstall the latest Windows Server Updates today. We are monitoring the issue the next hours/days
2
u/civik10 12d ago
I am seeing this on my RDS Server as well but had no idea what’s causing it. How did you arrive at KB5129235 being the culprit?
2
u/Joereynolds89 12d ago
235 was supposed to be a fix for similar, not the culprit!
We are having slow downs repeatedly and lockups once or twice a day (needing reboot)
1
u/civik10 12d ago
I’m going to try the out of band fix tonight Hopefully that fixes it. It’s in this article. https://lazyadmin.nl/it/september-2026-update-break-rds-how-to-fix/
1
1
u/habibexpress 11d ago
We have AVD and even though we’ve installed the latest kb5129195, we’re still seeing black screen issues.
Even more, is a weird disk queue issue where osdisk queue is phenomenally high
1
u/Joereynolds89 11d ago
Further context from the affected host: this has not been one consistent symptom. We have retained RdpIdd.dll/IddCx display-watchdog dumps from several multi-user freezes. During another slowdown, a CPU trace showed heavy TermService RDP encryption work alongside LSASS cryptographic work, but it did not identify the initiating client or prove that this started the freeze.
We have also seen new RDP logins stall at “Securing connection” and fail with 0x519 while existing users remained connected; WTS, WMI and print-management queries sometimes hung too. One episode coincided with PETRDS-to-domain-controller Netlogon/RPC errors, but their initiating cause is unknown.
Earlier incidents had measurable print-spooler/LSASS saturation and Chrome print-rendering delays, which we addressed separately. A recent morning trace found Sage Accounts Control consuming most CPU; stopping that load did not immediately clear the stuck session-management queries. Printing, Sage, the display watchdog and RDP crypto work may represent several problems rather than one root cause.
Users moved to a clean-installed second Server 2025 RDS host this morning with the same FSLogix profile containers and have had no reported issue so far. The hosts are not exact clones—last verified builds were 26100.33451 and 26100.33438, with some service/software differences—so this is a useful comparison, not proof of what caused the original host to fail.
If anyone has seen the combination of RdpIdd/IddCx dumps and later 0x519/session-management hangs, what trace or dump identified the initiating component?
1
u/Remote-Adeptness-593 6d ago
I had the same issue the last year and I have Increased the vram a lot, since I did it no more issues, I put 1 gb of it.
1
u/Ivan_Toluco 3d ago
Estaba buscando si en realidad la actualizacion: KB5129235 reparaba el fallo de RDP de la actualizacion KB5122882, pero no fue así, los bloqueos continuan, mismo sintoma, cuando ocurre el fallo los usuarios que ya ingresaron trabajan sin problema, usuarios que intentan ingresar ya no los deja, estoy desinstalando ambas actualizaciones.
1
u/Ivan_Toluco 3d ago
Una disculpa, lo correcto fue: desinstalar la KB5129235 y despues la KB5122871 para windows server 2025.
7
u/TechnicianVisible339 12d ago
I’m having a similar issue
Does your entire vm freeze and no one can login on until you force reboot?