Windows 10 V1903: Known Issues – Part 3

[German]Windows 10 May 2019 Update (Version 1903) has been released to the public since May 21, 2019. Nevertheless, there are some upgrade blockers that Microsoft has set to V1903 for the installation of the feature update. Since Microsoft released this Windows 10 version at the end of September 2019 for broad use', I continue the series of articles described in Part 1 and Part 2 in Part 3.

Similar to Windows 10 V1809, Microsoft maintains a list of known issues for Windows 10 May 2019 Update (Version 1903). This list is available here and is constantly updated. 

Meanwhile Microsoft has worked through most of the problems on the list. Below I describe issues confirmed by Microsoft and in addition bugs, which came to under my eyes.

Issues with Wi-Fi adapters

Some older computers may lose Wi-Fi connectivity due to an outdated Qualcomm driver. A remedy is an updated Wi-Fi driver from the device manufacturer (OEM), if available and if this driver works. Microsoft has therefore blocked the feature update to Windows 10 version 1903 for these machines with an older Windows 10. I had reported about that within the blog post Windows 10 V1903: Know issues (Wi-Fi etc.) updated. Meanwhile I have received feedback that it also affects certain Intel and Realtek chips. 

RDP issues (black screen, CPU load)

Administrators repeatedly reports issues with remote desktop connections in Windows 10 V1903. In mid-July 2019, I published the blog post Windows 10 V1903: Remote Desktop shows Black Screen, which deals with the black window in RDP sessions. Microsoft has fixed this bug, but there are blog readers who are still affected by this problem. In addition, the Microsoft patches did not fix the problem that RDP connections generate a high CPU load. I had addressed that within my my blog post: Windows 10 V1903: RDP (dwm.exe) causes high CPU load, freezes VMs. Both articles describe a workaround for this issue.

Surface Book 2 and the Nvidia GPU

Windows 10 May 2019 update causes trouble with the Surface Book 2 if an NVIDIA GeForce GTX 1060 is installed. The graphics processor on the add-on card is randomly separated, affecting the graphics performance of Surface Book 2. I reported this in the blog post Surfaces Book 2: Issues with Windows 10 V1903 and Nvidia. To my knowledge the problem has not been fixed yet.

OneDrive Personal Vault returns error 0x80070057

Recently Microsoft rolled out OneDrive Personal Vault (see the announcement). Within this German comment, a user points out that he receive error 0x80070057 when unlocking. The code 0x80070057 stands for ERROR_INVALID_PARAMETER. The cause could be a moved OneDrive folder on drive D:, as the user supposed.

Grouping the Download Folders

A German reader explicitly pointed out an annoying problem with Windows 10 V1903 to me – but I've already seen this elsewhere.

Especially annoying is the problem that in 1903 the grouping in the downloads folder has been activated and you don't seem to be able to do this. It can be permanently deactivated via the normal GUI mechanisms. The network is full of people who have the same problem and who are
Question I have received tips on how to process the registration, only
1. should that simply not be necessary and 2. has it with me also
no permanent remedy has been found.

The problem is also discussed on the Internet in the Technet Forum, on Microsoft Answers and here and here. The reader writes:

For me this is clearly a bug in 1903, by default activated grouping fine and good, but the normal view settings of the Windows Explorer should be able to overwrite that and exactly that seems to be just not the case anymore.

In the meantime I got a tweet from Jen Gentleman (Microsoft employee on the topic:

Hey Jen – why do you like having your files grouped by date rather than sorted alphabetically?

Me: pic.twitter.com/dE6cJxJ2Yc

— Jen Gentleman (@JenMsft) September 15, 2019

File History causes trouble

The file version history allows you to back up files to a separate drive. The German reader send me an e-mail with the following text:

The second question was recently asked by customers: There File
History with a retention time of X. Finally ran but the NAS is still full because there are significantly more fuses than X were present. A manual and manually triggered automatic Cleanup via Task Scheduler and fhmanagew works fine.

The question, however, is whether this is the way MS is meant to do it and whether you can really I have to take care of the cleanup myself? In my opinion, the GUI and the documentation give a different impression, snapshots of images created at wbadmin are automatically cleaned up etc.

There is a discussion in the Technet forum, but there is not workaround or mitigation in view. The reader writes:

At least, again, somehow nobody seems to have a definitive answer but many has the the same question, if that's the way it's supposed to be a bug.

Is there a copy speed problem?

There may still be a problem with copying files on Windows 10 version 1903, where speed is slowed down after 10 seconds. The effect is discussed in the blog post Windows 10 V1903: Is there a speed drop during file copy?

Issues caused by Updates

Updates rolled out by Microsoft for Windows 10 in July, August and September may also cause issues. Here an outline, without claim to completeness.

Windows Server 2016: No access to SMB shares (KB4507460)

In the comments to a German article, user Chrisrian Lungwitz points out problems with SMB shares under Windows Server 2016. 

I have had problems with a Windows Server 2016 since the current patchday. I can't access SMB shares anymore. Neither the "normal" nor the admin shares (C$). On the server itself you can see the shares but still not access them.

User Alex confirms the same effect in this comment, citing Remote UAC as the reason for the access block on administrative shares.   

Remote UAC prevents the connection to the administrative shares.

A workaround is to set the  LocalAccountTokenFilterPolicy. This is done in the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system

set the DWORD value LocalAccountTokenFilterPolicy=1 and restart Windows.

Search and start menu problems

In connection with the August 2019 update KB4512941 there were problems with some users. The desktop search did not work anymore or a high CPU load by Cortana occurred. I had reported about it in several blog posts (see Windows 10 V1903: Search and Cortana bug in Update KB4512941 confirmed (09/05/2019)).

Microsoft states that the bugs that occurred with the August 2019 update KB4512941, such as broken desktop search or high CPU load, were fixed by Cortana. But I have further reader feedback where the problems still occur. These problem reports have also come to my attention occasionally on the web (see Windows 10: Issues with Updates KB4522015, KB4522016 / KB4517211 (Sept. 2019)). 

Printer issues with Update KB4517211

Since the KB4517211 update released in September 2019, some users have reported printer issues in Windows 10 V1903. I had mentioned this as an isolated case in the article Windows 10: Issues with Updates KB4522015, KB4522016 / KB4517211 (Sept. 2019) (the article mentions also other issues). In the meantime I have some confirmations from different sources (see Windows10 V1903: Update KB4517211 causes printer issues).

Articles
Windows 10 V1903: Known Issues – Part 1
Windows 10 V1903: Known Issues – Part 2
Windows 10 V1903: Known Issues – Part 3

Similar articles:
Windows 10 Mai 2019 Update released
Windows 10 N: Media Feature Pack for Version 1903 released
Windows 10 V1803 threatens a forced update as of July 2019