Microsoft Fixes Windows Bug Causing File Explorer Freezes

Cyber Security Threat Summary:
“Microsoft has resolved a Windows bug that was causing freezes in the File Explorer application. The issue primarily affected non-consumer environments and was observed in Windows 11 21H2/22H2 and Windows Server 2022. Users experienced freezes in File Explorer after installing Windows updates released since May 9th, 2023. Microsoft released an optional cumulative update (KB5027303) this month to address the issue for Windows 11 22H2 users, with a plan to make it available to all affected Windows users in the July Patch Tuesday cumulative updates. A workaround is also provided, advising affected users to reboot their systems or sign out. Another bug related to intermittent failures when saving and copying files on Windows 11 22H2 systems was addressed in a recent cumulative update (KB5027231)” (BleepingComputer, 2023). Security Officer Comments:
This Windows bug that’s causing the File Explorer to freeze has been a significant concern for non-consumer environments. Microsoft's timely release of the optional cumulative update for Windows 11 22H2 users demonstrates their commitment to addressing the issue. The provided workaround and plans to release updates for other affected Windows versions indicate that Microsoft is actively working to resolve the bug for all affected users. However, it is essential to note that the impact on individual users using Windows devices at home is expected to be minimal. Suggested Correction(s):
For users affected by the File Explorer freeze bug in Windows 11 21H2 and Windows Server 2022, Microsoft suggests two mitigation options:

  • Restarting the device or signing out for the affected user. These actions can help alleviate the issue.
  • Additionally, Microsoft has released an optional cumulative update (KB5027303) for Windows 11 22H2 users, which provides a permanent solution. Users should also ensure they install the upcoming July Patch Tuesday cumulative updates, which will include the fix for this bug.
Link(s):
https://www.bleepingcomputer.com/