Microsoft Resolves Two-Year-Old Windows 11 Security Flaw Affecting Phishing Protection

Fixing Phishing Protection in Windows 11: What You Need to Know

Windows 11 users faced a troublesome issue where phishing protection would automatically deactivate after rebooting, particularly when utilizing a PIN for Windows Hello. Fortunately, the latest security update has addressed this persistent bug.

Overview of Phishing Protection

Phishing protection is a vital security feature integrated into Microsoft Defender SmartScreen. Its primary responsibility is to alert users when entering credentials on potentially harmful websites or when it detects unsafe practices such as storing passwords in plain text. Phishing protection is crucial for safeguarding personal and professional information in an increasingly digitized world.

Details of the KB5007651 Security Update

This week, Microsoft rolled out the KB5007651 security update for Windows Defender, which resolves the issue causing the phishing protection feature to turn off unexpectedly.

The terrible experience of manually re-enabling the feature after each reboot is largely a thing of the past, thanks to improvements made in this update.

Key Changes with KB5007651:

Persistent Phishing Protection: Enhanced phishing protection will remain enabled even after rebooting with Windows Hello using a PIN.
Improved User Experience: This update eliminates the need to constantly toggle the phishing protection settings back on, freeing users from frustration.
New Documentation Insights: Microsoft has also provided clearer guidelines on how the Phishing Protection functions under different sign-in methods.

The Role of Windows Hello and Its Impact

In the past, anyone logging in with Windows Hello using a PIN would notice that the phishing protection did not function the same way as it did with standard password sign-ins. As Microsoft’s documentation points out, signing in with a PIN or biometric identification meant users wouldn’t receive alerts or telemetry signals when attempting to access unsafe content.

This significant shortfall led to confusion, as users expected consistent security regardless of their sign-in method. Post-update, however, Enhanced Phishing Protection is now available, regardless of whether you use a PIN or a password.

User Experiences and Frustrations

The persistent issue of phishing protection turning off led to widespread user dissatisfaction. Many reported frustration, having to repeatedly enable this critical security feature every time they started their laptops. Some even considered abandoning the search for settings altogether due to the troubles faced.

Fortunately, as users have reported, the new KB5007651 security patch appears to effectively resolve the long-standing deactivation issues.

Additional Resources

For those seeking further information, consider exploring the following resources for deeper insights into phishing protection and security measures in Windows 11:

Conclusion

This recent Microsoft security update is a game changer for many Windows 11 users, as it seeks to restore normalcy in phishing protection operations. For all users, keeping this feature active is now much more manageable and essential for maintaining security online.

Additional Insights

1. What changes were made in the latest security update for Windows 11?

The KB5007651 security update fixes the bug where phishing protection would deactivate after rebooting when using Windows Hello with a PIN. It now ensures that the protection remains active, significantly enhancing security for all users.

2. How does Enhanced Phishing Protection work with different sign-in methods?

Enhanced Phishing Protection provides alerts and notifications when logging in with a password but previously lacked alerts when using a Windows Hello PIN. The latest update ensures that protection remains engaged, regardless of the sign-in method.

3. Where can I find the phishing protection settings in Windows 11?

You can locate the phishing protection toggle within the Windows Security app, specifically under the Reputation-based protection settings. Make sure to verify that this is enabled after any reboot.

Source & Images