[German]Microsoft has updated its Status Summary page for the Windows 10 May 2019 Update. In addition to three removed upgrade blockers, two new known issues have been confirmed – one, the Surface Book 2 dGPU issue is an upgrade blocker. However, regular blog readers may know these issues – and in contrast to Microsoft – there is a workaround for the black windows on remote desktop sessions, which is documented within the blog here.
I just blogged a few hours ago about the fixed issues that has blocked an upgrade to Windows 10 May 2019 Update (see my blog post Windows 10 V1903: Further 3 upgrade blockers removed). Now Microsoft has added two ‘new’ known issues to the KB article with the status of upgrade issues with Windows 10 Mai 2019 Update.
Surface Book 2 dGPU may occasionally disappear
Coincidence? A few hours ago, MVP colleague Barb Bowman answered on Twitter about my blog post mentioned above, that she doesn’t understand why Microsoft doesn’t address the Surface Book 2 problem and blocks the feature update to Windows 10 version 1903.
— Barb Bowman (@barbbowman) 13. Juli 2019
I’ve described this issues within my blog post Surfaces Book 2: Issues with Windows 10 V1903 and Nvidia already in June 2019 – and Barb knows this article. Maybe it was Barb’s tweet addressing me (@etguenni) and also @WindowsUpdate reminds the Microsoft team to document this issue. A short time later Barb added that Microsoft has added the dGPU issue to the KB article. Titled ‘The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU’ Microsoft write:
Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Window 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open.
The feature update to Windows 10 V1903 was therefore blocked on the Surface Book 2.
Black screen on Remote Desktop
The second bug that has been confirmed concerns the black screen in remote desktop sessions that occurs with certain older graphics chips. Microsoft writes about this in the KB article in a section, titled ‘Initiating a Remote Desktop connection may result in black screen’:
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).
This applies to both Windows Server 1903 and Windows 10 V1903 clients – but probably only in enterprise environments, since Remote Desktop is not available under Windows 10 Home. Microsoft is working on a solution to fix this issue.
Just for the records: If you need more information, I’ve documented that issues a few hours ago within my blog post Windows 10 V1903: Remote Desktop shows Black Screen. What Microsoft doesn’t told us within the kb article linked above: There is a workaround for administrators. You can block the loading of the new WDDM graphics driver for remote desktop sessions via group policy. Several people have now confirmed to me that this works. By the way, it didn’t grow on my crap. A blog reader from Hong Kong thankfully left me a comment as a tip on the English-language article (see the article linked above).