The Windows 10 May 2019 Update has experienced a few blocks lifted which have been preventing the upgrade from getting shipped to some PCs – the upshot becoming that you may possibly now be able to get the most up-to-date update if it was staying held again due to a person of these compatibility issues.
The troubles which have been healed, and marked as resolved on the May well 2019 Update overall health dashboard, are as follows:
- Loss of operation in Dynabook Smartphone Hyperlink app
- Audio not performing with Dolby Atmos headphones and house theater
- Mistake attempting to update with exterior USB gadget or memory card connected
The previous just one is the biggie, and it prevented the May 2019 Update from remaining set up on PCs which experienced an external USB gadget plugged in (or an SD memory card).
Naturally it is great to see these concerns banished into non-existence, and in accordance to the overall health dashboard, there are only two flaws which Microsoft hasn’t settled or mitigated.
Individuals are the Windows Sandbox failing to commence and manufacturing an error code (file not discovered) on certain equipment, and an concern with screen brightness not responding to the user’s adjustments (impacting certain Intel exhibit motorists).
Having said that, Ghacks, which spotted this advancement, did observe that there have been a couple challenges which popped up recently that Microsoft has not acknowledged nonetheless, or at the very least are not nonetheless documented on the health and fitness dashboard.
These unaddressed troubles include things like a problem with Microsoft Remote Desktop whereby people are encountering a black display screen due to flaky screen drivers, as nicely as the SFC/Scannow option failing to do the job appropriately.
And, in the newest patch for Home windows 10 May possibly 2019 Update, KB4507453, some products are staying affected by a restart notifications loop: meaning even just after the update is installed, and your Laptop is rebooted, you continue to get a pop-up stating that a restart is necessary (and this persists indefinitely).
If the latter gremlin is basically bugging you, then there is a likely workaround as documented by Günter Born.
However, the May possibly 2019 Update has run really efficiently, especially in contrast with the debacle that was the earlier Oct 2018 Update. We never anticipate any difficulties with the future update for later on in 2019, both, provided that it’s a additional minimal-important affair that will concentrate on building modest tweaks and strengthening functionality.