GP SoftwareTwitter
Opus FAQsManualCommandsObjects

Crashes and hangs in Windows 10 Creators update

Since my system updated itself to Windows 10 Creator Update (Build 15063) I found that Directory Opus (version 12.4) crashes/hangs frequently. Here is the latest error report: -

Directory Opus

Stopped responding and was closed

‎22/‎04/‎2017 10:04

Report sent

A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\GPSoftware\Directory Opus\dopus.exe

Problem signature
Problem Event Name: AppHangB1
Application Name: dopus.exe
Application Version:
Application Timestamp: 58d0c702
Hang Signature: 310f
Hang Type: 134217728
OS Version: 10.0.15063.
Locale ID: 2057
Additional Hang Signature 1: 310f703cf7ea5de2011ef2d76935a31a
Additional Hang Signature 2: 68e3
Additional Hang Signature 3: 68e3aff2a73a71956033271ace48bd0f
Additional Hang Signature 4: 310f
Additional Hang Signature 5: 310f703cf7ea5de2011ef2d76935a31a
Additional Hang Signature 6: 68e3
Additional Hang Signature 7: 68e3aff2a73a71956033271ace48bd0f

Extra information about the problem
Bucket ID: 07b562d1d1cebbeaac0588c18a4bbce6 (129404258541)

Can you please help me with this issue?

Please send any crash dumps and we may be able to see where the crash is happening, and if it's in Opus itself or another component:

These guides may also help troubleshoot things:

I have done as you suggested but found no *.dmp files anywhere on my PC

That rules out using crash dumps. The other guides are your best bet, in that case.

If you can work out a likely cause of the crash (e.g. a sequence of operations) then we can try the same here to see if it happens for us as well.

Crashes are often caused by shell extensions and other add-on components which may be unique to your machine. If that is the case then we may not see the same thing, but the guides include suggestions on tracking down the problem component.

If network folders are involved, let me know as there is something currently under investigation with network folders and the Win10 Creators Update, although it may turn out to be nothing.

Major updates like "Creators Update" fully reinstall Windows remembering most settings and apps. Sometimes you won't run into trouble, but often you will. I always try out first the update and then do a fresh install on new Windows releases.

I have now completed my investigative work and discovered that there appears to be incompatibility between Directory Opus and an update to from Acronis TI Home 2016 to Acronis TI Home 2017. I have completely removed my Acronis software and, as yet, the problem has not reappeared. I will wait a few days to verify my hypothesis and will then tale appropriate action.

Many thanks for your suggestions which have guided me down a helpful analytical direction.

That sounds like progress.

While the main program and functionality of Acronis TrueImage has never caused a known proble, the shell extensions it installs have been known to cause some problems on & off over the years.

So you may be able to reinstall TrueImage and still use it with just the shell extensions disabled (either system-wide, using ShellExView, or just in Opus using the ignore_context_menus setting).

Disabling the shell extensions will lose things like some right-click menu options for TI backup files, but nothing vital (at least from my knowledge of older versions of TI). The main program is independent of them and everything can still be done via its UI.

Please let us know how things get on, as it may make sense to add mitigations to Opus to avoid these particular extensions from causing crashes. (In fact, we had them blocked in Opus by default for some time, but unblocked them late in Opus 11's lifecycle as they seemed stable again.)

The guides on right-click crashes and shell extensions which may cause problems have the IDs of the TI extensions for easy pasting, but it's also worth checking with ShellExView in case the IDs have changed in the newer version. Links to ShellExView and other details are in the two guides.