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.
Win 10 1903 May 29, 2019—KB4497935 (OS Build 18362.145) still fails the update from a USB stick.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
76 answers
Sort by: Most helpful
-
Anonymous
2019-06-01T19:36:01+00:00 -
Anonymous
2019-06-01T19:30:01+00:00 "Uh-oh. Now I see you were using Installation media that says it is ...145 at a Command Prompt & the Setup.exe is ...1. I was thinking that should work. Not sure what to think now."
Hi PCR,
The block that checks for the USB is in the Windows installer, if they don't update the setup.exe in the installation media it will still fail from the USB even if the Installation wim is at 18362.145.
Anyway, to workaround the bug I just did the upgrade on all my PC just using the ISO file on a local disk instead of using the USB stick.
Just open the windows.iso file with file explorer and click the setup from there, make sure you don't have any USB storage plugged in and it will work fine.
All my machines were upgraded from 1809 build 17763.529 to 1903 build 18362.30 and then windows update brought them up to 18362.145.
Now we just have to wait for Microsoft to release a new installer for 1903 without the damn USB block.
Would be much easier if MS specified what level is available to download with the media creation tool, it is a waste of time to download just to find out that it is still the old version.
-
Anonymous
2019-06-01T08:33:38+00:00 I saw your prior post & just returned from two reboots.
(1) My 1903 USB shows **10.0.18362.**30 at the Command Prompt & ...1 in Setup.exe.
(2) My 1809 USB shows 10.0.17763.107 at Command Prompt & ...1 in Setup.exe**.**
I guess that's what they install, because no greater OS Build was around when they were made. If it's a clean install & one clicked to have it get updates, it would read them in during the install. But an over-install wouldn't do that (I don't think).
Yep, I think they have to fix the installer (Setup.exe). But I'm wondering now whether it would still have ...1 as its version. Then we'd have to go to the Command Prompt of the Installation USB to know what OS Build it really is. It looks like DISM can do it too...
But I'm not sure where this really gets us.
Edit: Uh-oh. Now I see you were using Installation media that says it is ...145 at a Command Prompt & the Setup.exe is ...1. I was thinking that should work. Not sure what to think now.
-
Anonymous
2019-06-01T07:06:31+00:00 Hi PCR,
I can see where the confusion is.
I checked the build level on the command prompt after booting from the installation media and it shows 18362.145, but the level of the setup.exe is still 18362.1, that means they did not update that part and they still check for the USB devices to block the update.
I guess another separate fix is needed for the windows installer.
Perhaps Kb4497935 did not include a new installer setup.exe ?
Microsoft Windows [Version 10.0.18362.145]
(c) 2019 Microsoft Corporation. All rights reserved.
X:\Sources>
-
Anonymous
2019-06-01T06:44:22+00:00 Hi fg,
I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.
Media creation tool isn't updated immediately. It might take a while for the fix to get it corrected in the installation media. In your case, would suggest you to copy the installation media to the hard drive and then manually update after removing the SD Card/USB Stick.
Hi Sumit,
I know the workaround, but I was trying to see if they fixed the bug.
The installation media was created from an ISO file that was obtained with UUP-dump that includes Kb4497935 and when I boot from it and go to command prompt it shows build 18362.145, which means it has the update.
I think I see what the problem is the setup.exe on the installation media was not updated accordingly, even on the 1st official release of the installation media that shows build 18362.30 in the command prompt, it still has the setup.exe at level 18362.1 dated 4/1/2019 4:54 PM , the one created at 18362.145 has the setup.exe still at level 18362.1 dated 5/22/2019 11:31 AM, that means that while the software has the latest updates, the installation setup.exe is still old even if it has a different date and time.
I hope they don't forget to update the windows installer setup.exe part when they make the official update of the installation ISO.
Thanks.
Command prompt after booting from Installation media:
Microsoft Windows [Version 10.0.18362.145]
(c) 2019 Microsoft Corporation. All rights reserved.
X:\Sources>