Microsoft has begun pushing the Windows 11 26H2 feature update straight to eligible machines that sit outside any management system, BleepingComputer reported on 20 November. For administrators, the interesting question is not what the update contains — it is which machines get it, and who finds out first.

One important guardrail before the panic: 26H2 does not land on every Windows PC. Delivery still gates on Microsoft's standard Windows 11 hardware requirements, so machines that never qualified for Windows 11 in the first place are unaffected. The exposure is limited to eligible hardware running an unsupported or soon-to-be-superseded Windows 11 release outside the organisation's management envelope.

The managed/unmanaged split

Devices enrolled in a management system — Intune or another MDM, domain-joined machines, endpoints governed by Windows Update for Business, WSUS, or Group Policy — keep the controls IT already uses: feature-update deferrals, staged rollout rings, approval checkpoints, and scheduling around maintenance windows.

Devices with none of those anchors — personal PCs, staff-owned laptops touching corporate resources, and endpoints that simply fell out of inventory — receive 26H2 directly through Windows Update, installed automatically with no remote administrative lever to slow it down.

The risk is therefore about timing and visibility rather than the update's content. Unmanaged endpoints may take the feature update before anyone has run line-of-business or peripheral-device compatibility testing. In many organisations the first signal of a problem will be a user reporting that an application no longer launches — not a dashboard alert.

Organisations running mixed fleets should expect this pattern to continue: Microsoft increasingly treats feature updates for the consumer and unmanaged segment as continuous delivery rather than a discrete, administrator-controlled event.

A compliance footnote

Devices outside management are not automatically outside responsibility. Where staff-owned machines handle customer personal data, the obligations that apply to that processing do not vanish because the endpoint sits in someone's home. Teams should treat unmanaged, data-touching endpoints as a known gap and record the decision — an unassessed device is harder to defend than a documented one.

This week's checklist

  • Find the blind spots. Reconcile device inventories against your authentication and endpoint logs. Any machine authenticating to corporate services without an active MDM, Intune, WSUS, or WUfB policy is unmanaged — and that is the population receiving 26H2 without your sign-off. Note explicitly which of those also process customer data.

  • Confirm enrollment coverage, then control the timing where you still can. Verify that fleet machines are actually enrolled: Settings > Accounts > Access work or school should show your organisation's connection, or check the Intune device record directly. For machines you do manage, set or confirm feature-update deferrals under Settings > Windows Update > Advanced options > Feature updates, or via the equivalent WUfB ring policy, so 26H2 lands after your test cohort rather than alongside it. Where a device is unmanaged and you need breathing room, the only remaining levers are the user's own: Settings > Windows Update offers pause updates (up to five weeks) and the option to delay "get the latest updates as soon as they're available."

  • Run compatibility checks and document the gap. Before the rollout reaches a machine you cannot block, test line-of-business applications, printers, scanners, VPN clients, and security agents against 26H2 — and log any device you could not test because it sits outside management. That record is what separates a defensible patch posture from an unplanned one when the first application breaks.

Additional guidance on restart timing, BYOD policy positions, and pause controls will follow in a separate tips post.


據 BleepingComputer 於 11 月 20 日報導,微軟已開始將 Windows 11 26H2 功能更新直接推送至符合條件、但處於任何管理系統之外的電腦。對系統管理員而言,有趣的問題並非更新內容為何 — 而是哪些電腦會收到更新,以及誰會最先知情。

在恐慌之前,先了解一項重要防護機制: 26H2 並非適用於所有 Windows 電腦。推送仍然取決於微軟標準的 Windows 11 硬件要求,因此原本就不符合 Windows 11 資格的電腦不受影響。風險範圍僅限於符合資格的硬件,而這些硬件正運行不受支持或即將被取代的 Windows 11 版本,並且處於機構管理範圍之外。

受管理與不受管理的分野

已登記於管理系統的裝置 — 包括 Intune 或其他 MDM、已加入網域的電腦、受 Windows Update for Business、WSUS 或群組原則管轄的端點 — 仍然沿用 IT 部門現有的控制手段:功能更新延遲、分階段推出環(staged rollout rings)、核准關口,以及圍繞維護窗口的排程。

完全沒有上述管控錨點的裝置 — 即個人電腦、接駁公司資源的員工自備筆記型電腦,以及單純從資產清單中遺漏的端點 — 會透過 Windows Update 直接接收 26H2,自動安裝,沒有任何遠端管理手段可以減緩其速度。

因此,風險在於時機與可見度,而非更新內容本身。不受管理的端點可能在任何人進行核心業務應用或周邊裝置相容性測試之前,就先行取得功能更新。在許多機構中,問題的首個信號將是用戶反映某應用程式無法啟動 — 而非儀表板上的警報。

採用混合裝置隊列的機構應預期此模式將持續:微軟越來越多地將面向消費者及不受管理範疇的功能更新視為持續交付(continuous delivery),而非一項由管理員控制的離散事件。

合規性補註

處於管理範圍之外的裝置,並不代表自動免除責任。當員工自備機器處理客戶個人資料時,適用於該處理活動的義務,並不會因為端點位於某人家中而消失。團隊應將涉及數據的不受管理端點視為已知缺口,並記錄相關決定 — 未經評估的裝置比有文件記錄的裝置更難以辯護。

本周清單

  • 找出盲點。 將裝置資產清單與身份驗證及端點日誌互相核對。任何在沒有有效 MDM、Intune、WSUS 或 WUfB 政策下向公司服務進行身份驗證的電腦,均屬不受管理 — 而這正是未經你批准便接收 26H2 的群體。請明確註明其中哪些裝置同時處理客戶數據。

  • 確認登記覆蓋率,然後在仍可行的情況下控制時機。 核實隊列中的電腦確實已登記:設定 > 帳戶 > 存取工作或學校 應顯示貴機構的連接,或直接查閱 Intune 裝置記錄。對於你確實管理的電腦,請在 設定 > Windows Update > 進階選項 > 功能更新 下設定或確認功能更新延遲,或透過相應的 WUfB 環原則進行設定,使 26H2 在你的測試組別之後而非同期推出。若某裝置不受管理而你需要緩衝空間,則僅餘的控制手段只屬於用戶本人:設定 > Windows Update 提供暫停更新(最長五週)以及延遲「在有最新更新時立即取得」的選項。

  • 進行相容性測試並記錄缺口。 在推出範圍抵達你無法阻擋的電腦之前,請針對 26H2 測試核心業務應用程式、打印機、掃描器、VPN 客戶端及保安代理 — 並記錄任何因處於管理範圍之外而無法測試的裝置。當首個應用程式出現故障時,這份記錄正是區分可辯護的補丁狀態與欠缺規劃的狀態的關鍵。

有關重啟時機、BYOD 政策立場及暫停控制的進一步指引,將於另一篇技巧文章中跟進。

新聞來源 / Original News Source