{"id":9691,"date":"2019-06-08T14:26:34","date_gmt":"2019-06-08T08:56:34","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=9691"},"modified":"2023-07-31T20:45:40","modified_gmt":"2023-07-31T15:15:40","slug":"fix-slow-right-click-crashes-shell-extensions","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/fix-slow-right-click-crashes-shell-extensions\/","title":{"rendered":"[Fix] Slow Right Click and Crashes Caused by Shell Extensions"},"content":{"rendered":"

When you right-click on a file or folder on some computers, the context menu may take many seconds to appear. This article tells you how to fix the slow right-click issues and other context menu handler shell extension problems in Windows. Here are some of the symptoms you may be facing.<\/p>\n

    \n
  1. On Windows 11, when you open the classic context menu<\/a> by clicking “Show more options”, the “Print” (or “Set as desktop background”) command is shown as the default option (in bold letters). So, double-clicking on image files will either open the Print dialog or set the image file as the desktop background. The ClipChamp<\/a> shell extension causes this issue.<\/li>\n
  2. When you right-click a file\/folder, there may be a huge delay before Windows displays the context menu.<\/li>\n
  3. When you try to empty Recycle Bin, it opens another application instead.<\/li>\n
  4. When you select multiple files, right-click and click Open \/ Print, nothing happens. Whereas it works when a single file is selected.<\/li>\n
  5. Error message “Windows Explorer has encountered a problem and needs to close. We are sorry for the inconvenience” when you right-click a folder.<\/li>\n
  6. Right-click is extremely slow only when the network<\/a> card is enabled.<\/li>\n
  7. When you right-click on a folder and choose Properties, nothing may happen.<\/li>\n
  8. Right-click menu turns ugly (classic look) after installing an older version of Notepad++<\/li>\n
  9. Data Execution Prevention (DEP) error occurs when Windows Explorer or Control Panel is launched.<\/li>\n
  10. Nothing happens when you click Slideshow or Print in the Tasks pane or File Explorer Ribbon.<\/li>\n
  11. When you click “Set up backup” or click “Change settings” in Windows 7 Backup and Restore, nothing happens, or the System32<\/code> folder opens.<\/li>\n
  12. When you right-click Start to access the Win+X (Power User) menu in Windows 10, none of the shortcuts work<\/a>. At the same time, they work correctly from the Win+X shortcuts folder.<\/li>\n
  13. Right-click context menu Run as Administrator not working<\/a>.<\/li>\n
  14. Folder Names Truncated after the Dot (Period) in Explorer<\/a> (caused by TortoiseSVN<\/code> shell extension)<\/li>\n
  15. A vertical scroll bar appears in Windows 11 fast context menu<\/a>; a gap appears at the bottom of the menu. This happens when text size\/scaling is increased.
    \n\"scroll
    \n(A redditor has indicated that disabling “NVidia CPL Context menu extension” using ShellExView has solved the context menu issue.)<\/em><\/li>\n
  16. ESET NOD32 Antivirus context menu breaks the Windows 11 fast context menu. A portion of the menu is cut off.
    \n\"eset
    \nWorkaround: Disable the “Integrate into the context menu” option in ESET NOD32 \u2192 Advanced Setup \u2192 User Interface \u2192 “User Interface Elements” section. ESET support says this issue has been resolved in the Windows 11 Insider Builds. (Ref: ESET forum posts     #1<\/a> and #2<\/a>)<\/em>\n<\/li>\n
  17. Whenever you open up File Explorer, right-click on a file or folder, or copy and paste a file within File Explorer, you may see a pop-up window with the error message: “Failed to load resource DLL.<\/strong>”
    \nThe Ipswitch WS_FTP shell extension causes this error on some systems<\/em><\/li>\n<\/ol>\n

    Cause<\/h2>\n

    A poorly coded context menu handler shell extension added by a 3rd party program may be causing any of the above symptoms.<\/p>\n

    A context menu handler is a type of shell extension that adds commands to your right-click menu. For example, the entries “Scan with Windows Defender,” “Set as Desktop Background,” etc., you see in the right-click menu are context menu handers included by default in Windows. Likewise, 3rd party programs may add their own extensions.<\/em><\/p>\n

    When Explorer shell crashes, it writes an entry to the Application event log. You can open the Event Viewer and check for recent Application log errors 1000<\/code> to find more information about the crash.<\/p>\n

    In some cases, the exact name of the offending shell extension is shown in the Application event log. Here is an example:<\/p>\n

    Log Name: Application\nSource: Application Error\nDate:\u00a0\nEvent ID: 1000\nTask Category: (100)\nLevel: Error\nKeywords: Classic\nUser: N\/A\nComputer:\u00a0\nDescription:\nFaulting application name: explorer.exe, version: 10.0.10240.16405, time stamp: 0x55b455cf\nFaulting module name: IDTNCPL.cpl<\/strong>, version: 1.0.6365.0, time stamp: 0x4e68a44d\nException code: 0xc0000005\nFault offset: 0x00001151\nFaulting process id: 0x1284\nFaulting application start time: 0x01d0d2a6d2ff07fc\nFaulting application path: C:\\WINDOWS\\explorer.exe\nFaulting module path: C:\\WINDOWS\\system32\\IDTNCPL.cpl\nReport Id: 1da3cf69-34ba-4871-bb74-5bbaa97e8eb0\n\n<\/pre>\n
    Here is another instance where the Foxit PhantomPDF’s shell extension ConvertToPDFShellExtension_x64.dll<\/code> caused the crash.<\/p>\n
    \"context<\/p>\n
    However, in some cases, the module name may show up as shell32.dll<\/code> instead of the actual 3rd party module that caused the issue.<\/p>\n
    \n
    \n
    Contents<\/strong><\/p>\n
      \n
    1. Use ShellExView to resolve shell extension problems<\/a>\n