14 DAY TRIAL // Windows 10 May 2019 Update is now available for download, and Microsoft is now working on resolving any issues that users might come across in order to move forward with the public rollout.
The company has confirmed three issues in the May update, and all of them are under investigation as we speak, with users recommended to avoid upgrading until a fix goes live.
Display brightness may not respond to adjustments
First and foremost, this is an issue that only exists on Intel devices, and according to Microsoft itself, it’s caused by a driver compatibility error.
“After updating to Window 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change,” Microsoft explains.
The workaround in this case is to reboot your device to apply brightness changes, and Microsoft says it blocked the upgrade on devices that might be impacted by the issue. A fix is on its way, with no ETA for the time being.
Audio not working with Dolby Atmos headphones and home theater
Next, Microsoft says that some Dolby Atmos devices could experience loss of audio after installing the May update because of a licensing configuration error.
“This occurs due to an issue with a Microsoft Store licensing component, where license holders are not able to connect to the Dolby Access app and enable Dolby Atmos extensions,” Redmond says.
No workaround is available in this case, and Microsoft promises a fix in mid-June.
Duplicate folders and documents showing in user profile directory
Users installing Windows 10 May 2019 Update could end up with empty folders in libraries if they redirected known folders.
“This may occur if known folders were redirected when you chose to back up your content to OneDrive using the OneDrive wizard, or if you chose to back up your content during the Windows Out-of-Box-Experience (OOBE). This may also occur if you redirected your known folders manually through the Properties dialog box in File Explorer. This issue does not cause any user files to be deleted and a solution is in progress,” Microsoft notes.
No workaround exists for this problem either, and Microsoft says a fix is coming later this month.