• What’s an SAC-T? What’s going to happen to the old SBB? And why should you care?

    Microsoft’s terminology for Windows 10 releases is so infernally screwed up it’s hard to imagine the official terms could get any worse.

    Don’t hold your breath.

    Late last week, we got word that “Semi-Annual Channel (SAC) – Targeted” gobbledygook is going away – to be replaced by what, we don’t know.

    There’s been so much turmoil in the terminology that you might (rightfully) assume that the people in charge don’t have a clue what they’re doing. And, in my humble opinion, you’d be right.

    I think it’s likely that Microsoft will move farther toward the “we’ll update/upgrade your Win10 machine whenever we feel like it” end of the spectrum. Chances are good they’ll use this new terminology change to mask the process.

    We’ve already seen a move in that direction. In Win10 1703 and 1709, we (delightfully!) got an easy-to-use interface for Win10 Pro update deferral settings. The settings were never precisely explained, but such is life in Microsoft land.

    Then, in 1803, things changed. Arguably the worst “feature” in 1803 is its hiding of those deferral settings, pushing them back into the Group Policies whence they came. You can still defer cumulative updates and “feature enhancements” (better understood as version changes), but only on Pro and Enterprise, and only by using the arcane Group Policy interface.

    Now we’re looking forward to yet another change. Oh boy.

    Look, folks. All I want is a simple “Off” switch – let me decide when you can apply updates. That’s what we had in Win7 and 8.1. That’s what we need right now.

    Our own @Zero2dash put it this way:

    “I am altering the deal. Pray I don’t alter it any further.” How many times has the deal been altered at this point? I’ve lost count. This is no bueno. I foresee a whole lot more “accidental” upgrades in the future for everyone.

    (I’ve moved the comments on his topic over to this one.)