

Windows 10 continues to have shorter timeframes, with six months less time for both Pro and Enterprise/Education.įor those organizations running Windows 10 Pro, that’s going to mean a pretty tight timeframe: You won’t see a new feature update until 12 months after the previous one, and the day it comes out the six month countdown starts you must finish within that six months.

So now the only real difference is in the support timeframes. How does that affect you? First, let’s compare the (current) Windows 10 and Windows 11 lifecycles: OK, so there’s going to be one release per year for Windows 10. NET developers, where a GAC is something completely different.) The new term to use for these feature updates is now “General Availability Channel.” (You can abbreviate that as GAC, which will thoroughly confuse.

With today’s release of Windows 10 21H2 (a fairly boring release overall as there aren’t really any significant new features - thankfully it can easily be deployed to Windand above as an enablement package), Microsoft announced that there is no longer a “Semi-Annual Channel.” That’s because Windows 10 (like Windows 11) will only be updated once per year for the rest of its lifetime (at least through 2025).
