Microsoft will block Windows 10 May 2019 update if you have a USB drive or a connected SD card



[ad_1]

Blocked!

If you have external storage connected to your computer, you may find that you can not install the Windows 10 May 2019 update when it is released next month.

As an obvious precaution, Microsoft decides to block the installation of the update if a computer is equipped with an external USB drive or an SD card. Blocking has been introduced because it is concerned that drive letters may be inappropriately reassigned during installation.

See also:

In a support article, Microsoft warns that some people may see an error message when they try to install the May 2019 update. "This PC can not be upgraded to Windows 10 "could display if, like many people, a USB device or SD card is connected.

You can see what the error message looks like here:

Windows 10 May 2019 Update installation error

Microsoft explains that:

An inappropriate drive reassignment may occur on eligible computers to which an external USB device or SD memory card is connected during the installation of the May 2019 update. For this reason, the May 2019 update is currently stuck on these computers. This generates the error message that is mentioned in the "Symptoms" section if the upgrade is attempted again on an affected computer.

The company then gives an example of what could happen:

Example: An upgrade of the May 2019 update is attempted on a computer on which the October 2018 update is installed and a USB key is also inserted into a USB port. Prior to the upgrade, the device would have been mounted in the system as a G drive based on the existing drive configuration. However, after the upgrade, the device is assigned another drive letter. For example, the drive is reassigned as drive H.

At the moment, the advice is to simply unplug the USB drive or SD card and restart the installation of the update, but an appropriate fix is ​​being prepared. Microsoft says:

This problem will be resolved in a future maintenance update for Windows 10. For Windows Insiders, this problem is fixed in versions 18877 and later.

Image credit: Aquir / Shutterstock

[ad_2]

Source link