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-02T02:39:31+00:00

    Hi PCR, 

    On one of my machines, windows update offered the upgrade from 1809 to 1903 the first day it was available on 5/21/2019, but not on any of the other ones.

    Since that worked fine, I decided to upgrade all the other machines by downloading the 1903 installation ISO using the media creator 1903 available on the MS site.

    That ISO turned out to be build 18362.30.

    Anyway when I tried upgrading from the USB that I created it was blocked in every machine including the one that was already at 1903 for the reasons explained in this link:

    https://support.microsoft.com/en-us/help/4500988/windows-update-hold-for-windows-10

    I then decided to do the upgrades directly from the mounted ISO file residing on an internal local drive and everything worked fine.

    After that, windows update downloaded all the fixes to bring up the machines to build 18362.145. (KB4497935)

    Now I was just trying to see if they also fixed the Windows installer to work from the USB stick, or when any USB disk is plugged in,  but clearly they did not, at least not yet.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-06-02T03:08:37+00:00

    I tried to outsmart the process by pulling the USB at the "downloading" stage, but quickly got a message saying "we can't tell" whether the computer is "ready".

    OK, thanks for your experience, fg2001. I'll go for the .iso (or maybe try a Memorex 16 GB) only if I become impatient again, but for now am cured of it. Thanks again, & thanks to Saltgrass for the idea of trying other USB media.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-02T03:47:06+00:00

    I tried to outsmart the process by pulling the USB at the "downloading" stage, but quickly got a message saying "we can't tell" whether the computer is "ready".

    OK, thanks for your experience, fg2001. I'll go for the .iso (or maybe try a Memorex 16 GB) only if I become impatient again, but for now am cured of it. Thanks again, & thanks to Saltgrass for the idea of trying other USB media.

    Now I'm confused.

    Do you have a USB disk plugged in all the time ?

    If you can leave out all the USB drives and download the Windows.iso file to an internal drive using the MediaCreationTool1903.exe.

    You don't need any USB drive at all to do the upgrade.

    You can always create the USB media later from the ISO file if you need it for recovery or want to do a new clean install.

    What is the configuration of your  machine ?

    Was this answer helpful?

    0 comments
  4. Pauli O 16,380 Reputation points Volunteer Moderator
    2019-06-02T03:47:36+00:00

    I continue testing from where I left yesterday.  It's not just setup.exe that cause this issue.

    I copy setup.exe from 1809 ISO and same failure with same USB as used before.

    Next I create USB installer from 1809 ISO, but replace original install.wim with install.wim taken from 1903 ISO. --> Now it is updating 17763.507 -> 18362.30.

    I see this so that this issue is in installer and this can't be fixed with CU's or using DISM to inject any new CU inside install.wim.

    MS need to fix MCT so that fixed installer is included to created ISO.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-06-02T04:16:07+00:00

    I continue testing from where I left yesterday.  It's not just setup.exe that cause this issue.

    I copy setup.exe from 1809 ISO and same failure with same USB as used before.

    Next I create USB installer from 1809 ISO, but replace original install.wim with install.wim taken from 1903 ISO. --> Now it is updating 17763.507 -> 18362.30.

    I see this so that this issue is in installer and this can't be fixed with CU's or using DISM to inject any new CU inside install.wim.

    MS need to fix MCT so that fixed installer is included to created ISO.

    Sounds good. I hope MS releases the proper fix soon.

    Was this answer helpful?

    0 comments