
Windows 11 version 26H2 is now generally available—but this is a phased feature-update rollout, not a new Patch Tuesday security release and not a signal to force it onto every PC tonight. Microsoft began offering the Windows 11 2026 Update on September 29 to eligible Windows 11 25H2 and 24H2 devices, starting with PCs whose owners have enabled early access to the latest updates.[1]
Reporting cutoff: September 29, 2026 at 7:10 p.m. EDT (23:10 UTC). We rechecked Microsoft’s Windows Message Center, 26H2 release-health page, release-information table, KB5124010 history, deployment guidance, and Apple’s security-release surfaces at this cutoff.
The short version
- What happened: Windows 11 26H2 reached general availability on September 29.[1]
- Who gets it first: eligible Windows 11 25H2 and 24H2 PCs with “Get the latest updates as soon as they’re available” enabled.[2]
- What it is not: it is not a new September 29 security patch. KB5124010 was first released September 22 as an optional, non-security preview update; Microsoft added 26H2 applicability on September 29.[4]
- Best home-user move: use Windows Update and wait for Microsoft to offer 26H2 to your PC. Do not bypass a safeguard hold just to get it sooner.
- Best business move: pilot 26H2 on representative hardware and workflows before expanding deployment, especially if you use USB Audio Class 1.0 devices, on-premises Active Directory with Machine Identity Isolation, Azure Virtual Desktop, or FSLogix.
What Windows 11 26H2 general availability means
General availability moves 26H2 beyond Insider and Release Preview testing into Microsoft’s production servicing channel. Microsoft describes 26H2 as an annual feature update that shares a servicing foundation with 25H2 and 24H2, allowing eligible systems to install it with a relatively small download and a quick restart.[5]
The rollout is gradual and will expand over the next few months. A compatible PC can still be temporarily held back when Microsoft detects an application, driver, or hardware conflict; that compatibility block is called a safeguard hold.[1][7]
Affected and not affected
| Device or environment | 26H2 rollout status | Practical interpretation |
|---|---|---|
| Windows 11 25H2 | Eligible source version | May be offered 26H2 now if the device is eligible and early-update access is enabled.[1] |
| Windows 11 24H2 | Eligible source version | May be offered 26H2 through the same phased path.[1] |
| Windows 11 26H1 | Not named in the reviewed consumer GA offer path | Do not assume the 24H2/25H2 offer instructions apply; follow the device maker’s servicing path.[2] |
| Windows 11 23H2 or older | Not named in the reviewed consumer GA offer path | Check support status and move to a currently supported path before treating 26H2 as a one-step upgrade.[2] |
| Windows 10 | Not named in Microsoft’s 26H2 GA offer path | 26H2 is a Windows 11 release; a Windows 10 PC needs a separate Windows 11 eligibility and migration decision.[2] |
| macOS | Not affected | Apple’s latest macOS releases were dated September 28, not September 29.[8] |
Build and KB details: do not confuse the dates
| Date | Event | Build or KB | Classification |
|---|---|---|---|
| September 22, 2026 | KB5124010 first released | 26200.9550 / 26100.9550 | Optional non-security preview for 25H2 and 24H2.[4] |
| September 29, 2026 | 26H2 reaches general availability | 26300.9457 | Production feature-update baseline; no KB is shown for this row in Microsoft’s release table.[3] |
| September 29, 2026 | 26H2 applicability added to KB5124010 | 26300.9550 / KB5124010 | D-type optional non-security preview.[3][4] |
| October 13, 2026 | First scheduled monthly security update for 26H2 | Not yet published at this cutoff | Planned security servicing date.[6] |
Microsoft’s release-information table lists 26H2 in the General Availability Channel with build family 26300 and current build 26300.9550 at our cutoff.[3] The KB5124010 support page still identifies the package as the September 22 Preview and says 26H2 support was added on September 29.[4] In other words: September 29 is the 26H2 launch date, not the release date of a new security patch.
Known issues to check before you roll out 26H2
Microsoft’s 26H2 release-health page listed three mitigated issues at the cutoff. “Mitigated” does not mean every symptom has a permanent fix; Microsoft says future Windows updates are still planned for these items.[2]
1. Some USB Audio Class 1.0 devices may fail
Symptoms can include Device Manager Code 10, no audio output, a volume control stuck at zero, or unavailable sound settings. Microsoft limits this issue to USB Audio Class 1.0 devices and lists a broad affected range spanning several Windows 10, Windows 11, and Windows Server versions—not only 26H2.[2]
What to do: before a broad business rollout, test conference-room audio, USB headsets, capture devices, and any specialized USB audio hardware. IT administrators whose symptoms are not covered by the available out-of-band mitigation should use Microsoft Support for Business; Microsoft does not publish a universal consumer workaround on the 26H2 page.[2]
2. Domain trust can fail in a narrow Machine Identity Isolation scenario
Some Credential Guard-protected machine accounts can lose their secure channel to an on-premises Active Directory domain when Machine Identity Isolation enforcement was already enabled but the environment is not using domain controllers at Windows Server 2025 Domain Functional Level or later. Valid interactive domain sign-ins can fail, although cached offline sign-in may continue to work; Microsoft says AD replication and domain-controller services are not affected.[2]
What to do: this is an administrator issue, not a reason for ordinary home users to edit the registry. Microsoft’s workaround is to disable Machine Identity Isolation through the same management method that enabled it, restart, and repair the secure channel. Organizations should review Microsoft’s exact Intune, Group Policy, or registry instructions and back up the registry before any direct registry change.[2]
3. AVD and FSLogix desktops may show a black screen
Microsoft says some devices may show a black screen or fail to load the desktop after sign-in, primarily on Azure Virtual Desktop hosts using FSLogix and more often with some existing user profiles. The issue is not described as a general home-PC failure.[2]
What to do: an affected user can temporarily start explorer.exe through Task Manager. Managed environments can deploy Microsoft’s KB5124010 Known Issue Rollback Group Policy and restart the affected systems; that KIR is an enterprise mitigation, not general consumer upgrade advice.[2]
What home users should do
- Back up important files first. A feature update should not be your only copy of photos, tax records, or work documents.
- Open Settings → Windows Update. If you want early access, turn on Get the latest updates as soon as they’re available, then select Check for updates.[5]
- Install only when 26H2 is actually offered. An absent offer can mean your device is later in the phased rollout or is protected by a safeguard hold.
- Leave time to test. After the restart, check audio, printers, cameras, VPN access, sleep/wake, Windows Hello, and your most important applications.
- Confirm the version. Press Windows+R, type
winver, and verify that Windows reports version 26H2. For deeper troubleshooting, use our Windows 11 update troubleshooting guide.
What businesses and managed fleets should do
- Inventory source versions and hardware. Separate 24H2, 25H2, 26H1, older Windows 11, Windows 10, and special-purpose systems before assigning deployment policy.
- Build a representative pilot ring. Include common laptop models, docks, USB audio devices, VPN and security clients, line-of-business applications, AVD/FSLogix profiles, and domain-authentication paths.
- Review safeguard and known-issue status. Do not remove a hold merely to keep a date on a project plan.
- Preserve recovery options. Verify current backups, BitLocker recovery-key custody, spare-device capacity, and a tested rollback/escalation path before broad deployment.
- Expand only after measured success. Microsoft says existing update rings, policies, and deployment practices can continue to manage 26H2, and it recommends targeted deployments before wider rollout.[5][6]
Good
- The enablement-style delivery should be quicker than a traditional full OS replacement on eligible 24H2 and 25H2 PCs.[5]
- The phased rollout gives Microsoft and administrators time to apply compatibility holds.
- 26H2 starts a new servicing window: Microsoft lists support through October 10, 2028 for Home/Pro-class editions and October 9, 2029 for Enterprise/Education-class editions.[3]
Cautions
- General availability does not mean every compatible PC should receive 26H2 immediately.
- KB5124010 is an optional non-security preview, not a new security update released on September 29.[4]
- Three known-issue areas deserve testing: USB Audio Class 1.0, Machine Identity Isolation with on-premises AD, and AVD/FSLogix desktop loading.[2]
- A forced upgrade that bypasses a safeguard can trade a quick version number for preventable downtime.
FAQ
Is Windows 11 26H2 a security update?
No. September 29 marks the general-availability launch of a Windows 11 feature update. KB5124010 is a non-security preview first released September 22, and Microsoft says 26H2’s first scheduled monthly security update is October 13.[4][6]
Should I use the Installation Assistant if Windows Update does not offer 26H2?
Usually not as a first move. If Windows Update has not offered 26H2, your PC may simply be later in the phased rollout or subject to a compatibility safeguard. Waiting preserves Microsoft’s device-specific gating.[7]
Can Windows 10 upgrade directly through this rollout?
No direct Windows 10 source path is named in Microsoft’s 26H2 GA instructions. A Windows 10 computer needs a separate Windows 11 eligibility, application-compatibility, backup, and migration review.[2]
Do I need the optional KB5124010 preview?
Not necessarily. It is an optional non-security preview. Home users who are not troubleshooting a specific addressed issue can generally wait for normal Windows servicing rather than installing every preview package.[4]
Need help deciding whether to update?
The IT Guys can check Windows 11 eligibility, backups, BitLocker recovery readiness, line-of-business applications, drivers, and a safe rollout plan for homes and small businesses in Port Saint Lucie, Jensen Beach, Fort Pierce, and Vero Beach. Schedule an appointment.
Official sources checked
- Microsoft Windows Message Center — How to get the Windows 11 2026 Update
- Microsoft Windows 11, version 26H2 known issues and notifications
- Microsoft Windows 11 release information
- Microsoft Support — September 22, 2026—KB5124010 Preview
- Windows Experience Blog — How to get the Windows 11 2026 Update
- Windows IT Pro Blog — An IT pro’s guide to Windows 11, version 26H2
- Microsoft Support — How to check safeguard holds affecting your device
- Apple security releases
