Windows 10 Version 2004 is Now Available

Posted on May 27, 2020 by Paul Thurrott in Windows 10 with 47 Comments

Thinking About the Future of UWP, Windows Store, and Windows 10 S (Premium)

Following an unprecedented—for Windows 10—testing schedule, Windows 10 version 2004 is now available via the so-called May 2020 Update.

“Beginning today, the May 2020 Update is available for customers who would like to install this latest release,” Microsoft Director John Cable announced today. “We are taking a measured and phased approach to how we offer the May Update, initially limiting availability to those devices running Windows 10 versions 1903 and 1909 who seek the update via Windows Update.”

Windows 10 version 2004 will be supported by Microsoft for 18 months starting today.

“If you’re an IT administrator, we recommend that you begin targeted deployments to validate that the apps, devices, and infrastructure used by your organization work as expected with the new release and features,” Cable continues. “Windows 10 version 2004 is available through Windows Server Update Services (WSUS), Windows Update for Business, and the Volume Licensing Service Center (VLSC) for phased deployment using Microsoft Endpoint Configuration Manager or other systems management software.”

End users wishing to check for this upgrade can navigate to Settings > Update & Security > Windows Update and click “Check for updates.” As Microsoft notes, you may not be offered the download immediately because it is “slowly throttling up this availability over the coming weeks,” or because your PC might have a known compatibility issue that will remain in place until Microsoft is confident that you will have a good update experience.

Onwards to 20H2!


Join the discussion!


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

Comments (51)

51 responses to “Windows 10 Version 2004 is Now Available”

  1. sherlockholmes

    I wonder how small 20H2 will b. 20H1 didnt have much new in it.

    • SWCetacean

      In reply to SherlockHolmes:

      Not much in terms of front-facing features, but there was a significant amount of internal work that was done. A lot of that stuff was talked about months ago though, and they weren't directly attributed to being in 20H1 at the time (e.g. all of the DirectX 12 Ultimate stuff was announced last summer and wasn't stated to be part of 20H1, but it is). Plus remember that WSL 2 is finally getting a public release in 20H1.

      As an aside, this is one of the areas where I think the Linux community is better. Linux people love talking about small plumbing improvements to the kernel and filesystems and other OS internals. And the result of this fascination with small internal improvements here and there means that over time Linux becomes an incredibly robust kernel. This isn't to say that Microsoft doesn't do that internally (I'm sure the kernel/core team is also super-focused on small kernel improvements too), and NT is not as bad of a kernel as Linux lovers would believe, but the wider community in Windows doesn't really have that passion for small technical improvements.

    • IanYates82

      In reply to SherlockHolmes:

      I finally got 1909 on my laptop after being stuck on 1803 for ages.

      Tried Windows sandbox finally. Neat idea. Run winver in it and, despite outer windows being 1909, the inner sandbox copy says 1903. I was under the impression that a lot of the windows system files are virtually shared with the sandbox copy so I found it intriguing that the versions differed like that.

      Another reflection of 1909 not really being that different from 1903 I suppose.

      20H2 may follow suit in large part. Hoping for some of that cool WSL2 stuff they announced to maybe flow through though

  2. jmarco

    I found it 7:18 pm CST in Windows Update settings as Download Available. Downloading took only 4 min with Spectrum 1 gigabyte wifi and another 24 min to install completely. It is also available as ISO at Window 10 install website.

  3. red.radar

    Fairly flawless fresh install for me. I thought it was odd that old edge was the native browser... I had to use old edge to get to new edge. However once I installed new edge old edge just disappeared....

    this comment is hard to follow because Microsoft kept the edge brand ...

  4. scottkuhl

    Even the Media Creation Tool won't update the Surface Pro X.

  5. wright_is

    Worked fine for me. Although, like red.radar, it still had old-Edge after the update. I thought it would update Edge at the same time...

  6. Sihaz

    My surface Pro 7 reports that this update is not available when I try to update using the USB installer I made with the media creation tool. Anyone else seeing this?

  7. ghostrider

    It always staggers me that people rush to get the latest update on launch day. With Microsoft's track record, delaying it for at least 3 months is probably a good idea. What I can also probably assume is that other than winver now reporting a newer build, most probably won't notice any difference whatsoever.

  8. brettscoast

    Thanks for the heads up Paul

  9. simont

    And as usual, none of my Surface devices can see the update via Windows Update yet.

  10. gregorylbrannon

    I was able to successfully install it last night on my Gen 1 SurfaceBook.

  11. john

    As of 10:00 AM on May 28th the Windows Upgrade Assistant will update to Version 2004. You will first see Version 1909 but after you download the Upgrade Assistant it will offer Version 2004. I'm in the middle of the update process right now and will update this post with the result.


    I'm running a Surface Laptop 3 Business Edition. The install reported my PC isn't supported at this time. Wow, Microsoft doesn't support their own??

  12. rlcronin

    For what its worth, I updated 3 machines to 2004 yesterday and today they have all been reverted to 1909. I use ZeroTier to remotely access my machines. ZeroTier adds a virtual network adapter that you then connect to your ZeroTier network-in-the-cloud on each of your machines. They are then all on the same network and you can just use Remote Desktop to get to them. Well, after the 2004 update, the ZeroTier network adapter got reset to being an unidentified public network. I fixed that by uninstalling and reinstalling the ZeroTier adapter and then everything would work, but if I rebooted the machine at all the problem came right back. It's a bit of a show stopper for me since I depend on being able to access multiple machines at various locations around the country.

  13. bogdan

    No it is not.

    • This comment was verified by Jack "The ripper", so it is true, and I can prove it.
  14. HowGozit

    I am not sure i am game to install this one - at lest on my Surface Go. I ran the Windows Insider - preview ring last month - upgraded 3 times then reverted - the last time I got out of the preview ring.

    Reason - the Surface Go is by no means fast - but after 2004 installed, it was to all intents an purposes - stopped. 100% CPU utilisation for over 20 minutes - 95% on system interupts.

    Drop back to 1909 - and it was fine. 1 minute of startup sluggishness (not stopped, but a little slow - this is usual), then normal - running 3-4 programs simultaneously fine.

    Anyone else have Surface Go issues - If it had been one of the i7 machines I may not have noticed - but the Surface Go ....

  15. simard57

    Not seeing it for HP Spectre 360

  16. pesos

    We have a few hundred 20H1 machines already deployed. It is a solid release and the IPUs from earlier releases are incredibly fast. Now just hoping MS makes another exception and extends it from 18mo to 30!

  17. remc86007

    I know it doesn't really matter; but I find it annoying that my Surface Laptop 3 isn't in the first wave of the rollout. You'd think they would have compatibility with their own device sorted out before launch. Perhaps they don't want the risk that there is a breaking bug and then they have to deal with it as the OEM as OS maker?

    • Thretosix

      In reply to remc86007:

      You can force the upgrade from the Microsoft download site. From the same location you can download the media creation tool to download the ISO to make copies to upgrade several PCs at the same time.

    • angusmatheson

      In reply to remc86007:

      I also find it weird that my HP desktop is getting it before my surface pro 7. Does Microsoft want other company’s customers to be their Guinea pigs. If they had faith in it I would think they would give it to surface. And the limited number of configurations seems to make it an idea first run.

    • Paul Thurrott

      It does matter. It makes zero sense that Microsoft's own devices aren't fully compatible and ready to upgrade on day one. Zero.
      • remc86007

        In reply to paul-thurrott:

        I finally got the update tool to work, it said I was compatible, spent 30 minutes downloading the update and then I get this message:  "This PC can't upgrade to Windows 10. Your PC isn't supported yet on this version of Windows 10. No action is needed. Windows Update will offer this version of Windows 10 automatically once the issue has been resolved."

        This is a Surface Laptop 3 15inch with the Ryzen 5. I ran a build of 20H1 back in December on it with no problems...yet now, five months of testing later, on launch day, it isn't compatible.

    • Paul Thurrott

      And even Google gets this right. Imagine if Android 11 shipped and some set of third party phones got it, but none of Google's. It's inconceivable.
      • compuser

        In reply to paul-thurrott:

        It happens. A coworker's Pixel 3 still has Android 9. I think it's up to the carrier to push Android updates, isn't it? (My wifes LG Stylo 4 and my Moto G7 obviously aren't Google devices, but they're both still running Android 9, and Xfinity Mobile says that's the latest Android version.)

    • epguy40

      In reply to remc86007:

      Tero Alhonen recently got the May 2020 update on his Surface Pro 4 device

      not sure about other Surface Pro devices, fwa ha ha :)

  18. MacLiam

    When I installed the Release Preview version of 2004 on my main computer about a month ago, it froze intermittently or got stuck in processes that it couldn't complete. Boots took minutes rather than seconds, so I rolled back to 1909 and blocked new updates for as long as I could. I will install the release version at some point, but will roll back again if there are problems. My event log showed a bunch of DCOM errors.

    A less-used computer got the 2004 update without problems. At the time I didn't bother to try to figure out the different experiences.

    • IanYates82

      In reply to MacLiam:

      Every event viewer I've examined in the past couple of years - server or workstation - shows mystery dcom errors like clockwork unfortunately. They need to get better at including more context for logged errors so we could perhaps see what triggered the dcom component activation and then we can know if it's even worth investigating further or if we can dismiss it as background noise.

  19. JerryH

    And - nope - it is not there in Windows Update for Business. Not yet anyway. I just checked as I went to setup a deployment of 2004. 1803, 1809, 1903, and 1909 are there but no 2004. Maybe tomorrow?

  20. SvenJ

    Not available to me thru Windows Update. But then I'm using a non-mainstream device, a Surface Pro 7.

  21. mattbg

    Just installed with no issues on my self-assembled desktop, but it's not available on my Thinkpad X1 Carbon.

  22. jslobello

    Windows update didn't find anything for my Virtual Machine. In the past I had luck using the "Windows 10 Upgrade Assistant" to bypass WU. No such luck this time. The freshly downloaded upgrade assistant says "No update found'. I went to and found the ISO there, which is downloading now.

  23. luis3007

    Neither WU or the exe from the update to May 2020 update page are working for me

  24. jmeiii75

    Still not available on my XPS 13. Been seeking like crazy.

Leave a Reply