This article is more than 1 year old
Another reprieve for exhausted IT admins: Looks like there are no whizzbangers in Windows 10 21H1
Still Missing In Action for Windows Insiders
Windows 10 21H1 is on its way, and seemingly without the major new features we've come to expect in a Microsoft spring rollout, if a post on Redmond's Windows Hardware Certification blog is anything to go by.
Confirmation coming through the Windows Hardware Compatibility Program (WHCP) is another departure from the norm. The usual suspects, Microsoft's Windows Insider team, haven't made a peep about it: perhaps they are too busy breaking ARM64 support to tell us about new Windows versions.
As many have suspected, the update appears to be a retread of last year's Windows 10 20H2 release, at least as far as drivers are concerned. If it works on Windows 10 2004 (released in the first half of last year) then things aren't changing from a WHCP perspective.
Should 21H1 indeed be little more than a jumped-up cumulative update, it will mark a change from recent years where Microsoft has unveiled new features in the spring and made the autumn code drop a simple and quick to install update (if you were running Windows 10 2004). This isn't ideal for enthusiasts thirsting for the next big thing, but will be a blessed relief for enterprises faced with rolling out the software to fleets of company hardware.
Another half-year without significant update will please those same IT administrators even as the fans stare glumly at a distinct lack of innovation in test versions published by the Windows Insider team.
The Windows Insider program has yet to have a sniff of Windows 10 21H1 in any of its channels, although one would hope that the confirmation of its existence will result in some movement over the coming days and weeks.
A commenter on the blog post observed: "So, confirming 21H1 then? Perhaps ask your colleagues on the Windows 10 team to let their Insiders know what's going on, please?"
Quite. However, such communication would require attention to be diverted from borking one or more components related to Dev Channel Windows 10 support for ARM64. And that would never do. ®