Latest

Technology

Windows 11 26H2 starts installing itself on more devices

Starting November 18, Microsoft is expanding the automatic delivery of Windows 11 26H2 to devices running 24H2 and 25H2 without an IT manager, in phases and without asking permission.

Translated from Spanish by an automated system. The Spanish original prevails. Read the Spanish original

Windows 11 26H2 starts installing itself on more devices
Windows 11 26H2 starts installing itself on more devices

Microsoft stopped waiting for users to give permission. Since November 18, devices running Windows 11 24H2 and 25H2 that are not managed by an IT department can receive version 26H2 without touching a single button: the update downloads on its own when Windows Update decides, and the company is expanding the rollout in phases. The change appears on the version 26H2 status page, which presents it as the next step after the controlled rollout that began a month ago.

Anyone who already updated manually will notice nothing new, because since late October all eligible devices could download 26H2 by checking for updates in Settings. The difference is for everyone else: that majority who never go there until something breaks. From now on the new version arrives through the same channel as a Patch Tuesday update, with the caveat that the pace is set by each machine's telemetry rather than a public calendar.

The practical consequence is a change in who owns the decision. On a home device, or on the laptop of a micro-business without an administrator, updating stops being a choice and becomes a consequence of the default configuration, which almost nobody has ever reviewed. Anyone who wants to keep control has two levers: the deferral options and the toggle that decides whether the system installs new releases as soon as they appear.

An automatic change

The status page narrows the scope. Automatic delivery starts on devices running 24H2 or 25H2 that are not managed by an IT department, whether personal or business machines without an administrator. Microsoft warns that the process depends on Windows Update settings, so two identical laptops can receive 26H2 weeks apart.

That uneven distribution is the norm in recent Windows rollouts, which is why forums fill up with questions from people who see the update and people who don't, with the same laptop model on the desk.

There is an intermediate lever that many people don't know about. The launch announcement on the Windows blog explains that enabling the option to receive new releases as soon as they are available brings the update forward, and that the system applies compatibility holds when it detects a known problem. Translated: whoever has that box checked becomes an early tester without having fully asked for it.

In companies with an administrator the map doesn't change. Managed devices continue to receive the version through corporate channels, with deployment rings and their own policies, and that separation explains why the announcement reads as home news when it also affects small businesses without internal technical support.

An update that weighs less than it appears to

The scare of a version update doesn't match what happens on disk. The Windows blog describes 26H2 as an enablement package: a small file that doesn't replace the operating system but unlocks features that were already included in previous monthly updates and that the device had dormant.

Versions 26H2, 25H2 and 24H2 share a servicing branch and much of the code, so the installation looks more like a monthly patch than a migration, with one reboot and a reduced download.

The visible part of the package is the November cumulative update. The KB5132061 page, dated November 10, serves the same update to all three versions and leaves 26H2 on build 26300.9974; among its fixes is a USB audio bug that left speakers and microphones with Code 10 error. That is the kind of detail that decides whether an update is noticeable or not.

The recent history of that page shows how Microsoft behaves when something goes wrong. The previous cumulative update, published on October 28 as a preview, left some devices in a loop with errors 0x80070306, 0x800f0989 and 0x800f0993; the company sent an automatic repair from November 11 and maintains that affected users were resolved within 24 or 48 hours.

The matter of the 0x800f0993 error in the November cumulative update we already covered this morning, and what this piece adds is the context of the mass rollout pushing that same update to devices that haven't asked for it.

The brakes Microsoft keeps in place

The expansion doesn't mean open season. The status page keeps open an issue with SQL Server linked-server connections that may remain alive after the October updates, confirmed on November 12, and that list is what decides whether a specific device sees the 26H2 offer or not. As long as a model appears on it, the new version doesn't arrive.

For the reader with a single computer at home, preparation comes down to three checks: free disk space, an up-to-date backup and a list of the programs that depend on old drivers, which are the first to break.

Anyone coming from Windows 10 doesn't need to go through an intermediate version of Windows 11 first. The official download page lists 26H2 as the current version and offers the Installation Assistant for the device in use, with the requirement of having a Windows 10 or 11 license and a build 2004 or later. It is the quick route for anyone who fell behind and prefers to jump straight away.

One detail about installation media is worth treating with caution. The Media Creation Tool was updated to include the November cumulative update and the most recent Defender definitions, a point that does not appear in the official documentation consulted and that stands as specialist press information, not as Microsoft confirmation.

The support clock resets

There is a less visible reason not to resist. Installing 26H2 resets the support cycle for compatible editions, with 24 months for Home and Pro and 36 months for Enterprise and Education, according to the September announcement. Anyone who stays on 24H2 doesn't lose the device overnight, but starts counting toward a date that arrives sooner than it seems.

The other change is behavioral: features that came disabled by default in 25H2 become active in 26H2, and that is the real reason the update is noticeable despite its size.

The first week of 26H2 was not calm, and that helps explain the caution of the phased rollout. The failures we documented in the review of those first days arrived with half-finished patches and the sense that the version was cooked up in a hurry, exactly what is now spreading to machines that cannot afford an afternoon out of action.

What remains to be seen in the 26H2 rollout

The automatic rollout will move in the coming weeks by telemetry, not by announcements, and the useful signal will be the list of known issues: if the compatibility holds are lifted and no new incidents appear, the distribution will speed up without a press release. If the opposite happens, Microsoft will repeat the October pattern, with silent repairs and late notes on the status page.

For anyone managing devices without an IT department, the question is no longer whether to update, but when it is convenient for it to happen. The honest answer is that the decision is made in Settings, in two checkboxes almost nobody looks at, and that the margin shrinks as the rollout advances.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
Gemini 4 Neon cuts Google's coding to $3 per input

Keep reading