Microsoft recently released the official version of Windows 11 for some eligible devices, but it seems to have brought with it some serious performance issues, with some users observing incredibly high memory usage. AMD has confirmed that some of the performance issues were caused by new security features in Windows 11. Now, another problem with file explorer is becoming apparent.
Many users feedback, Win11 occupies a very high memory usage, which makes the performance of the entire device affected, the game frame rate is also significantly decreased. And this problem, seems to be caused by the Win11 file Explorer (Explorer. Exe).
In Win11, file explorer retains a lot of the design of Win10, but in fact it is based on the new WinUI production, so it brings new ICONS, modern controls, buttons and other visual adjustment functions, visual effects are also more using Mica materials. In addition, the Right-click menu in Explorer uses the new Fluent Design language to work with the rest of the operating system.
However, this new version of the resource manager results in excessive memory usage. Task Manager is reportedly listed as "task Manager". Explorer.exe " The process causes resource peaks of 70-99%, and in some cases calls to the processor constantly. Each time file Explorer is opened, the memory usage of file Explorer increases.
What's even more annoying is that the problem was reported last month in the Windows Insiders test channel, but the reports seemed to have been ignored, leaving the File Explorer memory leak open even after the Windows 11 launch.
However, Microsoft seems to be following up on the issue. In a Feedback Hub post at the end of last month, Microsoft noted that they had "made a point of saying that... Changes are included in Build 22454 to alleviate several issues that cause leaks when using File Explorer." . This means that Microsoft has found a fix, but for now users need to join the Dev channel to update the fix, and regular users will have to wait a few weeks.
Microsoft has been testing the fix for more than a month and may soon be releasing it as a separate patch, but hopefully it won't cause any additional problems.