Microsoft Acknowledges Windows 11 KB5127648 Breaks Smart App Control Enablement

En bref

• Microsoft's KB5127648 update for Windows 11 can block Smart App Control from being enabled.
• The issue affects a subset of users and was acknowledged this month.
• No CVE is associated; it's a functionality regression, not a vulnerability.
• Admins should pause deployment or check for a fix.

Microsoft has confirmed that a recent security update for Windows 11, labeled KB5127648, can prevent some users from turning on Smart App Control. The problem appears after the patch is applied, and the company has acknowledged the issue. No CVE has been assigned, indicating this is a functionality regression rather than an exploitable vulnerability.

Only a portion of the user base is affected. Those who attempt to activate Smart App Control following the update may find the option unavailable or the enablement process failing. The feature is designed to block untrusted or potentially malicious applications, so its absence could leave systems with reduced protection.

The issue surfaced in October and was acknowledged by Microsoft this month. Administrators should note that the update is a security patch, so skipping it entirely carries its own risks. The company has not yet provided a timeline for a fix or a workaround.

For now, IT teams should test the update in a controlled environment before wide deployment. If Smart App Control is critical for your organization, consider delaying KB5127648 or rolling it back on affected endpoints. Watch Microsoft's release health dashboard for updates.

This is a medium-severity operational hiccup, not a critical security flaw. Still, it highlights the importance of staged rollouts and monitoring feature behavior after patching.

À faire maintenant

1. Pause broad deployment of KB5127648 until Microsoft issues a fix or workaround.
2. Test the update on a small pilot group to confirm whether Smart App Control fails to enable.
3. Check endpoints where Smart App Control is required; if broken, consider uninstalling the update.
4. Monitor Microsoft's Windows release health dashboard for official guidance.
5. Document the issue for helpdesk and inform users about potential feature unavailability.
6. Evaluate whether delaying the security update outweighs the risk of leaving Smart App Control disabled.
7. Prepare a rollback plan for affected machines if the feature is business-critical.

Source originale

BleepingComputer