What needs your attention "This PC Can't be upgraded to Windows 10" error message while upgrading to Windows 10 May 2019 update [Fix]

This pc can't be upgraded to windows 10, this will be the error message you are gonna get while installing latest windows 10 may 2019 update. With the final build already on release preview wing for insiders,  Today, Microsoft announced that the users of windows 10 while upgrading to upcoming Windows 10 May update will see the above error message with text "Your PC has hardware that isn't ready for this version of Windows 10. No action is needed. Windows Update will offer this version of Windows 10 automatically once the issue has been resolved" (Ref, below image).

You might have high end specs that can run many OS simultaneously, but you will still see the error message because of an simple issue.

So, what is the fix/ solution?

Simple, just remove the plugged in external storage, and restart your update, it will now work without any hassles. for example: if you had plugged in your USB drive or any device on usb port, then remove it, and try again, that's it.. 

Here is what Microsoft says about the cause,

Inappropriate drive reassignment can occur on eligible computers that have an external USB device or SD memory card attached during the installation of the May 2019 update. For this reason, these computers are currently blocked from receiving the May 2019 Update. This generates the error message..

Example: An upgrade to the May 2019 Update is tried on a computer that has the October 2018 update installed and also has a thumb drive inserted into a USB port. Before the upgrade, the device would have been mounted in the system as drive G based on the existing drive configuration. However, after the upgrade, the device is reassigned a different drive letter. For example, the drive is reassigned as drive H.

Note The drive reassignment is not limited to removable drives. Internal hard drives can also be affected.

So, will there be any official fix?

Microsoft says, the issue will be resolved in future service updates, and the issue will be fixed for insiders in the windows insider build 18877. Until then, follow the above fix.

Last updated on April 24,2019.