A Windows key beside a closed steel padlock.
Security / The story

Windows 11 update can block Smart App Control from being turned back on

Microsoft has published a targeted workaround. Systems where the protection is already enabled remain unaffected, and 24H2 Home and Pro users face a separate support deadline.

GeekRadarStory date Published 3 min read

Microsoft has acknowledged a Windows 11 problem that can prevent Smart App Control from being turned on after the feature was previously switched off. The issue appears in the known-issues section of the October cumulative update, with guidance added on October 16.

There is an important limit to the fault: Microsoft says devices where Smart App Control is already enabled remain protected. This is a problem with enabling the feature under the affected circumstances, not a statement that the update has silently disabled it on every computer.

What Smart App Control does

Smart App Control is one of the protections available under Windows Security’s App & browser control section. Microsoft describes it as a way to block untrusted or potentially unwanted applications, working alongside Microsoft Defender or another antivirus product. It is a separate layer from a browser warning or a traditional scan of a downloaded file.

The Windows Security overview explains where that control sits among the system’s application protections. For users investigating this particular issue, the useful first step is to check its displayed state. An enabled system and a system that cannot enable it are different cases, and the support response should reflect that difference.

Use the notice for this specific update

Microsoft’s KB5127648 support page covers Windows 11 versions 24H2, 25H2 and 26H2. Its known-issue entry describes the failure to turn Smart App Control back on when it was previously off and provides temporary mitigation instructions.

For individual systems, the published procedure involves two registry overrides followed by a restart. For managed environments, Microsoft supplies corresponding policy guidance. The exact current instructions belong on that support page: copying only one setting or omitting the restart is not equivalent to following the complete procedure.

These are targeted changes for a documented fault. They should not become a general recommendation to disable security features, uninstall every October update or reset a working PC. In particular, someone whose Smart App Control is already on has no reason to apply this workaround solely because the notice exists.

Check the version before drawing conclusions

Windows support notices often name several releases because a fix or regression affects a shared component. That does not mean every device has the same support status. Windows 11 Home and Pro version 24H2 reached the end of its servicing period this week, according to Microsoft’s lifecycle table. Other editions have their own lifecycle dates.

A Home or Pro user still on 24H2 therefore has two separate questions: whether this particular control is affected, and how to move to a supported Windows release. Resolving one setting does not extend the operating system’s servicing lifecycle.

For everyone else, the response can remain narrow. Confirm the Windows version and the feature’s state, use the current KB guidance if the described failure applies, and leave an already enabled protection running. The known issue warrants a precise fix, rather than treating all of Windows Security as unavailable.