Microsoft Fixes USB Bug Preventing Users From Updating to Windows 10 Version 1903

Posted on May 29, 2019 by Mehedi Hassan in Windows, Windows 10 with 12 Comments

Microsoft is today rolling out a new update to the Windows 10 May 2019 Update, or version 1903. The company is releasing KB4497935, which comes with a number of fixes for the update.

The update bumps the build number up to 18362.145. There are a bunch of fixes in the update, but the most notable fix here is a USB-related bug. Microsoft stated earlier that some users won’t be able to upgrade to Windows 10 Version 1903 because of an issue that results in an external USB device or SD memory card to be reassigned to an incorrect drive during installation. “To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved,” the company said.

KB4497935, which is rolling out today, fixes that problem, meaning users should be able to upgrade their device to Windows 10 Version 1903 if they were previously affected by the bug. I believe this might be the reason why I was unable to upgrade to version 1903 earlier in the week, so I am going to try installing it again and see if that fixes anything.

Anyway, here’s the full changelog for the update:

  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
  • Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.
  • Addresses an issue that my turn off Night light mode during display mode changes.
  • Addresses an issue that may distort the rendering of a full-screen game when the Microsoft Game bar is visible on top of the game.
  • Addresses an issue that prevents the removal of Bluetooth® peripheral devices from some systems with specific Bluetooth radios.
  • Addresses an issue that may cause event 7600 in the Domain Name System (DNS) server event log to contain an unreadable server name.
  • Addresses an issue in which the dots per inch (DPI) of the guest does not match the host.
  • 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.
  • Addresses an issue in which a File Share Witness does not remove Server Message Block (SMB) handles, which causes a server to eventually stop accepting SMB connections.
  • Addresses an issue that prevents an application protocol URL from being opened when hosted on an intranet page.
  • Addresses an issue with BranchCache when it is in distributed cache mode. BranchCache may use more disk space than assigned for the republication cache. To fully address the issue, devices that have exceeded the disk space assignments should empty BranchCache using the netsh branchcache flush command.
  • Addresses an issue that may prevent some Direct3D applications and games from entering full-screen mode if the display’s orientation has been changed from the default.
  • Addresses an issue with creating a Windows catalog file on an x64 system using Windows System Image Manager. For more information, see What’s new in ADK kits and tools.
  • Addresses an issue that causes a delay when loading many unsigned Domain Name System (DNS) zones related to the Domain Name System Security Extensions (DNSSEC) feature.

Tagged with , ,

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (12)

12 responses to “Microsoft Fixes USB Bug Preventing Users From Updating to Windows 10 Version 1903”

  1. SvenJ

    Always amazes me, some of the issues that slip through all the way 'RTM" (Release to Masses). I venture to guess a high percentage of Surface devices, Pros, Gos, have permanent SD cards stuck in them. This is MS's own product and pretty popular on campus. You'd think Surface would be among the first to get upgraded. I had to pop my SD out of my GO to get 1905, oops, 1903.

    • IanYates82

      In reply to SvenJ:

      I agree.

      I wonder though if it's not so much the surfaces to worry about since most probably have that card as drive d

      It's the desktops with a DVD drive on d and then a second hdd on e. Swapping them by accident can break a lot of stuff that an end user, who's never heard of diskmgmt.msc, would have no clue how to fix

      Personally I set any optical drive to drive r

      I intensely dislike logging on to a virtual sever for maintenance, where it's only ever had a single ISO connected (to install windows initially) and it still has drive d set to the permanently empty DVD drive and then the server admin has just left the remaining drive letters get allocated willy nilly.... Take some care! ?

  2. Lordbaal


    But at least they won't let you update this time.

  3. Tony Barrett

    What MS meant to say was 'To prevent a repeat of the 18xx feature update fiasco's, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10'. That sounds more like it.

    Still, if you're running on AMD Ryzen, I'd steer clear of 1905 until MS issue the fix that either prevents install, or borks the machine entirely. Go Microsoft!

  4. waethorn

    Um....shouldn't the patch be for EARLIER versions of Windows before 1903 in order to fix the inability to upgrade to 1903?

    Also, they haven't updated the ISO's on the software download page.

    • fraXis

      In reply to Waethorn:

      Your would think so (in regards to the earlier versions being patched to fix the inability to upgrade to 1903).

      And yes, the MSDN version of 1903 has not been updated since it was first posted on 4-4-19. The older versions (1809, etc) were updated on 5-27-19. Not sure what is taking them so long to post a new ISO of 1903.

      • SvenJ

        In reply to fraXis: No, it is in the upgrade code, not a problem with the earlier version you are upgrading from. It starts the upgrade, realizes it can't continue, reverts, and gives you a clear have a removable drive. Presumably now, that will not be an issue in the current upgrade files.

  5. waethorn

    Still doesn't fix the BSOD caused by removing Windows Fax & Scan on 32-bit.

  6. Patrick Wingert

    I am glad six of my machines still run 1709 and the othe 4 run 1803. This idea of deferring update for 364 days is working really well. If things go well I might qualify for the new Windows OS core by the time my deferrals are scheduled to expire in March 2023?????

  7. techguy33

    "Microsoft releases new cumulative update for Windows 10 May 2019 Update that fixes an issue preventing users from installing the May 2019 update"

    Is it just me or is there a chicken and egg problem here?

Leave a Reply