Win 10 1903 May 29, 2019—KB4497935 (OS Build 18362.145) still fails the update from a USB stick.

Anonymous
2019-06-01T01:04:11+00:00

According to the description of the fixes in KB4497935 the bug with the USB devices should have been fixed, but it still does not allow updates with installation media on a USB stick.

Fix description:

"Addresses an issue that may cause an external USB device or SD memory card to be reassigned to an incorrect drive during installation. For more information, see "This PC can't be upgraded to Windows 10" error on a computer that has a USB device or SD card attached"

I tried to do an update with installation media build 18362.145 on a system already at 18362.145 and still gets the error message below:

 

Is there a fix yet for this bug in the v 1903 release ? Which build do I need to get this bug fixed ?

I know that I can work around the issue installing from a local drive.

Also if I try upgrading from1903 to a preview 20H1 build 18908.1000 using a USB stick the update completes without this message.

I hope we don't need to wait for 20H1 to get this bug resolved.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

76 answers

Sort by: Most helpful
  1. Anonymous
    2019-06-03T02:51:05+00:00

    "Why do you accept the highlighted text as fact?

    I believe Microsoft is trying to find a way to install on systems which don't have the space needed on the OS partition to complete the install. 

    For years, the EFI system partition was being assigned a drive letter, in error, on some systems.  It has never happened to me, but has happened to many folks.

    The 32 GB partition size may be relevant because many systems had a 32 GB prefetch drive or tablets were sold with 32 GB drives.  Using Rufus to set up a Install Media drive my be outside the box since it creates 2 partitions, not just the FAT 32 maximum size partition of 32 GBs.

    But i agree, it is too bad the conversation seems to revolve around the install as opposed to the actual  build upgrade... I think I am going to make good use of the Sandbox in 1903.."

    Saltgrass, 

    Why should all this make a difference on what type of USB stick is blocked out by the installer?

    In your case you said it worked fine with a 32GB Sandisk Glide, while in my case it fails with a 32GB Sandisk Ultra on 5 different machines.

    I use the same 32GB SanDisk Ultra and I have no problem doing any upgrade using any version of windows from 1709, 1803, 1809 or 20H1.

    It only fails with the released version 1903. They just need to fix it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-06-03T02:28:28+00:00

    The fact that the installer is blocking only some of the USB devices seems just another mistake of MS, they tried to prevent the problem that caused the dive letter reassignmentduring installation and for that they should have blocked any USB storage device. 

    Why do you accept the highlighted text as fact?

    I believe Microsoft is trying to find a way to install on systems which don't have the space needed on the OS partition to complete the install. 

    For years, the EFI system partition was being assigned a drive letter, in error, on some systems.  It has never happened to me, but has happened to many folks.

    The 32 GB partition size may be relevant because many systems had a 32 GB prefetch drive or tablets were sold with 32 GB drives.  Using Rufus to set up a Install Media drive my be outside the box since it creates 2 partitions, not just the FAT 32 maximum size partition of 32 GBs.

    But i agree, it is too bad the conversation seems to revolve around the install as opposed to the actual  build upgrade... I think I am going to make good use of the Sandbox in 1903..

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-06-03T01:52:59+00:00

    "

    B.T.W.

    I just tried opening the Windows.iso from the USB sticks that failed earlier and they fail the same way.

    This shows that 1903 windows installer is blocking specific USB devices, but not all.

    So until they fix the bug,  USB SanDisk Ultra is just good for a clean install or for recovery when you need to restore a WindowosBackup image.

    I understand why you don't want to leave a windows.iso on the C: drive because it would increase the backup time of your system image.

    "

    OK - some USB sticks are just plain poison for doing an over-install. Interesting that they work for a clean install. Also - that message says "your PC has hardware that isn't ready for this version of Windows 10". But now I've got that version - & the USB sticks work just fine!

    The whole thing is really fishy. Nevertheless, I congratulate Microsoft for 1903 - looks great to me.

    PCR, 

    there is nothing wrong with the USB sticks. They work fine with all previous versions and the future preview versions.

    The fact that the installer is blocking only some of the USB devices seems just another mistake of MS, they tried to prevent the problem that caused the drive letter reassignment during installation and for that they should have blocked any USB storage device. By mistake they only limited the filter to some of them, probably just the ones they had available when they implemented the temporary block on the installer.

    The fact that the upgrade works with some USB storage devices is just by luck, not by design.

    I think they just rushed in a temporary block for USB devices on 1903 windows installer and it was not checked out properly.

    Now that the original bug has been fixed they should just remove the block and release a new Installer together with a build 18362.145 or higher.

    P.S.

    I assume you don't have a DVD on your PC ?

    Doing the upgrade from the DVD works fine too.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-06-03T01:19:08+00:00

    "

    B.T.W.

    I just tried opening the Windows.iso from the USB sticks that failed earlier and they fail the same way.

    This shows that 1903 windows installer is blocking specific USB devices, but not all.

    So until they fix the bug,  USB SanDisk Ultra is just good for a clean install or for recovery when you need to restore a WindowosBackup image.

    I understand why you don't want to leave a windows.iso on the C: drive because it would increase the backup time of your system image.

    "

    OK - some USB sticks are just plain poison for doing an over-install. Interesting that they work for a clean install. Also - that message says "your PC has hardware that isn't ready for this version of Windows 10". But now I've got that version - & the USB sticks work just fine!

    The whole thing is really fishy. Nevertheless, I congratulate Microsoft for 1903 - looks great to me.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-06-03T01:02:49+00:00

    That's right, I was able to run the .iso off my Seagate HDD (plugged into a USB port), & fg2001 could run it off a Maxtor.

    So - in that other thread you said you could make this site look different...

    https://www.microsoft.com/en-us/software-download/windows10

    Download Windows 10 - Currently, this is version 1903

    You said, hit F12 (which is a toggle) for developer mode [or Edge, More (…), More Tools, Developer Tools], & set it to emulate "Lumia 950 (or use some another OS than Windows)". Then, you get more choices for an .iso.

    I can hit F12 OK - but how do I do the emulation? Not that I want a different .iso than I've got which works just fine. But I want to know.

    Was this answer helpful?

    0 comments No comments