Windows
Azure Virtual Desktop was slow because the VM maxed out CPU
The remote desktop in AVD was sluggish because the VM was on a 2-core legacy size and the CPU was hitting 100% during normal use. It was resized to the newer D4ads_v5 4-core / 16 GB size and brought back online.
Killed once by someone from XL.net, on 2026-09-25.
Affects
Apps
- Azure Virtual Desktop
Hardware
- 2-core legacy VM size
- D4ads_v5 4-core / 16 GB VM size
What you see
- CPU regularly hit 100% during the workday while memory and storage still had room.
Why it happens
Likely The VM did not have enough processing power for normal use; the 2-core legacy size was saturating CPU.
When it shows up
An Azure Virtual Desktop session feels slow and the VM is a 2-core legacy size with CPU pegged at 100%.
You are in this case if:
- Standard_E2as_v4 (2 cores)
- CPU at 100% during normal use
- Memory and storage not under pressure
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Someone from XL.net killed this on a Windows computer on 2026-09-25. It is written up from that one repair, so it cites no outside page.