I don't know if @Leo or anyone else could come up with a better idea, but what I would do is to try and use process monitor (Process Monitor - Sysinternals | Microsoft Learn) having it tracking opus.exe (e.g. in the filter window that pops up at procmon startup, add "Process Name" is "dopus.exe").
Then see what are the operations going on when it crashes.
This was never explicitly answered, but if that's the case, it could be a byproduct of the dodgy patch. I doubt the issue lies in their config, it's more likely due to the way this was implemented (other files placed somewhere doing nasty things, etc)
Did you copy anything to the DOpus program files folder or somewhere else if you indeed previously used a pirated version?
I'm not sure if it was a dodgy/pirated verson of DOpus 13.7, but I indeed downloaded from a third party site. It was working fine and, because of that and because I liked the program, I decided to update to version 13.10 and buy a license. When I clicked on vs. 13.10 installer, it installed automatically. Then it stopped working fine. Is the crash probably caused by the first install? So, the problem remains: What should I do to completely clean any installation as well as any windows corrupted registry key? I think the solution to my problem has to do with this registry cleaning.
errante, I cleaned all DOpus directory among several installations. I am sure I didn't let any file or archive in directory <C:\Program Files\GPSoftware\Directory Opus> prior to the last installation.
- Did you install your certificate? One idea, but maybe just the trial license expired and the fact that the license manager is displayed is off-putting for some reason to a poor designed antivirus. Doesn't hurt to try install your certificate from command line.
- If you used a pirated version, and copied some files somewhere, probably that's the cause. I doubt about some registry entries.
If you've installed a pirate version from a dodgy source, all bets are off. The entire machine could be compromised and misbehaving as a result, depending on what that dodgy installer did while it was given admin rights.
answer 1: I didn't let the trial license expire. As we speak, I still am able to use DOpus in trial mode. Tomorrow is the final day. From Monday on, only with the certificate installed. And, btw, I use Kaspersky AV, witch I think it's effective.
answer 2: The files were copied in default directory, as I stated in my last message.
I'm a PC heavy user and, so far, no other program or windows itself misbehaved after using the dodgy version of DOpus. I'll quit using DOpus in this PC, as I can't fix this nasty issue. Thanks to all that spent some time trying to help me.
Hi, guys.... great news!!! I tried restoring my system to a date prior to DOpus installation, and started doing so. After some time, it rebooted and FAILED to restore to an old date, but, somehow, It showed the first installation of DOpus (vs. 13.7). Then I completely uninstalled this version, rebooted windows once more, installed v. 13.10 from official installer and... voilá!!! it's working perfectly. Including some customized config that I saved before. I hope this thread helps someone in case he/she may face the same issue. Thank you all, folks!
1 Like
I would be reinstalling the whole machine at this point. Too many strange errors and OS-level problems to trust it, especially if software from unknown sources has been used on it previously.
1 Like