I've just completed some upgrade work and found that without updating 1903 to 1909 but simply by updating AMD chipset and video drivers to the latest, the RDP/Hyper-V problem has fixed itself (even...

Mostly retired but still keenly interested in all things technical.

I've worked in a number of industrial automation/control industries since the late 70's including the occasional stays on oil...

I'd left a Win10 1903 system running with WDDM disabled via local group policy but when investigating why the VM had once again become problematic, found the policy had reverted back to 'Not...

jimbo45 & Ben Hastings

Thanks for the useful info.

In previous years I'd jump onto following through and trying it out but, in this 'Windows As A Service' epoc we're forced to endure, it seems...

Currently looking at going with LTSC as we really only need Windows 7 functionality but the security included in later editions. Everything else is unwanted junk that has done little other than to...

Thanks for your input.

Although I couldn't see how checking the services listed and adding the config'n changes would impact on a previously working setup that failed when KB4512508 was applied...

Thanks for that tip.
In the mean while, MS released (in the last 24 hrs) KB4512941 as a follow on to KB4512508. I tried it to see if it fixed the subject problem but, unfortunately, it didn't. ->...

Restoring to earlier snapshot also worked for me. Problem is that it's really hard to stop updates trickling in from MS. I've currently paused them until late September (being the longest I can...

I'm also experiencing similar problems starting last Friday after updates were installed with Windows 10 Pro x64 1903 host and guests. Enhanced sessions from host's Hyper-V Manager and also RDP...