Microsoft Finally Fixes Windows 10 Version 1903 Blocking Issue

Posted on July 13, 2019 by Paul Thurrott in Windows 10 with 17 Comments

Microsoft has quietly fixed three major issues with Windows 10 version 1903, one of which was preventing users from upgrading to this version.

Despite its promises of increased transparency, the firm has not announced or discussed these important fixes via its corporate blogs. Instead, it has silently updated a Known Issues page on Microsoft Docs.

You’ve probably heard about at least one of these issues: Infamously, Windows 10 would not upgrade to version 1903 if the user had a USB storage device or memory card plugged-in to their PC. This has been a known 1903 blocker since mid-May, but it was quietly fixed two days ago, on May 11.

Two other major issues with Windows 10 version 1903 were quietly fixed this week as well. One regards audio loss with Dolby Atmos headphones or Dolby Atmos home theater, and the other is a major flaw in Event Viewer that made the app unusable.

Microsoft is investigating three more known issues in Windows 10 version 1903 related to Windows Sandbox (a new virtualization feature in this release), Remote Desktop, and display brightness. And users have reported a fourth issue related to the dGPU on Surface Book 2, which Microsoft has “acknowledged.”

Presumably, Windows 10 version 1903 will be “perfect” once these issues are all fixed.

It’s unfortunate that Microsoft didn’t think to communicate these fixes. But thanks to Neowin for the tip.

Join the discussion!

BECOME A THURROTT MEMBER:

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

Register
Comments (17)

17 responses to “Microsoft Finally Fixes Windows 10 Version 1903 Blocking Issue”

  1. Avatar

    gardner

    The end of the third paragraph you say “two days ago on May 11”. I think you mean July 11.

  2. Avatar

    waethorn

    Did they fix the BSOD issue when you remove Windows Fax & Scan from 32-bit installs?

  3. Avatar

    mrlinux11

    I have a Lenovo desktop with Phantom USB drives and Microsoft Update said my system was ready to install 1903, but it failed to install. I disabled USB Ports and tried it again and it worked, so I think they still have some work to do on USB install issue.

    • Avatar

      epguy40

      In reply to mrlinux11:


      I did not encounter the usb install problem when installing/upgrading to 1903 using newly refreshed 1903 ISO install media. that's why I never install feature updates thru microsoft update or windows update and ALWAYS create install media and upgrade from that instead.

  4. Avatar

    IanYates82

    What's odd is that I thought they claimed they'd fixed the external drive blocking issue a while back. Wasn't that said each week for the past few weeks on Windows Weekly? Leo's brought it up a few times.

  5. Avatar

    Cristian Botezan

    The update blocks even without any external storage device or mapped network drive.

    Hopefully, they fix it before the next big update :)

  6. Avatar

    simont

    And apparently Microsoft have now added a block for the SB2, something to do the Nvidia GPU. You would think Microsoft would do extensive testing on their own devices first.

  7. Avatar

    blackcomb

    They're still trying to make this twice a year update happen, huh? LTSC for life. Security patches only.

  8. Avatar

    crconrad

    From the article: “This has been a known 1903 blocker since mid-May, but it was quietly fixed two days ago, on May 11.”


    You mean on July 11?

  9. Avatar

    gpmccartney

    My update to 1903 was held up by mapped network drives. Windows update said my computer wasn't ready for 1903 but would be soon. I disconnected my network drives thinking they may have the same issue as USB drives and all of a sudden 1903 was available.

  10. Avatar

    jimchamplin

    They still haven’t fixed a graphical error that happens on all UWP apps. The top pixel border of the window is a darker color stroke than the sides and bottom borders.


    It’s a tiny thing, but it’s like absurd 80s contract riders. If they can’t be assed with taking the brown M&Ms out, did they read the part about electrical requirements for the music equipment?

  11. Avatar

    wordz42

    "quietly fixed two days ago, on May 11." From the context, assume that should be July 11?

  12. Avatar

    AnOldAmigaUser

    This would explain why all of my computers were "cleared" for 1903 this week, despite external drives and SD cards. After testing on a sacrificial machine, I have started the upgrade process.

    The only issue I have run into is with remote desktop to devices with very old Intel display drivers: they would display only a black screen when used remotely, which is how I use them, since one is for testing fast ring releases and the other is loaded up with disk to store backups from the other computers. The fix, should someone else need it, is to hook up a monitor, keyboard and mouse; then go to Device Manager, and uninstall the Display driver without checking the box to delete it.

  13. Avatar

    epguy40

    hi Paul Thurott.


    you may want to read these new articles from ZDNet that got published this Tuesday July 16


    www.zdnet.com/article/microsoft-is-starting-to-auto-update-windows-10-home-pro-users-on-1803-or-older-to-1903/


    www.zdnet.com/article/windows-10-has-microsoft-cleaned-up-its-update-mess/


    the one recently written by Ed Bott is especially good and questions Microsoft whether or not they "cleaned up their update mess."

Leave a Reply