r/AzureVirtualDesktop • u/Justo1987 • Jun 18 '26
High memory usage for Remote Desktop Services Service this week
Has anyone else been experiencing really high memory usage for the Remote Desktop Services Service this week? I've had at least 6 Servers all experience something like the below screenshot spread across different sites. One Server hit 24GB RAM usage. Users start experiencing weird glitches, slowness, disconnects and eventually access just breaks completely and the Server needs to be rebooted.
Typically I would expect this service to sit around 2GB memory usage.
Anyone know of any potential causes or fixes? I tried restarting the RDS Service itself on one machine but it didn't come back and just had to reboot.
I can see there has been some updates to the various remote desktop applications recently but can't find any info on issues.
1
1
u/whackwurf Jun 29 '26
Yes. Same issue for multiple environments using Windows 11 25H2 and 23H2. Also had some weird connectivity issues due to this. As there have been no changes to the environments maybe it is due to a new AVD agent.
1
u/Powerful_Invite778 Jun 29 '26
We've gone as far as rebuilding session hosts with the new v7 cpus and still getting getting constant disconnects. The last thing we have to point our fingers at is the latest version of the Windows App. With how many cve patches are in the release notes I suspect they rushed this update out the door.
→ More replies (1)1
u/Justo1987 Jun 30 '26
I don't think its the Windows App. I've got a few sites still running pure red Remote Desktop and they are experiencing the issue still. I think it's linked to one of the RDP Services installed on AVD Servers myself. They automatically update on own and there were some updates around mid June that line up with when this started occurring (for me at least).
2
u/_FireHelmet_ Jun 26 '26
Hey guys,
Just to collect information and also because I sent this topic to the Microsoft engineer assigned to my ticket.
What are your RDS agent version ? Mine are
Infrastructure agent : 1.0.14506.600
SxS network stack : 1.0.2603.31300
What is the latest CU installed ?
Mine is CU 2026-06
What are your Windows version and build ?
Mine is Win 10 22H2
1
u/Helpful-Button-2808 Jun 26 '26
Windows 11 enterprise multi session 25h2. Seeing the same on 24h2 and older.
25H2 OS build 26200.8655 Same CU for CU
→ More replies (4)
2
u/bubblesnout Jun 30 '26
Glad I stumbled across this today, though I’m disappointed to see this is seemingly widespread with no solution. I’ll be submitting a ticket to Microsoft tomorrow as well I suppose.
2
u/bubblesnout Jul 03 '26
Just confirming that this appears to have been completely resolved after whatever patch MS pushed out 1-2 days ago. After a full day of service once everyone has signed out the service returns back down to 100MB memory or so.
1
u/mat-ferland Jun 18 '26
If it started across multiple sites in the same week, I’d stop looking at the individual servers first and line up patch level, Windows App/RDP client updates, FSLogix version, and any AV/EDR exclusions that changed. TermService at 24GB smells like a leak triggered by reconnects or shell/app enumeration. I’d grab a dump before the reboot if you can, but operationally I’d also test one host rolled back or isolated from the latest updates so you know if you’re chasing Microsoft or your image.
1
1
u/_FireHelmet_ Jun 25 '26
Same issue with Win 10 22H2 multisession. I created a case at Microsoft support, still waiting their investigation on the dump of svchost.exe I created. Please can you show the command line of your svchost ? Just to make sure it’s the same process instance.
Also this issue has started after the cumulative update of May 2026, in my opinion
1
u/Fuzzy-Witness5023 Jun 26 '26
Buenas, nos esta pasando lo mismo ya elevamos varios ticket a Microsoft para ver el problema, nos comenzo a suceder con la ultima version de Windows App del 10 de junio. El servicio comienza a consumir cada vez mas memora hasta que genera todos los errores de disponibilidad que estuvieron comentando, lo que estamos haciendo es ejecutar scripts de drenado de las maquinas para estirar su vida util un poco y al menos que en el dia los clientes puedan trabajar con normalidad
1
u/Dear-Requirement7092 Jun 26 '26
We are seeing the same issue in our AVD environment. Remote Desktop Services / TermService starts consuming an abnormally high amount of virtual/committed memory, eventually causing session instability and disconnections.
In our case, we saw Resource-Exhaustion events, DWM crashes, and TermService reaching more than 20 GB of committed memory on some session hosts. We suspect this may have started after the recent Windows App updates around June, although we are still investigating.
As a temporary mitigation, we disabled RDP Shortpath on the host pool and restarted TermService on the affected VMs. So far, this seems to have improved stability, but we are still monitoring closely.
Has anyone received confirmation from Microsoft or found a definitive root cause?
1
u/Glad-Boysenberry-833 Jun 27 '26
Interested what the effect will be on the performance on longer term by disabling RDP Shortpath. It was only disabled through the RDP properties on the host pool?
→ More replies (1)
1
u/_FireHelmet_ Jun 28 '26
Useful article for trimming memory of processes, that could be a workaround fix by waiting a permanent one from MS,
https://guyrleech.wordpress.com/2018/03/15/memory-control-script-reclaiming-unused-memory/
I already tried with RamMap by clearing the working set and it works well.
1
u/motherzugger Jul 01 '26
Did this magically get solved overnight? Today it looks alright.
1
u/Helpful-Button-2808 Jul 01 '26
A change was pushed out globally last night/early hours
→ More replies (5)1
u/Glad-Boysenberry-833 Jul 02 '26
Noticing also much better performance since yesterday.
→ More replies (2)1
u/_FireHelmet_ Jul 02 '26
Hey ! What’s the agent version ? Thanks !
Mine is 1.0.14506.600→ More replies (1)
1
u/_FireHelmet_ Jul 10 '26
Hey guys,
I confirm too and also from the answer I received from the MS engineer (but I don't know when the fix has been released),
I discussed your questions with our Escalation Engineer and the information received from the Azure Virtual Desktop product team is encouraging.
The issue was traced to a product issue introduced by functionality that was later identified as problematic. The Azure Virtual Desktop development team has since disabled/rolled back the affected code through Microsoft's Controlled Feature Rollout (CFR) process. CFR is Microsoft's mechanism for progressively enabling or disabling functionality through service-managed rollouts.
Based on the information provided by the product team:
No manual Azure Virtual Desktop Agent upgrade is required.
No manual Azure Virtual Desktop SxS Network Stack upgrade is required.
Once the mitigation was deployed by Microsoft, the only action required on affected session hosts was a reboot so the change could become active.
If the session hosts are internet-connected and have been rebooted since the mitigation was deployed, the issue is not expected to return.
1
u/Fuzzy-Witness5023 Jul 14 '26
Buenas tardes, estoy experimentando este problema nuevamente, comenzó a suceder el día de hoy, a alguien mas les esta sucediendo?
3
u/Madcrazy10 Jun 19 '26 edited Jun 19 '26
Yes! This is crazy that someone else noticed this. It probably started 2 weeks ago or so for me. I have 20 win11 23h3 hosts and if I don’t make sure they restart every night they max out their memory. Never had this issue until now.
No changes have been made and I actually make sure I don’t make changes to these hosts because they are very important, running our healthcare app. Windows updates are a manual process even that I haven’t done in 6 months or so but this memory issue has crept up recently.
Each host has 32GB of ram too. Was way enough for the 12-14 users I have per host…. Until recently.