Newsletter Archives

  • The next-next version of Windows 10, code named 20H1, known colloquially as 2003, may arrive in December 2019

    Just when you thought the pace of unnecessary changes in Windows was receding….

    Now comes word from Zac Bowden at Windows Central that the version of Win10 following 1909 (widely expected next month) will arrive in December. Of this year.

    Microsoft’s upcoming 20H1 release of Windows 10 will be the company’s first version of the OS to be finalized in December, three months earlier than usual, as a result of Windows moving under Azure and adopting the “semester” based development cycle that Azure is already using. Mary-Jo Foley was first to reveal that the Windows dev cycle was being changed up earlier this year, but here’s what this all means for Insiders.

    You should take that pronouncement with a very large heap of salt, but it sounds plausible. Bowden  frequently has scoops that reflect the current thinking at Microsoft. Notably, though, none of the other major players in the Microsoft Tea Leaf game have independently confirmed the rumor. Mary Jo hasn’t published anything on the topic in the past 24 hours. Paul Thurrot hasn’t commented.

    So either Zac broke something that’s being played very close to the chest – or he got tossed a wild herring. Time will tell.

    There’s very little of interest in 20H1, er, 2003, uh 1912, ahem Vibranium, based on my very brief look-around. Chris Hoffman at How-To Geek has a detailed look at the new features in beta versions of 20H1, all of which put me to sleep.

    Bowden’s next prognostication, though, sends chills down my spine:

    This also means that work on the next Windows 10 feature update after 20H1, known as 20H2 or “Manganese” has already started development internally, and Insiders should begin receiving 20H2 builds in the next couple of weeks. On this new development cycle, 20H2 will RTM in June 2020. This is important, as this release will play a vital role in the availability of Windows 10X on new foldable PCs expected to start shipping in fall 2020.

    So it looks like the tic-toc theory of Windows rollouts — big feature changes followed by little feature changes, as exemplified by the Win10 1903-to-1909 sequence — may turn into a tic-toc-toc. Would that it would segue into a tic-hum-hum-hum instead of burp-burp-burp.

    Change for change’s sake. To get us more aligned with Azure. Oh boy.

  • Rings within Insider Rings – where you end up, nobody knows

    Those of you in the Insider Program have a choice to make. I’m having a hard time guessing where this is all headed.

    Right now, I can confirm that if you’re in the Release Preview Ring on a completely clean copy of 1903 and check for updates, you end up on 1903 build 18362.448 with an offer to upgrade to 1909

    Looks like Slow Ring is on 1903 (build 18362.10024?), but “you’ll be updated to 20H1/2003 shortly” and you won’t be offered a chance to move to 1909. If I read the tea leaves correctly.

    Fast Ring is a big question mark. Right now, Fast is on 20H1/2003, but will it move to 20H2/2009? Or will it move to 21H1/2103?

    Skip Ahead is also a big unknown. Will it go to 20H2/2009 or 21H1/2103?

    Another way to rephrase the question… Is Microsoft going to switch over to giving us a Service Pack late in the year every year – or are we going back to the old two-versions-every-year pace?

    A related question: Could Microsoft possibly make this any more complex?

  • Windows Insiders: If you’re in the Slow ring, you’re about to get pushed to the next-next version of Win10, version 2003 (a.k.a. 20H1)

    Paul Thurrot caught this – it went right over my head.

    If you’re one of the (16 million?) folks in the Windows marketing beta… er, Windows Insider program… you should check which ring you’re on. If you’re in the Slow Ring, and are currently beta testing Win10 version 1909, you’ll be switched over to testing Win10 version 2003 (or whatever they’ll call it) “very shortly.”

    Paul nails it:

    Last night, Microsoft updated a blog post that was originally posted 11 days earlier. This marks the second time they’ve released news to this post by editing the post, and the company seems to be clueless about the fact that these updates are basically sent into a black hole: Without issuing a new post, no one will ever be alerted to the news.

    Although I subscribe to the Windows Insider Twitter account, I didn’t notice the tweet. One of my test machines is on the Slow Ring — and it’s about to get pushed to version 20H1/2003. Oh boy.

    Anyway, word to the wise, and thanks Paul.

  • Windows Insiders watch out: Build 18947 may be worth skipping

    Warning from Zac Bowden:

    I assume Zac means both the Fast and Slow rings. Release Preview is still locked in to 19H2.

    Looks like it’s also being pushed to 64-bit machines.

    If you’re in the Fast or Slow rings, might want to sit this one out. Pause updates.

    UPDATE: Brad Sams has details on Thurrott.com:

    Users on the Insider rings know the risks of running pre-release updates, an accidental release of a build to all rings is a serious issue for Microsoft, but installing this build comes with even more risk than typical for the program. The company does try to hold back releases that will corrupt machines in the preview program but this release has slipped through without the proper telemetry to know if there are any major issues.

    ANOTHER UPDATE: According to Ed Bott on ZDNet, the bad build has been pulled.

  • Even more evidence that there will never be a “real” Win10 version 1909

    I’ve been speculating (spreading rumors?) about this for months, but it seems highly unlikely we’ll ever see anything resembling a “real” Win10 version 1909.

    Yeah, MS will release something called 1909. But it’ll just be the cumulative update we should’ve been getting all along. That’s my guess, anyway:

    https://twitter.com/h0x0d/status/1126111303339089920

    “Vibranium” is the codename for 20H1 – the version that’s in the Insider Fast Ring right now. I really, really hope they don’t call it Win10 version 2003.