Microsoft has resolved a known issue that prevented some Windows 11 machines from activating Smart App Control after the October 2026 security update, KB5127648, BleepingComputer reported. For administrators running managed fleets, the story carries a specific warning: an estate can show a successful cumulative rollout while a security control on those same endpoints silently fails to come up.
Smart App Control is a Windows 11 security layer that blocks untrusted or potentially unwanted applications, drawing on reputation-based intelligence and, in some configurations, code signing. Its design is what makes this defect matter. The feature is meant to be activated at or near the time of a clean install; once a device falls into a failed or disabled state, bringing it back is not straightforward. That is also why an activation failure reads very differently from a surface-level bug — a machine can look patched and compliant while a protection control it was supposed to carry simply is not there.
The source describes the problem as an activation failure rather than a vulnerability, and reports no sign the defect was exploited. The impact sits in protection posture rather than update integrity: devices that took KB5127648 as part of the October cumulative found Smart App Control would not enable.
BleepingComputer reports the fix as delivered but does not say whether it reaches deployed machines as an out-of-band patch, a known-issue rollback, or part of the next cumulative update, nor which builds and architectures were affected — both details administrators will need from Microsoft's release and known-issues documentation before scoping an audit.
The timeline was relatively compressed. Microsoft documented the activation problem as a known issue affecting some users after the October KB5127648 release, and the announced resolution closes it out within roughly a single update cycle.
For Windows administrators, the takeaway is a single, easily missed distinction: patch delivery and security-control health are not the same check. Confirm the fix has arrived, confirm Smart App Control is actually active, and flag any device still sitting in a failed state for follow-up before the November cycle begins.
據BleepingComputer報道，微軟已解決一項已知問題，該問題令部分Windows 11電腦在安裝2026年10月安全更新KB5127648後無法啟用Smart App Control。對於管理受管裝置群組的系統管理員而言，此事帶有特定警示：整個系統環境可能顯示累積更新部署成功，但同一批endpoint上的某項安全控制卻悄悄未能啟動。
Smart App Control是Windows 11的一項安全層，用於攔截不受信任或可能不受歡迎的應用程式，其運作依賴信譽評分智能，某些配置下亦會運用code signing（程式碼簽章）。正是其設計令此缺陷顯得重要。該功能理應在全新安裝時或前後啟用；一旦裝置落入啟用失敗或已停用狀態，要將其恢復並非易事。這也是為何啟用失敗與表面問題的性質截然不同 — 一部電腦表面上可以看似已修補及合規，但它本應具備的防護控制實際上根本不存在。
消息來源將問題描述為啟用失敗（activation failure），而非漏洞（vulnerability），並指沒有跡象顯示該缺陷曾被利用。其影響屬於防護狀態（protection posture）層面，而非更新完整性：已作為10月累積更新一部分安裝KB5127648的裝置，發現Smart App Control無法啟用。
BleepingComputer報道修復已交付，但未有說明該修復是以out-of-band patch（帶外修補程式）、已知問題還原（known-issue rollback），還是併入下一次累積更新的方式觸及已部署的裝置，亦未交代哪些build及架構受影響 — 這兩項細節均須向微軟的發布及已知問題文件查證，系統管理員方可據以釐定審計範圍。
相關時間表相對緊湊。微軟將啟用問題記錄為已知問題，影響10月KB5127648發布後的部分用戶，而公布的解決方案在大約一個更新周期內將其標示為已解決。
對Windows系統管理員而言，要點在於一個容易忽略的區分：修補程式交付（patch delivery）與安全控制健康狀況並非同一項檢查。應確認修復已經送達、確認Smart App Control確實處於啟用狀態，並在11月周期開始前，將任何仍停留在失敗狀態的裝置標記並跟進處理。