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

76 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-06-15T01:07:34+00:00

    I had good luck with a 32 GB USB drive where 8 GB and 16 GB failed.  Even with that, one system would not install until I removed an SD card.

    Hi, 

    I think I figured out why some different USB devices are not blocked on this upgrade.

    If I use any USB device that does not have the (Removable Media Bit) the upgrade works fine.

    There are still some USB flash drives out there that do not show as removable and those don't trigger the trap. 

    Also running the upgrade from a folder on a USB HDD work fine because those don't show as removable.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-07-09T03:35:32+00:00

    Good to see that you get it work. 

    It seem that there is differences on USB devices depend on is it memory stick or external disk.

    Most of the time I use WU to update Insider previews, so I use USB -installer

    only for clean install's, but I start testing this issue just for fun on rainy Sunday.

    That thread is in Insider forum, but "May Update 1903 is out" whole discussion is about released v1903, not previews.

    Hi Pauli O, 

    It looks like they just block the devices that show the RMB (Removable Media Bit).

    The upgrade works fine from devices that do not have the Removable bit on.

    Anyway, it seems that the block was added in the installation media files created on 4/1/2019 4:59PM (Build 18362.30) .

    MCT is now downloading a new ISO with files created on 6/11/2019 Build 18362.175, this seems to have removed the block for the USB removable from the installer, the upgrade from the USB stick proceeds normally.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-07-09T06:22:31+00:00

    (1) You ran that DISM on it, & it showed 175 (instead of 30)…?...

    DISM  /Get-WimInfo  /WimFile:E:\Sources\Install.esd  /Index:1

    ...That presumes the Installation USB drive mounted as E:.

    (2) With the 30, I got that error message after 3.5 minutes. If the error message doesn't come - does one get a chance to back out of the install? I don't want to run it unnecessarily.

    Was this answer helpful?

    0 comments
  4. Pauli O 16,380 Reputation points Volunteer Moderator
    2019-07-09T06:25:56+00:00

    I just use MCT to download that ISO and that's true, it's updated to give build 18362.175.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-07-09T06:36:33+00:00

    Thanks, Pauli. I'll make a new USB Installation drive, then, no matter - but...

    What about the other question? Does it give a chance to back out of the install past the first 3.5 minutes?

    Was this answer helpful?

    0 comments