Skip to main content

Microsoft announces Windows 10 version 20H2 coming later this year

Windows Update
Windows Update (Image credit: Windows Central)

What you need to know

  • Windows 10 version 20H2 build 19042.330 is now in testing.
  • It'll be launching in the second half of 2020.
  • Will be the first version of Windows to have the new Edge preinstalled.

Microsoft has today announced that the next version of Windows 10, known officially as version 20H2, will be launching later this year and is now in testing in the Windows Insider Beta Channel. The 20H2 release will be the first to have the new Chromium-based Microsoft Edge pre-installed in the OS image.

Just like Windows 10 version 1909, the 20H2 release will be delivered as a cumulative update that sits on top of Windows 10 version 2004. This means the update won't be a big download and will only take a few minutes to install. Microsoft hasn't yet detailed all of the new features or changes coming in the 20H2 release, but we're not expecting anything major as the focus is on small improvements to existing features.

20H2 Update

Source: Windows Central (Image credit: Source: Windows Central)

Microsoft has also confirmed that it's moving away from the year-month version format starting with this release. Previously, versions of Windows 10 were formatted by the month and year they were finalized in. For example, the most recent version of Windows 10 was numbered version 2004 as it was completed in April 2020. Starting with 20H2, Microsoft is keeping the year, but replacing the month with a more generic H1 or H2 indicator.

H1 is the first update in any given year, and H2 is the second update. This is the format Windows Insiders have been using as "codenames" for upcoming versions of Windows 10. Now, these codenames are the official version numbers going forward. Microsoft says it will continue to use friendly names (like September 2020 Update, for example) when communicating updates to consumers.

What are your thoughts on the upcoming Windows 10 update? Let us know in the comments.

Zac Bowden
Senior Editor

Zac Bowden is a Senior Editor at Windows Central. Bringing you exclusive coverage into the world of Windows 10 on PCs, tablets, phones, and more. Also an avid collector of rare Microsoft prototype devices! Keep in touch on Twitter: @zacbowden.

15 Comments
  • Some users had left Windows 10 after installing '2004' update.
  • Why change the version naming? Makes no sense. At least by 20H2 MS will have hopefully fixed all the bugs reported for 20H1
  • Version name hasn't changed as we don't really know when it will be finalize yet
    so just referring it to it as 20H2 makes sense for now.
    Definitely bugs will be squashed in 2004/19041. lots of cumulative updates to go.
  • They won't. It'll stay 20H2. They won't change to 2009, or whatever month they finalize it.
  • Probably because the old naming scheme was confusing. "2004" looks like a year, rather than YearMonth combo. Also too much is made of hitting that exact month target date. The new naming scheme has greater flexibility built-in.
  • Naming something April01 doesn't mean it has to be released to April fools.
    Any reasonable person knows its a revision to a version.
    Autodesk use a future date one year ahead like 2021 for this year release. No one is confused of anything as they are consistent year after year.
  • You're right, everyone out there is reasonable and tech-savvy. What was I thinking?
  • Nothing is changing. "Creator's Update" is a marketing name. You can name any update at your will. You could call the 1903 update the "Timeline Update" nobody really cares. The 20H2, 20H1 scheme is an Azure Service Pack naming. It is a planned service pack to incorporate fixes released all along. There is nothing sepcial about this either. You can apply the naming scheme to previous Windows 10 updates even when it wasn't part of the Azure release cycle. 1909, 2004, 2009 is the build number. No need to name it anything, it will always stay the build number for Windows releases. Whatever name marketing people will refer to a Windows 10 release by, the semi-annual release will be refered to as YYHX as long as Windows 10 stays under the Azure release cycle and Azure sticks to this technical naming. The build number being hit by the time comes will be 1909, 2004, 2009. Even if marketing people refer to something as the Fall Creator's update, landscape management will refer to it as the 17H2 version, while the sole developer sitting at the end of the pipeline will know that it is part of the 1709 release branch of Windows, and is really working on build 1709.17655.600. So there are builds, there are releases and there are names. You refer to them by whatever depending on what granurality of the lifecycle you are refering to and who you are. The problem is that at Microsoft nobody knows rats about communication and is subpar professional to know which way they are required to refer to something. Then many reporters are unable to handle the information they hear in its own place.
  • “Just like Windows 10 version 1909, the 20H2 release will be delivered as a cumulative update that sits on top of Windows 10 version 2004”. Really? When did Microsoft said this? I completely missed it.
  • They did say that today. My bad.
  • Well one of the features coming in this update is that the Chromium version of Edge will be install as the default browser.
  • This is what we want. All clean install will have the new Edge by default.
  • I just needed to install the new Edge manually a couple of minutes ago. I just could not understand why my PC is not getting it while all my laptops have deployed the KB for it automatically.
  • Well this is an early beta build which doesn't have all the features yet but the final release will have the new version of Edge by default
  • Another two weeks and 2004 will be out in 20H2. On many Surface devices anyway.