Microsoft finds a solution for the issue that prevented upgrading to Windows 10 version 1903

RN is run by readers. When readers purchase through links on our blog, we might earn an affiliate commission.

Microsoft has quietly fixed three big issues with Windows 10 version 1903, one of which was blocking users from upgrading to Windows 10 1903.

The Windows 10 May 2019 upgrade has some issues. Good for Microsoft that it has a page dedicated to documenting them and their fixes. Yesterday in the evening, the page was updated to show three new problems that were resolved by the company.

One of the main issues was that users using a USB drive or memory card attached were not able to upgrade to Windows 10 version 1903. With Tuesday’s update patch, the problem has been taken care of. The cumulative update will be bundled into the upgrade package that you will receive from Windows update.

Another problem that’s been fixed by the company is the loss of audio when using Dolby Atmos headphones or Dolby Headphones theatre. And finally, if you had a loss of functionality with the Dynabook Smartphone Link app, that should be fixed as well.

Despite the company’s promise of increased transparency, the firm has not announced or discussed these important fixes via its corporate blogs. Instead, it has silently updated a known issues page on Microsoft Docs.

If you have been prevented from installing the update because of any of these problems, you will soon able to do so.

Microsoft warns:

“These issues are now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903.”

However, there are two more issues that are still left of the list and yet to be fixed. One this includes Windows Sandbox failing to start and the other is about display brightness not responding to adjustments. The company stated that “we are investigating these issues.” the Sandbox issue, however, should only occur when the OS language has been changed.

With the problems having been fixed as of July 11, you may have to wait until the weekend for the update to show for you.

source

Leave a Comment