Microsoft has fixed a known problem that caused File Explorer to crash when viewing a file’s effective access permissions on Windows 11 and Windows Server systems.
Users of affected devices may see a message that states “Computing effective access….” without displaying the query results when they click the “View effective access” button under Properties > Advanced to check the effective permissions of a shared file or folder.
Additionally, even after closing the Advanced Security settings dialog, the explorer.exe process will continue to consume CPU resources, resulting in File Explorer freezes.
It’s important to remember that this problem only occurs in non-consumer settings and won’t affect home users of Windows devices.
Systems running the most recent versions of Windows, such as Windows Server 2022 and Windows 11 21H2/22H2, are affected by the known issue. As per Microsoft, clients will encounter Pilgrim freezes subsequent to introducing Windows refreshes delivered since May ninth, 2023.
Microsoft tended to it on Tuesday for Windows 11 22H2 clients with the arrival of the current month’s discretionary aggregate update (KB5027303), and it will be made commonly accessible to all impacted Windows clients with the arrival of July Fix Tuesday combined refreshes.
“File Explorer is impacted by this update, which addresses a problem. It could stop responding for good. Microsoft explained, “This occurs after you attempt to view the effective access permissions for files in File Explorer.”
On the Windows release health tracker, the company added, “This issue will be resolved on other affected Windows versions in updates that will be released in the near term.”
Workaround available for users still affected by this bug
Additionally, Redmond offers users of Windows 11 21H2 and Windows Server 2022 who are affected by this known issue a workaround that instructs them to either sign out or reboot their systems.
According to Microsoft’s statement, “If you have attempted to view effective access, you can mitigate the CPU usage issue by restarting your device or by signing out for the affected user.”
Fourteen days prior, the organization likewise tended to a Windows 11 bug setting off discontinuous disappointments while saving and replicating records on Windows 11 22H2 frameworks.