Microsoft Merges Fast Ring and Skip Ahead for Insiders, Releases New Build

Microsoft is making some major changes to the Windows Insider program today. Now that the Windows 10 May 2018 Update is almost ready for the public, it’s focusing on the next major update for Windows 10. And no, that’s not Windows 10 19H2. It’s Windows 10 20H1.

As you may remember, Microsoft already announced the company is pushing Insiders forward to Windows 10 20H1, which is set to arrive for the public sometime in early 2020. As for 19H2, the company still hasn’t stated how those builds will be released and tested with Insiders, but I’m guessing it will ship those builds in the Slow Ring instead.

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.

And so, yes, 20H1 is here for everyone now. Microsoft just merged both the Fast Ring and Skip Ahead, so if you were on Skip Ahead before, you will now be getting the same build as those on the Fast Ring.

The new build today is 18875, and it’s shipping for everyone on Skip Ahead and Fast Ring. In terms of features, there are some input-related improvements, though nothing too major apart from that.

So if you haven’t switched to the Release Preview program, you may want to try to do that now — else your device will be getting 20H1 builds which aren’t stable.

Going forward, it will be interesting to see how Microsoft deals with the 20H1/19H2 overlap. So far, it has been one confusing mess. Like usual, Microsoft is failing to communicate its intentions, and so everyone is a bit unsure about everything. Hopefully, though, most of these confusions will be addressed at Build 2019, where Microsoft is expected to talk about the next major update for Windows 10.

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 13 comments

  • NoFlames

    10 April, 2019 - 2:11 pm

    <p>I selected the option to exit the insider program at the next major build. Just now I went to check to make sure my insider settings were correct as I don't want to skip ahead. I was presented with an option to reset for changes to take affect. I restarted and then when I checked I was off the insider program. So the switch to jump to release did it's job.</p><p><br></p><p>BTW, I'm now using the edgium dev and canary builds, and they are an excellent start. I switched it to be my primary browser.</p><p><br></p>

  • jblank46

    10 April, 2019 - 10:09 pm

    <p>My suspicion is that there will be no 19h2, or at least not in the way we know it. Either Windows is moving to a once a year cadence similarly to macOS or the h2 builds become like a minor update and h1s are major updates. If either were the case, it would have to be announced at build next month.</p>

  • Tony Barrett

    11 April, 2019 - 5:16 am

    <p>FFS Microsoft – a single annual feature update is more than enough. If you have to go with an H2 build, just make it a 'fix up' release with security patches as usual during the year. Going by the general poor quality of releases recently, it's obvious two major updates a year are too much for MS to deal with, and quality is suffering. If you're really listening to your customers – you'd act.</p>

    • Luis Emilio Padilla

      14 April, 2019 - 2:46 pm

      <blockquote><em><a href="#419874">In reply to ghostrider:</a></em></blockquote><p>Yes, that would be the best. Use the H2 as a fix for heavy bugs and QoL from the H1, and keep H1 as the OS with new features and heavy changes. The monthly updates can keep going for light bugs and patches.</p>

  • fbman

    11 April, 2019 - 5:54 am

    <p>I can’t remember when last I played with an insider build. I used run it on a virtual machine as I only want public version on my main work machine (currently 1809). </p><p><br></p><p>I just dont don’t the time to fire up the Vm to test the builds. I think that VM may still have 1709 or 1803 builds. I just follow what is happening on this site</p>

    • Jacob Klein

      11 April, 2019 - 7:46 am

      <blockquote><em><a href="#419877">In reply to fbman:</a></em></blockquote><p>I set up all 4 of my PCs to have 3 OS installs — Release, Slow, Fast. Then I choose which one I want to log into. And I run Fast as a daily driver, on silicon, generally without too much issue.</p>

      • CompUser

        11 April, 2019 - 4:35 pm

        <blockquote><em><a href="#419882">In reply to Jacob Klein:</a></em></blockquote><p>I do the same, except only dual boot; release and skip ahead, and I use NeoSmart's iReboot to select which one to boot into., or to reboot directly from one to the other. Works pretty well for me as well.</p>

  • Jacob Klein

    11 April, 2019 - 8:00 am

    <p>The blog post… now lists the 0xca00a000 error as a Known Issue, and recommends people UpVote a Feedback Hub item.</p><p><br></p><p>Also, if you are getting 0x80242016, that is the real error that the install first crashes with. Apparently it is:</p><p>WU_E_UH_POSTREBOOTUNEXPECTEDSTATE</p><p>per:</p><p>Google search for 0x80242016 to find the "Common Windows 7 update error codes and how to fix them" page.</p><p>Fast Ring is FUN! :)</p>

  • Dan1986ist

    Premium Member
    11 April, 2019 - 9:22 am

    <p>Most likely, there will be a fall version of Windows 10, this calender year, but it will be a minor version upgrade like Paul and MJF have talked about on Windows Weekly. Yes, there are those who want a single version of Windows 10 released per year, but can't always get what you want. </p>

  • littlejohnjt

    Premium Member
    11 April, 2019 - 10:00 am

    <p>Has anyone had issues with updating to 18875? Getting error code 0xca00a00.</p>

    • bncz1

      Premium Member
      11 April, 2019 - 10:25 am

      <blockquote><em><a href="#419894">In reply to littlejohnjt:</a></em></blockquote><p>My first attempt to install 18875 failed with error <span style="background-color: rgb(245, 245, 245);">0x80242016 and then fell back to my orginial build 18362.53</span></p>

    • jshoq

      Premium Member
      11 April, 2019 - 4:24 pm

      <blockquote><em><a href="#419894">In reply to littlejohnjt:</a></em></blockquote><p>I also have been getting the 0xca00a000 error on installs of 3 different systems.</p>

  • danielmunitz

    12 April, 2019 - 2:50 am

    <p>"<span style="color: rgb(0, 0, 0);">Now that the Windows 10 May </span><em style="color: rgb(0, 0, 0);">2018</em><span style="color: rgb(0, 0, 0);"> Update…" shouldn't read 2019?</span></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 © 2024 Thurrott LLC