Microsoft Finalizes Windows 10 Version 20H2

Microsoft announced today that it has finalized the development of Windows 10 version 20H2 and will release it in October if all goes well. Current Windows 10 users will upgrade to this version by installing the Windows 10 October 2020 Update, the firm says.

“Today, we are releasing [Windows 10 Insider Preview] build 19042.508 (KB4571756) to Windows Insiders in the Release Preview Channel,” the latest Windows Insider blog post reads. “We believe that Build 19042.508 is the final build and still plan on continuing to improve the overall experience of [Windows 10 Version 20H2] on customers’ PCs as part of our normal servicing cadence.”

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Microsoft’s “servicing cadence”—seriously—has been anything but normal for at least the past two years. But the current schedule, which matches that of last year, is that the October 2020 Update will be delivered as a small quality update if you already have Windows 10 version 2004. Otherwise, you’ll get the full feature update treatment.

For those that want the final bits today, Microsoft notes that Windows 10 Version 20H2 will be offered to Insiders in the Release Preview Channel via its so-called “seeker” experience in Windows Update at first. This simply means that you’ll have to check for updates and then choose to install it. “Once an Insider updates their PC [with] the October 2020 Update [to Windows 10 version 20H2], they will continue to automatically receive new servicing updates through Windows Update (like the [normal] monthly update process),” the firm adds.

Finally, there’s also one known issue: Those who use Windows Subsystem for Linux (WSL) will see an “Element not found” error when they try to start WSL. A fix will be provided in the next Windows 10 version 20H2 servicing release “shortly,” Microsoft says.

Share post

Please check our Community Guidelines before commenting

Conversation 21 comments

  • rbgaynor

    18 September, 2020 - 4:21 pm

    <p>“<span style="color: rgb(0, 0, 0);">will release it in October if all goes well</span>”</p><p><br></p><p>So 1Q 2021?</p>

    • kb923689

      19 September, 2020 - 8:05 am

      <blockquote><em><a href="#576587">In reply to rbgaynor:</a></em></blockquote><p>Just quit this joke of OS and install LTSC.</p>

      • luis3007

        19 September, 2020 - 1:46 pm

        <blockquote><em><a href="#576777">In reply to kb923689:</a></em></blockquote><p>Very few normal people can obtain that version</p>

  • anderb

    Premium Member
    18 September, 2020 - 4:47 pm

    <p>"Here's 20H2. Oh yeah, we broke the main thing we added in 20H1. Please download it."</p>

  • pesos

    Premium Member
    18 September, 2020 - 4:59 pm

    <p>Been running it for months on both x64 and arm. Solid build. We have a couple hundred workstations deployed in production on it as well.</p>

  • MutualCore

    18 September, 2020 - 4:59 pm

    <p>So expect it come out in 4Q 2099.</p>

  • harris0n

    18 September, 2020 - 5:31 pm

    <p>When should I exit the beta channel to avoid getting the next release?</p>

    • mog0

      19 September, 2020 - 4:39 am

      <blockquote><em><a href="#576616">In reply to harris0n:</a></em></blockquote><p>There's an option in the insider settings to do this automatically. Select this and it will exit the program at the next release.</p>

  • djross95

    Premium Member
    18 September, 2020 - 6:20 pm

    <p>I'm a RP Insider and so I searched for and downloaded the update. I was called away to help with some packing my wife was doing just as the download started. I returned to my PC (a Surface Pro 4) about 45 min later and the install was complete and the computer rebooted. Not a single message, I had to check and see that it was, in fact, installed. It was. Wow!! </p>

  • jimchamplin

    Premium Member
    18 September, 2020 - 6:23 pm

    <p>If all goes well. Well? WSL2 is already MIA…</p>

  • locus123

    19 September, 2020 - 12:20 am

    <p>I wonder if they'll have fixed the Conexant blocker on the May update by then…</p>

    • sephdk

      19 September, 2020 - 12:47 pm

      <blockquote><em><a href="#576718">In reply to locus123:</a></em></blockquote><p>Hopefully they have…</p>

  • madthinus

    Premium Member
    19 September, 2020 - 3:15 am

    <p>They keep on breaking WSL. If it is a big feature, why is this not tested better?</p>

    • Stokkolm

      19 September, 2020 - 5:04 am

      <blockquote><a href="#576748"><em>In reply to madthinus:</em></a></blockquote><p>Isn't that what they're doing right now? It's not a GA build yet.</p>

      • madthinus

        Premium Member
        19 September, 2020 - 7:06 am

        <blockquote><em><a href="#576756">In reply to Stokkolm:</a></em></blockquote><p>It is their final build they are planning to rollout, with a fix planned for later. </p>

  • sevenacids

    19 September, 2020 - 9:10 am

    <p>I'm on 20H2 .508 for about two weeks now on multiple devices (I manually installed the enablement package without Edge about two months ago) and I don't have the WSL bug. What's bothering me more is that they can't fix the defrag-issue that's in there for months, spanning multiple releases already.</p><p><br></p><p>Apart from that, are there any features (except for the new Start menu colorization and the forced-installed new Edge) at all? If not, basically everyone on 20H1 that installed cumulative update .508 is on the same codebase anyways (for the most part). This whole release is nothing but another kind of fake upgrade. I hope they stop doing this non-sense in 2021 (I don't think they will) because there is so little in there, it's not worth it.</p>

    • epguy40

      22 September, 2020 - 11:25 am

      <blockquote><em><a href="#576781">In reply to sevenacids:</a></em></blockquote><p><br></p><p>the "defrag issue" has already been fixed since .487/.488 (KB4571744), sevenacids </p><p>you haven't been paying attention to this:</p><p></p>

  • SvenJ

    Premium Member
    21 September, 2020 - 12:59 pm

    <p>I have a Surface. I imagine I won't be seeing this till next year.</p>

  • navarac

    23 September, 2020 - 3:05 am

    <p>Well, that finalised build (19042.508) lasted a long time – 4 days, then 19042.541 – with TWO PAGES of fixes! So 508 was really ready? MS have got to be kidding us all.</p>

    • Paul Thurrott

      Premium Member
      23 September, 2020 - 8:53 am

      Is any Windows ever really ready? 🙂

      • navarac

        24 September, 2020 - 7:04 am

        <blockquote><em><a href="#578138">In reply to paul-thurrott:</a></em></blockquote><p>How very true! :-)</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC