Microsoft Has Started Upgrading Unmanaged Business PCs to Windows 11 26H2 on Its Own: A Layered Checklist for Small Offices
Since November 18, Microsoft has been gradually pushing Windows 11 version 26H2 automatically to personal and unmanaged business PCs running 24H2 or 25H2. Staying current is good for security, but an upgrade nobody planned can still surprise a small office. This checklist shows how layered controls turn it into a managed change.
Here Is How Layered Defenses Help Turn an Automatic Windows Upgrade Into a Planned One
If your office PCs are not enrolled in any kind of IT management, Microsoft has just become their upgrade manager. Starting November 18, the company began automatically delivering Windows 11 version 26H2 to eligible PCs that are not managed by an IT department. This checklist is based on BleepingComputer’s report and Microsoft’s Windows release health page for 26H2, with support dates from MakeUseOf.
The facts at a glance
- Who gets it automatically: personal devices and non-managed business devices running Windows 11 24H2 or 25H2. PCs managed by an IT department are not part of this first wave.
- How it arrives: gradually, depending on each PC’s Windows Update settings. Anyone can still install it early from Settings > Windows Update.
- How big a change: for 24H2 and 25H2 machines it is an enablement package that switches on features already delivered through monthly updates, usually with a single restart. MakeUseOf reports that PCs need the September 22, 2026 preview update (KB5124010) or a later cumulative update first.
- Why it matters for support: according to MakeUseOf, 24H2 Home and Pro stopped receiving updates on October 13, 2026, and 25H2 Home and Pro are supported until October 12, 2027. On 26H2, Home and Pro are supported through October 10, 2028, and Enterprise and Education through October 9, 2029.
- Known issues: Microsoft’s release health page lists open items for 26H2, including SQL Server linked server connections that can stay open over time. Separately, BleepingComputer notes Microsoft confirmed this week that the month’s hotpatch for Windows 11 24H2 and later is causing installation and launch problems for Office and some third-party apps.
The checklist, layer by layer
Layer 1: Know what you have
- List every Windows PC the business relies on, including laptops that go home and the one in the back office that runs a single important program.
- Record each machine’s Windows version (Settings > System > About) and edition. Any still on 24H2 Home or Pro are already out of support and should be the first to move.
Layer 2: Decide who controls updates
- Bring business PCs under central management so you, not a default setting, choose when feature updates land. Microsoft Intune with Windows Update for Business policies, or Group Policy in an Active Directory domain, are common examples; other device management tools can do the same job.
- Use a short deferral, not an indefinite block. The goal is a few weeks to test, not staying on an old version.
Layer 3: Test before everyone gets it
- Upgrade one or two PCs first, ideally ones used by people who will notice and report problems.
- Check the applications that matter most: accounting and line-of-business software, printers and scanners, anything that connects to a database server, and remote access tools.
- Read the release health page before widening the rollout, and remember that Microsoft can place a safeguard hold on hardware with a known compatibility problem.
Layer 4: Protect the data before the change
- Confirm each PC’s important files are backed up or synced somewhere other than the PC itself, and that you have actually restored a file from that backup recently.
- Make sure drive encryption recovery keys are stored somewhere you can reach if a machine asks for one after an upgrade.
Layer 5: Keep the other defenses on
- An up-to-date operating system is one layer. Keep endpoint protection, multi-factor authentication on email and remote access, and regular application updates running alongside it.
- Limit who has administrator rights on PCs, so a bad update or a malicious download can do less damage.
Layer 6: Close the loop
- After the rollout, check that every PC actually reports 26H2 and is receiving monthly updates. Machines that silently fail to upgrade are the ones that end up unsupported.
- Put the next support deadline on the calendar now.
What this means for your company
Microsoft’s automatic rollout is mostly good news: it moves forgotten PCs back onto a supported version and keeps security fixes flowing. The risk is not the update itself but the lack of a plan around it. A small office that discovers on Monday morning that its billing software misbehaves after an upgrade nobody scheduled loses time and money. Managing updates centrally, testing on a couple of machines first, keeping solid backups and tracking support dates turns that surprise into a routine change. And none of these steps is specific to this release; they will serve you for every feature update that follows.
If your PCs are updating on Microsoft’s schedule rather than yours, we can help you set up management, testing and backup so upgrades become uneventful. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.
