Fix Windows 11 KB5055523 BSODs and Windows Hello Errors in 2025

The Windows 11 24H2 update introduced exciting features like AI-driven Copilot enhancements and a revamped File Explorer, but it’s caused headaches for many users. Reports of Blue Screen of Death (BSOD) crashes—especially when waking from sleep—and Windows Hello authentication failures are widespread, particularly after installing patches like KB5055523 (April 2025). These issues can disrupt everything from work meetings to gaming sessions. If your PC is misbehaving, our detailed guide offers tested fixes to resolve BSODs and Windows Hello errors, so you can enjoy Windows 11 again.

Why Are BSODs and Windows Hello Errors Happening?

The Windows 11 24H2 update, while packed with useful improvements, has some issues that only show up on specific hardware and software configurations:

• BSODs: Crashes often occur from wake-from-sleep conflicts, outdated drivers (like SenseShield’s sprotect.sys), or update glitches. Common error codes include “SYSTEM_SERVICE_EXCEPTION” or “DRIVER_POWER_STATE_FAILURE.”
• Windows Hello: Face and fingerprint logins fail on systems with Dynamic Root of Trust Measurement (DRTM) or System Guard Secure Launch, leaving users stuck at the login screen.
• Other Issues: Misaligned File Explorer menus (addressed in KB5055523), random app crashes, and sluggish performance have also surfaced.

Well, Microsoft’s recent updates fix many bugs, but some users need hands-on solutions. Here, we explore how to fix Windows BSODs and Windows Hello errors step by step.

Fix 1: Resolve BSODs in Windows 11 24H2

Windows Blue screen of death (BSODs) can freeze your PC at the worst moments—mid-email, during a game, or right after waking your laptop. Most Windows BSOD crashes tie back to driver conflicts, power settings, or buggy updates. Here’s how to stop them.

Update Drivers

Outdated or incompatible drivers, especially for graphics cards, network adapters, or third-party security software, are a leading cause of BSODs in Windows 11. For example, a user report on the Microsoft forum reported crashes with an old NVIDIA driver that hadn’t been updated since 2023. Updating ensures your hardware plays nicely with the latest Windows changes.

• Press Win + X and select Device Manager to see all your hardware.
• Look for yellow triangles or exclamation marks, which flag problematic devices—often under “Display adapters,” “Network adapters,” or “System devices.”
• Right-click a flagged device, select Update driver, then Search automatically for drivers.
• Windows will pull the latest compatible version from Microsoft’s servers.

If auto-updates fail, visit your hardware manufacturer’s website:

• For graphics, check NVIDIA, AMD, or Intel.
• For laptops, go to your brand’s support page (e.g., Dell, HP, Lenovo) for driver bundles.

Download and install the latest driver, restarting your PC afterward.

Note: SenseShield’s sprotect.sys driver, used in some security apps, is a known BSOD culprit in Windows 11 24H2. Search for it in Settings > Apps > Installed apps. If found, uninstall the app or contact the vendor for a 24H2-compatible update.

Disable Fast Startup

Windows Fast Startup feature, enabled by default, speeds up boot times by saving system info to a hibernation file, but it can clash with Windows 11 24H2’s power management, triggering BSODs when your PC wakes from sleep. Gamers and remote workers have reported crashes after leaving their PCs idle overnight. Turning it off forces a full shutdown, reducing conflicts.

• Open Control Panel (search in Start menu), then go to Hardware and Sound > Power Options > Choose what the power buttons do.
• Click Change settings that are currently unavailable (requires admin rights).
• Locate Turn on fast startup (recommended) in the Shutdown settings section. Uncheck the box to disable it.

• Click Save changes and restart your PC to ensure a clean boot cycle.
• Test by putting your PC to sleep (Win + L, then sleep) and waking it to check for crashes.

Roll Back Updates (If Needed)

If the Blue Screen of Death (BSOD) started right after installing KB5055523 or another 24H2 patch, the update itself might be the issue. For instance, some users noticed crashes tied to KB5055523’s power management changes on older PCs. Rolling back gives you breathing room to troubleshoot while waiting for Microsoft’s next fix.

Uninstall the recent Windows update:

• Go to Settings > Windows Update > Update history to see recently installed patches.
• Look for KB5055523 or other updates installed when BSODs started.
• In Update history, click Uninstall updates. Find KB5055523 (or the suspect update) in the list, select it, and click Uninstall. Follow the prompts and restart your PC.

Prevent Re-Installation:

• Back in Settings > Windows Update, select Pause updates and choose Pause for 1 week to 4 weeks.
• This stops Windows from reapplying the update automatically.
• Check Microsoft’s KB articles weekly for a fixed version before resuming updates.

Fix 2: Troubleshoot Windows Hello Errors

Windows Hello’s face and fingerprint logins are convenient, but 24H2 bugs can break them, forcing you to type PINs or passwords—annoying when you’re rushing to join a call. These errors often hit laptops or desktops with biometric sensors, leaving users locked out or delayed. Here’s how to restore seamless logins.

Update Windows Hello Components

Windows Hello relies on specific drivers and system files, which can glitch after Windows 11 update changes. For example, a community member found their webcam stopped recognizing their face until they updated its firmware. Ensuring everything is current often resolves login failures.

Install Windows Updates:

• Open Settings > Windows Update and click Check for updates.
• Install all available updates, including Optional updates (click Advanced options > Optional updates).
• These may include biometric or camera driver fixes missed by standard patches.

Update Biometric Drivers:

• Launch Device Manager (Win + X > Device Manager).
• Expand Biometric devices or Cameras, right-click your device (e.g., “Windows Hello Face Sensor” or “Fingerprint Scanner”), and select Update driver > Search automatically.

If no update is found, visit your PC manufacturer’s support site: For Dell, HP, or Lenovo, search “biometric driver [model number]” (e.g., “Dell XPS 13 biometric driver”). Download and install the latest version, then restart.

Verify Camera Settings:

• Go to Settings > Privacy & security > Camera and ensure your webcam is enabled.
• Test it in the Camera app (search in Start menu) to confirm it’s working before resetting Windows Hello.

Reset Windows Hello

If updates don’t help, your Windows Hello setup might be corrupted—say, from a botched Windows update patch. Resetting clears old data and lets you re-register your face or fingerprint, often fixing persistent errors.

Remove Current Setup:

• Navigate to Settings > Accounts > Sign-in options.
• Under Ways to sign in, find Face Recognition or Fingerprint Recognition.
• Click Remove for each affected option.

Reconfigure Windows Hello:

• Click Set up under Face or Fingerprint and follow the on-screen guide.
• For face login, position yourself in good lighting, avoiding shadows or backlights.
• For fingerprints, scan each finger multiple times to capture all angles.

Lock your PC (Win + L) and try logging in with Windows Hello.

Disable DRTM/System Guard (Advanced)

Windows Hello errors often persist on high-security PCs—like business laptops or enthusiast builds—with Dynamic Root of Trust Measurement (DRTM) or System Guard Secure Launch enabled. These features, designed to block rootkits, can conflict with the Windows 11 biometric stack, causing login failures. Disabling them is a last resort but it is effective for many.

• Check your PC’s manual or manufacturer’s site for the BIOS/UEFI key (usually F2, Del, or F10). Restart your PC and press the key repeatedly during boot to enter BIOS.
• Navigate to Security, Boot, or Advanced menus (varies by brand, e.g., Dell calls it “BIOS Setup”).
• Look for options like Dynamic Root of Trust Measurement, System Guard, or Secure Launch.
• Set DRTM or System Guard to Disabled or Off.

Note: If unsure, search online for “[your PC model] disable DRTM” for specific steps.

If prompted, ensure Secure Boot remains enabled unless troubleshooting requires otherwise. Save changes (often F10) and reboot. Reconfigure Windows Hello and test logins.

Again, Corrupted system files can trigger BSODs or Windows Hello failures in 24H2 by disrupting core Windows processes. For instance, a damaged driver file might cause crashes labeled “CRITICAL_PROCESS_DIED.” The System File Checker (SFC) scans and repairs these files, restoring stability.

Sometimes, Windows crashes are tied to outdated apps, like antivirus or VPNs, that conflict with new system files. Check Settings > Apps > Installed apps for apps like Norton or ExpressVPN. Visit their websites to download compatible versions or uninstall if unused.