Newsletter Archives

• Win10 updating terminology is changing again – but this time maybe it’s tied to a major improvement

  Posted on February 14, 2019 at 19:06 CST by woody • Comment in the Forums

  In retrospect, I’m not convinced the terminology change is tied to anything worthwhile.

  Details in Computerworld Woody on Windows.

  Here’s my earlier, rosier take…..

   

  ******************************************

  At least I have my fingers crossed.

  First, John Wilcox announced on the Windows IT Pro blog:

  IF YOU USE WINDOWS UPDATE FOR BUSINESS: Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T [Semi-Annual Channel Targeted] information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release.

  That’s a major change to the meaning of SAC-T. I’ve long used the promotion of a Win10 version to SAC (from SAC-T) as an indication that it may be ready, in a few months, to install. Wilcox shows a screenshot of the new Win10 version 1903 Windows Update Advanced options pane, and it’s substantially different from what we’re seeing now.

  Reason to be cynical – Oh gawd, they changed the terminology again.

  Reason to be hopeful – maybe this means that when a new Win10 version is released it’ll be, you know, tested.

  Combine that with more unexpected news. People in the Windows Insider Program Skip Ahead ring were expecting to start testing version 19H2 (for lack of a better term, probably destined to become Win10 version 1909). But earlier today, Microsoft released Skip Ahead build 18336. According to Dona Sarkar and Brandon LeBlanc:

  These builds are from the 20H1 development branch. Some things we are working on in 20H1 require a longer lead time. We will begin releasing 19H2 bits to Insiders later this spring after we get 19H1 nearly finished and ready; once 19H1 is “nearly finished and ready” we’ll also use the Release Preview ring for previews of drivers and quality updates on 19H1.

  Which is an incredibly convoluted way to run a beta program, unless….

  … unless the talk of 19H2 is a smokescreen, and Microsoft’s finally going to start releasing new versions of Win10 every year.

  Hey, a guy can hope.

  Other 18836, 19H1, 20H1, Win10