
Microsoft's latest Windows 11 update, KB5051987, has introduced significant File Explorer issues affecting users worldwide. This optional update, released as part of the March 2024 Patch Tuesday cycle, was intended to deliver security improvements and bug fixes but has instead caused system instability for many.
Understanding the KB5051987 Update
The KB5051987 update was rolled out on March 12, 2024, as an optional non-security update for Windows 11 versions 22H2 and 23H2. According to Microsoft's official documentation, the update included:
- Security updates for Windows operating system components
- Performance improvements for the Windows kernel
- Fixes for known issues with the Start menu and Taskbar
- Enhancements to Microsoft Defender
However, shortly after installation, users began reporting serious problems with File Explorer functionality.
Reported File Explorer Issues
Multiple users across Microsoft's support forums and social media have documented these recurring problems:
- File Explorer crashes: Frequent and random crashes when browsing folders
- Slow performance: Significant lag when opening folders or accessing files
- Context menu failures: Right-click menus fail to appear or function properly
- Search functionality broken: Inability to search within File Explorer
- Thumbnail display issues: Missing or corrupted file thumbnails
Blue Screen of Death (BSOD) Connections
Perhaps most concerning are reports linking the update to Blue Screen of Death errors, particularly:
CRITICAL_PROCESS_DIED
SYSTEM_SERVICE_EXCEPTION
KERNEL_SECURITY_CHECK_FAILURE
These BSODs appear most frequently when users attempt to:
- Copy or move large numbers of files
- Access network shares
- Use the preview pane in File Explorer
- Attempt to rename multiple files simultaneously
Microsoft's Response
Microsoft has acknowledged the issues in a support document updated on March 15, 2024. The company states:
"We're aware of reports that KB5051987 may cause performance issues with File Explorer and are working on a resolution. Users experiencing these problems may uninstall the update as a temporary workaround."
Step-by-Step User Guidance
For Affected Users
If you're experiencing these issues after installing KB5051987, follow these steps:
-
Uninstall the update:
- Open Settings > Windows Update > Update history
- Click "Uninstall updates"
- Locate KB5051987 in the list and select Uninstall
- Restart your computer -
Temporary File Explorer fixes:
- Reset File Explorer:- Open Task Manager (Ctrl+Shift+Esc)
- Find "Windows Explorer" under Processes
- Right-click and select "Restart"
- Clear File Explorer cache:
- Open Disk Cleanup (search in Start menu)
- Select "Thumbnails" and "Temporary files"
- Click OK to clean
-
Alternative file management:
- Consider using third-party file managers temporarily
- Use Command Prompt or PowerShell for file operations if comfortable
For Users Who Haven't Installed the Update
Microsoft has temporarily paused the automatic rollout of KB5051987. If you see it in Windows Update:
- Home users: Skip this update for now
- Enterprise users: Block the update using WSUS or Intune policies
Technical Analysis
Early investigations by Windows experts suggest the issues may stem from:
- Shell extension conflicts: The update appears to have broken compatibility with certain shell extensions
- Memory management changes: Modified memory handling in the Windows shell components
- Security permission alterations: Stricter security checks causing authentication loops
When to Expect a Fix
Microsoft typically releases out-of-band updates for critical issues within 1-2 weeks. Based on previous patterns:
- Emergency patch likely: Week of March 25-29, 2024
- Included in April Patch Tuesday: If not urgent, April 9, 2024 update
Best Practices Moving Forward
To avoid similar issues in the future:
- Wait before installing: Delay optional updates by 1-2 weeks
- Create restore points: Always create a restore point before updating
- Monitor feedback: Check Microsoft's status page and forums before updating
- Enterprise caution: Test updates in staging environments first
Community Workarounds
The Windows community has developed some temporary solutions:
- Registry edit: Modifying
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions
(advanced users only) - Clean boot: Starting Windows with minimal drivers and programs
- SFC scan: Running
sfc /scannow
in an elevated Command Prompt
Note: These workarounds aren't officially supported and should be used with caution.
Impact on Enterprise Environments
Businesses have reported particular challenges:
- Deployment rollbacks: Many IT departments scrambling to remove the update
- Productivity loss: Significant slowdowns in file operations
- Help desk overload: Increased support tickets related to File Explorer
Microsoft has provided additional guidance for enterprise administrators in KB5051991.
Looking Ahead
This incident highlights the ongoing challenges of Windows as a Service (WaaS) and the importance of:
- More rigorous update testing
- Better communication about known issues
- Faster response times for critical problems
Windows 11 users should monitor Microsoft's official channels for updates on this situation.