Another Win10 version 1903 redline bug: Disconnected RDP sessions peg dwm.exe at 100% utilization

Topic

New Reply

Here’s an oldie but goodie just mentioned to me by Günter Born…. In Win10 version 1903, if you use a computer to RDP into another computer, and then
[See the full post at: Another Win10 version 1903 redline bug: Disconnected RDP sessions peg dwm.exe at 100% utilization]

Reply | Quote

Replies

This is a major problem as the old XDDM drivers do not support RDP acceleration/performance boosts like RemoteFX and GPU virtualization. For end-users that need high performance remote desktops this makes the experience pretty awful.

~ Group "Weekend" ~

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

Here’s an oldie but goodie just mentioned to me by Günter Born….

In Win10 version 1903, if you use a computer to RDP into another computer, and then disconnect the RDP session on the second computer (without logging out), dwm.exe redlines one core on the originating machine.

Although Günter says the issue surfaces on the client system, every user report I can find through your links and his (those that specify) say that the problem occurs on the host system (i.e. target machine, not originating machine).

2 users thanked author for this post.

NetDef, woody

Reply | Quote

I noticed the same discrepancy, think it might be a translation glitch.

The CPU core redlining is definitely happening on impacted systems on the RDP host (the target).

I’m seeing this on two machines at the moment, both for clients that like to remote in and use graphically demanding applications. The work-around on forcing the XDDM driver is a total bust for my use-case as the performance drop is too severe to be tolerable.

~ Group "Weekend" ~

2 users thanked author for this post.

b, woody

Reply | Quote

So this happens on the target (puppet) machine, running 1903, when disconnecting but not logging off?

Reply | Quote

Yes. But not all machines that took the patch that started this problem are doing it. I’m looking at them now trying to figure out why.

(Notes: I have five matching machines, only two exhibit this problem. All are on 1903, all have the same video cards and drivers: Quadro P4000 from NVidia. All are patched as of last Sunday.)

~ Group "Weekend" ~

1 user thanked author for this post.

woody

Reply | Quote

And another note: on other forums I see folks saying “Well, like, log off you goofus.”

They totally do not get that logging off is not the right work-around. It’s not at all uncommon to RDP in, start a long winded process, close the RDP session from the client site, and return to it hours later to check on the process.

That single core red-lining slows down the actual work I’m expecting my host computer to complete during my absence.

~ Group "Weekend" ~

2 users thanked author for this post.

woody, b

Reply | Quote

NetDef wrote:

And another note: on other forums I see folks saying “Well, like, log off you goofus.”

They totally do not get that logging off is not the right work-around. It’s not at all uncommon to RDP in, start a long winded process, close the RDP session from the client site, and return to it hours later to check on the process.

You just stopped me from saying that!

Is it recommended to log off from Windows when finished working on a server with RDP?

2 users thanked author for this post.

woody, NetDef

Reply | Quote

What is the impact this problem will have on DejaBlue prevention?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Update on my two wayward RDP host machines:

Updated the video drivers using a clean driver install (NVidia check box during manual setup) to a release from yesterday.

Optimal Drivers for Enterprise'(ODE) branch release for NVidia Quadro P-series Enterprise
Version: R430 U6 (431.86) WHQL
Release Date: 2019.9.4
Operating System: Windows 10 64-bit

I’m no longer seeing a core redlining when I leave PerfMon running in the background and close the RDP session.

I do NOT see new drivers from NVidia for the consumer lines (August dates) that might address this issue. If I owned those cards I would be keeping a watch out for an upcoming driver.

~ Group "Weekend" ~

2 users thanked author for this post.

woody, b

Reply | Quote

NetDef wrote:

Update on my two wayward RDP host machines:

Updated the video drivers using a clean driver install (NVidia check box during manual setup) to a release from yesterday.

Optimal Drivers for Enterprise'(ODE) branch release for NVidia Quadro P-series Enterprise
Version: R430 U6 (431.86) WHQL
Release Date: 2019.9.4
Operating System: Windows 10 64-bit

I’m no longer seeing a core redlining when I leave PerfMon running in the background and close the RDP session.

I do NOT see new drivers from NVidia for the consumer lines (August dates) that might address this issue. If I owned those cards I would be keeping a watch out for an upcoming driver.

Why do you point at NVidia as the culprit and not at Intel’s Built-in GPU ?

Reply | Quote

I don’t use Intel GPU’s on workstations. This is specific to one (of many) GPU interactions. YMMV.

Perhaps given this question I should point out that WDDM drivers come from:

a) Microsoft for VM’s and where none other is available for onboard GPU’s.
b) Some driver packages for commercial video cards/circuits.

Also of note is that NVidia and AMD provide special WDDM drivers for their enterprise cards specifically designed to increase RDP performance. (They may also do this for “gaming” cards, but I would not know.)

Intel may provide such, but I hate their driver update frequency. Slow to fix video issues.

~ Group "Weekend" ~

1 user thanked author for this post.

Microfix

Reply | Quote

IoW nvdia Quadro’s are far superior in drivers and 2D performance over intel generic stuff.
Favoured by my myself for CAD and design work for many years without some of the GeForce GPU gaming extensions.
Matrox used to do this with their cards also years back..

Windows - commercial by definition and now function...

1 user thanked author for this post.

NetDef

Reply | Quote

And as a side note of interest, the workstations I was servicing earlier today were exactly for those apps: AutoCAD and Revit . . .

~ Group "Weekend" ~

Reply | Quote

I RDP from a 1903 to another 1903 and have not seen this issue myself.

1 user thanked author for this post.

b

Reply | Quote

I can’t find a consistent thing to point a finger at myself. I had more than two machines that matched, but only the two were suffering from this problem. Makes no sense unless something random is being corrupted in the patching process.

Intermittent and inconsistent issues are really hard to accurately diagnose.

~ Group "Weekend" ~

Reply | Quote

I know this is specific to RDP… but I’m having Serious doubts now about going from Win8.1 to Win10 1909 AKA “1903 Service Pack”. If 1903 is as buggy as it is this month & probably next, how confident can I be that 1909 has cleaned up the goofs? & isn’t introducing new bugs… uhh, Features not in 1903?!

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

I’ve experienced (or had no reports of) none of the bugs Woody has reported at home and at work with several dozen 1903 machines.

I’m not saying these bugs don’t exist, but they’re not being widely reported on /r either, which is typically the first place where people lose their minds over Win10 issues.

Several posters here have reported similar findings with their 1903 machines/environments, ie no issues.

2 users thanked author for this post.

WildBill, b

Reply | Quote

@woody

Here’s an update on what happened in my test lab yesterday. (Recapping a bit from above posts, sorry . . . )

Five machines, matching hardware, all on Windows 10 Pro 1903. GPUs are from NVidia’s Quadro P-series line (last years models.)

Out of those, only two machines were exhibiting the CPU red-line (on one core) bug for RDP when the client disconnected without first logging off. They both started doing this right after I allowed the August 2019 patches on them over the last weekend.

At first I solved the problem by installing the latest drivers from NVidia. And that worked, but it bugged me that the other three had not needed the special attention. And now that I’ve found the difference, not certain that installing the drivers did all that much except reset something in the guts of RDP to address the correct WDDM drivers. (This is a theory, I really don’t know.)

Took me a while to find a real difference, but turns out that on the two machines with the problem, both had the Intel GPU (on their motherboards) enabled in BIOS – an oversight on my part when they were configured. The other three machines (which were behaving fine) had their Intel GPU’s DISABLED in Bios.

Hope this helps someone else with the problem.

~ Group "Weekend" ~

2 users thanked author for this post.

woody, Paul T

Reply | Quote