Crash, exit or high CPU when right-clicking certain files

Frequently asked questions.
User avatar
Posts: 36498
Joined: 07 Nov 2004, 01:30
OS: Windows 10 64-bit
Opus: Directory Opus 12
Location: London, UK
See also:

This FAQ helps if Directory Opus crashes, exits or uses high CPU when you open the right-click context menu for a certain file or certain types of files. These problems are usually caused by bugs in 3rd party components and this FAQ contains steps for finding and disabling the faulty component.

Known Issues:

  • See also: Shell extensions which are blocked by default.

  • Notepad++:

    Several people have reported crashes when right-clicking files with older versions of Notepad++ installed. If you have Notepad++ and are experiencing these problems upgrading to the latest version of Notepad++ may solve them, and is definitely the first thing you should try.

  • Acronis True Image:

    Some versions of True Image have had shell extensions which trigger crashes or large memory leaks in Opus (sometimes Explorer as well). As far as we are aware, current versions are OK, but if you have TI installed and are experiencing problems, you might want to try blocking its extensions to quickly rule them out, after verifying that you have the latest TI update installed. You can use ShellExView to fully block the extensions, or add the following CLSIDs to ignore_context_menus (more detail in the main FAQ below) to partially block them:

    Code: Select all


  • NOD32:

    The context menu added by NOD32 antivirus (version 8.x.x.x) does not crash but may add quite a bit of delay (about 1 second) to context menu opening, in both Opus and Explorer. If you're seeing this and have NOD32 installed, try disabling its context menu via NOD32's Advanced Settings window, under User Interface.

  • Older issues:

    Most other known conflicts have been addressed by fixes & workarounds in Opus & the extensions themselves, or by newer versions of Opus automatically blocking certain extensions. However, old issues may still affect you if you are using a old versions of Opus or old versions of other software. Details on some of these issues have been moved into the reply to this post, below.


Main Information:

If you experience crashes, apparently spontaneous exits, or high CPU usage when you open the right-click context menu for a specific file, or types of files, within Directory Opus then the problem is almost certainly caused by a bad Send To shortcut or a bad context menu extension.

Send To Shortcuts:

If your context menus work but take a long time to open, it may be because of something in your Send To sub-menu. For example, shortcuts pointing to unavailable network paths may cause a 30 second delay on the menu opening.

As of Opus, the Send To sub-menu is only built when you actually open it, not when its parent menu opens, so this should be less of a problem and it should be easier to tell where the problem is.

If you think there is a problem with your Send To menu, try right-clicking the same files/folders in Windows Explorer and see if opening the Send To sub-menu there triggers the same problem.

Context Menu Extensions:

Problematic extensions usually have problems because they assume they are always being hosted inside Windows Explorer and go wrong within Directory Opus.

  1. Extremely Quick Fix

    If you need the crash fixed immediately you can usually just turn on:

    Preferences, Miscellaneous, Windows Integration, Hide Windows items on file context menus (shift overrides).

    This option removes non-Opus items from the right-click context menus within Opus. The removed items include those added by Windows Explorer as well as those added by 3rd party context menu extensions.

    With the option enabled you can still hold shift when right-clicking a file to see the full context menu. You can also specifically add back certain items as explained in this tip, and the advantage of that is you can both organise what you want on the menu (so it's no longer a randomly-arranged mess) and get rid of what you don't want (so there's less to look through and it takes less time to build the menu the first time).

    Even if you're happy at this stage it's in everyone's interests to track down what was causing the crash so that the problem can be fixed or worked around.

  2. Finding The Culprit

    When you're ready to look for the cause of the crash, turn off the Hide Windows items on file context menus option mentioned above.

    Verify that you can still reproduce the crash, so you know you're not about to waste your time looking for a crash that no longer happens.

    Go to Preferences - Miscellaneous - Advanced and turn on context_menu_debug. (You do not need to exit or restart Opus for the change to take effect.)

    Download the small DebugView tool from Microsoft and run it. If you see an error message about extracting Dbgv.sys you can ignore it as we are not interested in debugging device drivers.

    DebugView will now display messages from Opus when you right-click on files. (Note that other programs may also send messages to DebugView and not everything that you see printed by the program comes from Opus.)

    If you now right-click the offending file in Opus, you should see information in DebugView with various CLSID numbers, and sometimes names, representing the context menu extensions that Opus is talking to. For example:

    Code: Select all

    CLSID: {8DD448E6-C188-4aed-AF92-44956194EB1F}
           (WMP Burn Audio CD Launcher)
    CLSID: {7850a720-705f-11d0-a9eb-0080488625e5}
           (BestCrypt Shell Extension)
    CLSID: {8D9D4D0D-FDDD-44CB-AAB2-6161FA0757C5}
           (IZArc Shell Context Menu)
    CLSID: {B089FE88-FB52-11d3-BDF1-0050DA34150D}
           (NOD32 Context Menu Shell Extension)
    CLSID: {750fdf0e-2a26-11d1-a3ea-080036587f03}
           (Offline Files Menu)
    CLSID: {A470F8CF-A1E8-4f65-8335-227475AA5C46}
           (Encryption Context Menu)
    CLSID: {E9FE4040-3C93-11D4-8006-00201860E88A}
           (Directory Opus Context Menu)
    CLSID: {906b0e6e-61ce-11d3-8ee2-0060080a7242}
           (QuickSFV Shell Extension)
    CLSID: {2F25CF20-C569-11D1-B94C-00608CB45480}
    CLSID: {4E716236-AA30-4C65-B225-D68BBA81E9C2}
           (WinMergeShell Class)
    CLSID: {969223c0-26aa-11d0-90ee-444553540000}
           (PGP Shell Extension)
    CLSID: {a2a9545d-a0c2-42b4-9708-a0b2badd77c8}
           (Start Menu Pin)
    CLSID: {FFB699E0-306A-11d3-8BD1-00104B6F7516}
           (NVIDIA CPL Extension)
    CLSID: {F1B9284F-E9DC-4e68-9D7E-42362A59F0FD}
           (WMP Add To Playlist Launcher)
    CLSID: {CE3FB1D1-02AE-4a5f-A6E9-D9F1B4073E6C}
           (WMP Play As Playlist Launcher)
    CLSID: {6B28C27B-8A75-4DB1-A08A-86C8CCEC3AF3}

    The cause of the crash is likely to be the last item that you see printed before the crash. If you're lucky Opus will have told you the name of the extension. If you only see a CLSID number then you'll have to search Google or search through the registry for the CLSID string (just the part between the curly braces) to see if you can find some clues (which is usually quicker and easier than it might sound).

    Having found the culprit you can now turn off the context_menu_debug mode via Preferences. (You can leave it on all the time, but it will slow things down a bit.)

  3. Disabling A Specific Extension

    You can instruct Opus to ignore a specific context menu extension if you've found one which is causing problems.

    Go to Preferences - Miscellaneous - Advanced and double-click the ignore_context_menus setting. A small window will appear into which you should paste the CLSID values, including curly braces, of the extension(s) you want to exclude, one CLSID per line.

    opus_ignore_context_menus_example.png (81.2 KiB) Viewed 9693 times

    Alternatively, you can use the 3rd party ShellExView tool to disable extensions, but this will also disable them in Windows Explorer, File Open dialog boxes, and so on.

    The context menu extension should no longer bother you. The next thing to do is report the problem so it can be investigated and then fixed or worked around properly for everyone.

  4. Reporting The Problem

    It is in everyone's interests for the problem to be reported so that it doesn't occur on other people's computers and also so that you can get your context menu handler back again, assuming it's one you wish to use.

    If you track down your problem to a particular context menu extension then please report it here at the forum (as well as the extension's author if applicable) so that the bug can be fixed or worked around. Even in the past when the problem has turned out to be within 3rd party extensions that GPSoftware has no control over it has still been possible to add code to Opus which works around the problem, sometimes by detecting the specific extension, so that the crash no longer happens.

  5. Crash dump investigation

    If you cannot find the cause using the methods above, and the problem is a full crash, then there should be a crash dump corresponding to the time of each crash.

    We'll only look at crash dumps from people with linked accounts. Please start a thread if you wish to send them to us, with details of what's going wrong and what you have tried already, and we can advise further.

  6. Further Information

User avatar
Posts: 36498
Joined: 07 Nov 2004, 01:30
OS: Windows 10 64-bit
Opus: Directory Opus 12
Location: London, UK

Postby leo » 10 Aug 2015, 00:42

Old known issues

This information was originally part of the Known Issues list in the post above, but is likely to only be useful to people using older versions of Opus or the other software involved. The information has been kept in case it is useful, but moved here to reduce the noise in the post above.

  • Bitcasa Cloud Storage:

    This context menu shell extension has triggered problems for several people and is blocked by default in newer versions of Opus. In older versions, you can disable it within Opus by adding the following CLSID to the ignore_context_menus setting mentioned and shown in the screenshot below:

    Code: Select all


    If you still get crashes when right-clicking drives (as opposed to files and folders) then you may need to use ShellExView to disable the extension system-wide. This may also apply with current versions of Opus.

  • Quick PDF Tools Pro:

    If you have Quick PDF Tools Pro (version, as of August 2012) installed you may experience long delays and high CPU usage when right-clicking files in Opus.

    A workaround for the problem was added to Directory Opus and later versions (more detail). Users on older versions of Opus may wish to disable the menu by adding the following CLSID to the ignore_context_menus setting:

    Code: Select all


    (Once you update to Opus or above, you can remove the CLSID again and you should be able to use Quick PDF Tools again in Opus without problems.)

  • Qualcomm Atheros Bluetooth Suite:

    This installs a shell extension which triggered crashes for several people. It is automatically blacklisted by Opus and above. Users on older versions can disable by adding the following CLSID to the ignore_context_menus setting:

    Code: Select all


    (The shell extension appears to create its own background threads and windows when files are right-clicked, then falls over if the extension is unloaded while those threads/windows still exist. The COM object's name (shown in the debug output) is the generic-looking AppShellPage Class, and the associated DLL is C:\Program Files\Bluetooth Suite\BtvAppExt.dll.)

  • CFi ShellToys - Image Resize menu (and possibly other shell extensions that add owner-draw menu items):

    This has been fixed in Opus In older versions, the menu may cause Opus to crash. This is not the fault of CFi ShellToys; it just happens to be good at triggering a bug in older versions of Opus.

  • O&O Defrag:

    If you have an old (< 19th May 2009) O&O Defrag installed and you find that Opus exits or crashes when you right-click things, updating to the latest version of O&O Defrag should fix the problem.

Return to “Directory Opus FAQs”