AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Latest Windows update disables key security setting – but there’s a workaround

Collected Oct 20, 2026

Microsoft's Patch Tuesday update for Windows 11, released on October 13, shipped with a bug that disables the Smart App Control security setting. Smart App Control, added to Windows 11 in 2022, blocks potentially malicious or suspicious apps and files from infecting a PC. It is stricter than some of the other security features built into Windows, aimed at protecting against new and emerging threats.

The glitch only bites in one direction. Machines where Smart App Control is already enabled keep that protection. On systems where the feature is currently off, the October update grays out the button that would turn it on, leaving no way to activate it through the normal Settings interface. ZDNET tested three Windows 11 PCs carrying this month's update and one that had not yet been updated; the option was grayed out on the three updated machines and still available on the one that had not taken the patch.

Microsoft has acknowledged the problem and says it is working on a fix that will arrive in a future release. Until that lands, the company has published steps for a Registry workaround that restores the ability to switch the feature on.

To confirm whether a PC is affected, open Settings, go to Privacy & security, and then Windows Security. In the Protection areas section, choose App & browser control, and in the window that opens, click the link for Smart App Control settings. If the feature shows as Off and the On option is grayed out, the machine has hit the bug.

The fix runs through an elevated command prompt. Typing cmd in the Search box and choosing Run as administrator is necessary; without administrator rights the Registry cannot be modified. At the prompt, two commands are entered one after the other, each writing a REG_DWORD value of 1 under the FeatureManagement Overrides policy key: the first names value 2883193997 and the second names value 2850574478, both using the /f flag to force the write. After each command, the prompt should confirm the operation completed successfully. The next step is to close the command prompt, reboot the PC, and return to the same Smart App Control settings screen, where the On option should once again be selectable.

For developers and product teams, the incident is a small but instructive example of how a monthly cumulative update can quietly change security posture across a fleet. Smart App Control is one of the more aggressive defenses in Windows 11: it is designed to stop untrusted or low-reputation executables before they run, rather than detecting them after the fact. That posture makes it attractive for locked-down machines and inconvenient for anyone who installs software from unfamiliar sources. The setting has been framed as something users may want to try and disable later if it becomes disruptive, on the theory that blocking unknown malware is worth some friction.

A likely trade-off is that a Registry override is a blunt instrument. It changes policy under a system key, so it needs administrator rights and a reboot, and in managed environments it could collide with Group Policy or other configuration management already writing to the same area. A safer approach for IT teams is to check whether affected endpoints already have the feature on, since those are unaffected, and to wait for Microsoft's official patch for the rest unless the gap is unacceptable. A useful question is whether a device management tool can detect the grayed-out state as part of routine compliance checks, rather than relying on users to notice.

Why it matters: Anyone provisioning or supporting Windows 11 machines after the October 13 update faces a choice between an unsanctioned Registry edit and leaving Smart App Control off until Microsoft ships a fix. Organizations that standardize on the feature should verify which endpoints are affected, since only machines with it disabled are hit, and plan how to apply and later unwind the workaround. This suggests patch management workflows should include a post-update check of security toggles, not just the install itself, because a cumulative update can alter settings without breaking anything visibly.

Read at ZDNet · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

A bug in Microsoft’s October Windows update prevents you from turning on a security setting that blocks malicious or suspicious apps. A Registry hack fixes the glitch.