Windows 11 is hit by slow File Explorer and context menu bug

Windows 11 slow Explorer

Windows 11 started rolling out on October 5 and it comes with
several known issues, mostly linked to the printing service.

As we reported earlier, Microsoft has confirmed and offered a
fix for performance issues experienced on AMD devices running
the most recent version of Windows 11. Additionally, Microsoft
has also confirmed reports of high memory usage caused by
Explorer.exe (File Explorer).

It turns out that Windows 11 has another bug that slows down
the performance of the context menu. This bug appears to be
related to the changes made to File Explorer and the context
menu – but the good news is that a fix has been developed and
it is currently being tested with Insiders.

As you may be aware, File Explorer has been updated with a
fresh design on Windows 11 and it also comes with a new command
bar which refers to the header or action bar that appears when
you open Explorer. The command bar is similar to the ribbon
menu and it contains your customization settings/options.

Windows 11’s command bar replaces the traditional ribbon and it
also adds support for a modern context menu.

The modern context menu, which works very well on touch
devices, has a bug that causes a delay when you right-click
anywhere on the desktop or Explorer. The delay is more
noticeable on low-end devices or when the system is easy and
some users have been able to fix it by restarting the
Explorer.exe.

Thankfully, Microsoft has confirmed that it’s working on
performance improvements for the context menu and
Build 22478 includes a change that would improve context
menu launch performance.

Microsoft has also made a few changes to improve explorer.exe
reliability and reduce crashes when using File Explorer. A bug
that could crash explorer.exe when using the Desktops flyout
context menu is also getting a fix, and another crash bug that
occurred when dismissing the desktop flyout will be fixed as
well.

About the Author: admin

i am as a writer and blogger...

Leave a Reply

Your email address will not be published. Required fields are marked *