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: Newest
  1. Anonymous
    2019-07-10T03:12:03+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.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-07-10T03:01:20+00:00

    (1) A new OS Build came in ("START, Settings, System, About")...

    But "Shift+Restart" still shows 30, as usual. I thought this time it might be different considering the new 175 release. I made a Windows system image backup afterward, as usual.

    (2) I made both an .ISO & an Installation USB of the new 175...

    Microsoft Windows [Version 10.0.18362.239]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>DISM  /Get-WimInfo  /WimFile:E:\Sources\Install.esd  /Index:1

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Details for image : E:\Sources\Install.esd

    Index : 1

    Name : Windows 10 Home

    Description : Windows 10 Home

    Size : 14,229,531,906 bytes

    WIM Bootable : No

    Architecture : x64

    Hal : <undefined>

    Version : 10.0.18362

    ServicePack Build : 175

    ServicePack Level : 0

    Edition : Core

    Installation : Client

    ProductType : WinNT

    ProductSuite : Terminal Server

    System Root : WINDOWS

    Directories : 19610

    Files : 88906

    Created : 6/11/2019 - 9:35:39 PM

    Modified : 7/9/2019 - 10:05:52 PM

    Languages :

            en-US (Default)

    The operation completed successfully.

    C:\WINDOWS\system32>

    The .ISO got made first try. The USB took two tries this time (instead of 3). On the 2nd try, all was the same, except I deleted both $Windows.~BT & $Windows.~WS first. Those are temporary folders that appear whenever MCT is run.

    (3) Now I'll do the upgrade (over-install) & edit the result into this post. Also, I want to make a new Recovery USB drive (ask Cortana or Search).

    Edit: I ran the over-install from the 175 Installation USB media. There was no error message. It took 3 hours (one more than the .ISO on page 4 of this thread). Shift+Restart gets to a Command Prompt that shows 18362.175 - just as you said, fg2001. And I did have a chance to exit where you said. I presume other important changes may also have occurred. Of course, after it completed, the OS Build still is 18362.239 - but the installed date is changed to today's date...

    I'm very pleased with the outcome. Thanks for the heads-up on 175 - how did you know that?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-07-09T09:50:01+00:00

    My system is currently 18362.207, & that is what shows at a Command Prompt when booted to Windows.

    My upgrade 1809 > 1903 was from MediaCreationTool1903.exe when it downloaded 18362.30. Right, the Command Prompt got by Shift+Restart [same as "START, Settings, Update & Security, Recovery, Restart now (under Advanced Startup)"] shows 18362.30. That's a boot to the Recovery Partition (as opposed to the Installation media's "repair your computer").

    Looks like you are saying - if I use MediaCreationTool1903.exe to make Installation media now - it will make one that is 18362.175. Well, Pauli O verified that much. Furthermore, you say - if I use it to over-install my current system - Shift+Restart will get to a Command Prompt that shows 18362.175. I guess that does make sense. Maybe it does even more than that.

    I guess tomorrow I'll make the new media - & I'll do the upgrade-install too. Thanks.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-07-09T08:26:03+00:00

    Thanks, fg2001. I'll make it tomorrow & test it at least up to that question.

    I expect - if I use it to enter its recovery environment (repair your computer) - its Command Prompt will show 170 whether or not I do the upgrade.

    Are you saying - if I do the upgrade - the onboard recovery environment (Shift+Restart) would also show 170?

    PCR, 

    No the recovery environment cmd prompt will show 18362.30 unless you upgrade using 18362.175.

    Even if your system is up to 18362.207, the recovery environment depends on the installation media that your used for the upgrade. 

    If you upgraded with windows update, the recovery environment will show 18362.1 in the command prompt.

    If you go to windows update and click on recovery then restart..

    Then select troubleshooting and go to command prompt. You will see the level there 

    Microsoft Windows [Version 10.0.18362.207]    <-    (Running system prompt)

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>

    The 3 below are the prompts you will get on recovery depending on how you did the upgrade.

    Microsoft Windows [Version 10.0.18362.175]     <-    (Recovery system prompt)

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>

    Microsoft Windows [Version 10.0.18362.30]       <-    (Recovery system prompt)

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>

    Microsoft Windows [Version 10.0.18362.1]         <-    (Recovery system prompt)

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-07-09T08:14:00+00:00

    Thanks, fg2001. I'll make it tomorrow & test it at least up to that question.

    I expect - if I use it to enter its recovery environment (repair your computer) - its Command Prompt will show 170 whether or not I do the upgrade.

    Are you saying - if I do the upgrade - the onboard recovery environment (Shift+Restart) would also show 170?

    Was this answer helpful?

    0 comments No comments