I received an integrity check failure today. The installer's digital signature was fine, as was the dopus.exe file.
The digital signature for dopuslib.dll was invalid. Virus/trojan scans by two commercial antivirus programs did not turn up anything.
I reinstalled DO and it works fine now. I am attaching a copies of the corrupt dopuslib.dll file and the replacement dopuslib.dll file. I had to change the extension from "dll" to "dop" in order to upload them.
Both files are the same size. I would like to know what is different in the corrupt file and what might have caused the change.
Looks like random corruption in part of the file, most likely caused by failing storage hardware. or possibly by overclocked/overheating/failing CPU or RAM hardware.
If you see any other strange crashes or bugs in programs, I would suspect other files on the drive may have random changes in them as well. The changes in this file would have caused some weird behavior had the program not checked itself and allowed you to run with that version of the file, and most software doesn't check itself, so there may be some other surprises lurking on the system.
But it does not look like anything malicious, like a virus, since the changes would just make things not work, rather than make things work differently. (At least that I have noticed. They could throw in some random changes to make a malicious change harder to notice, but I doubt it, as it'd also make you more likely to notice something is wrong. Macilious changes usually want to remain hidden and undetected as long as possible.)
You can use a tool like CrystalDiskInfo to check your storage hardware's SMART parameters, which may indicate if the hardware is failing.
I agree with Leo, it looks like a hardware issue. I would check memory first, Windows has a built in memory check external link.
When did you install DOpus the first time? I would only expect this to happen when the file was being written, and once its installed I cant think of why it would get re written. Wondering how long the installed file was sitting there before it became corrupted.
DO 12.7 was installed on 12/02/17. It was installed over DO 11 (which was installed 12/11/14). The integrity check failure did not appear until 12/22/17.
