Computers & Laptops | June 30, 2023
Windows 11 is undoubtedly the star of Microsoft. After leaving Windows 10 behind, the company’s new operating system promises to occupy the computers of many people for many years. However, it is not without flaws, like its predecessor. The latest flaw, caused by an update, can make the computer run slower than usual due to a system issue.
According to Microsoft itself, updates released starting from May 9th have caused a problem where CPU usage increases. The issue is centered around the Windows File Explorer and has been caused by the KB5026372 update, potentially greatly impacting the system’s performance.
Microsoft explains that the problem occurs when trying to verify effective access permissions from the “Advanced Security Settings” dialog for shared files and folders. This dialog is responsible for causing the File Explorer to continuously request resources from the processor.
In the words of the Redmond-based company, the flaw could cause the user to “be unable to see effective access in the Advanced Security Settings dialog for shared files or folders. On affected devices, when you select the View effective access button, you’ll receive the message Computing effective access.”
The company further states, “The query results may not be displayed, and explorer.exe may continue to use the CPU,” even after closing the Advanced Security Settings dialog. “It is unlikely that consumers using Windows devices at home will experience this issue,” the statement reads.
Thus, this problem affects networked computers more than personal devices because it specifically involves shared files or folders. Fortunately, the solution to the problem is simple; restarting the computer or logging out will be sufficient to reset the CPU usage and prevent the problem from reoccurring. The error affects all versions of Windows 11 (both 21H2 and 22H2), as well as devices running Windows Server 2022.
If, by any chance, this error is causing you headaches and you don’t want to keep restarting your PC, we have good news. Microsoft has promised that they are working to resolve this issue and plan to release a permanent solution by the end of this month, June.
