Bug-High CPU Present in Windows 11 22H2, Microsoft Provides Solution


Bug-High CPU Present in Windows 11 22H2, Microsoft Provides Solution


Microsoft has given an important announcement for us Windows 11 users, where they have just analyzed and got a new High CPU Bug in the Windows 11 operating system. As a result, the performance of File Explorer experiences a slight interruption which causes excessive CPU users.

Windows 11 had previously experienced some of the same information, where yesterday it was obtained by NVIDIA users who reported that their CPU and GPU consumption increased even though they were not opening any applications.

This happens again but now in File Explorer, Windows 11 users get a workload that is more on the CPU when accessing File Explorer. Regarding this, Microsoft finally confirmed that this is a bug that is present in their CPU.

This bug will be obtained by users who update to the KB5026373 version provided by Microsoft last May. According to the company, this is due to Access to Advanced Security Settings which shares the FIles and Folders dialogs.

After installing updates released on May 9, 2023, or later updates, you might be unable to view Effective Access in the “Advanced Security Settings” dialog for shared files or folders. On affected devices, when the “View effective access” button is selected, you will receive the message “Computing effective access….” but the results of the query might not be displayed and explorer.exe might continue to use CPU after the Advanced Security settings dialog is closed. This issue is unlikely to be experienced by consumers using Windows devices in their homes.

So what is the solution provided by Microsoft to overcome this one problem? The company has provided a first step to overcome this problem, where you only need to reboot from the Windows 11 system.

If you still get the same problem, then you have to access the connected Microsoft Account then Sign Out. After that, Restart and re-enter or Sign In using your account earlier, it's done, it's easy, isn't it?

Meanwhile, most likely this issue will be fixed by Microsoft through the next update.