Hello!
Great news! Finally, I can now confirm that QuickDiag works perfectly, from start to finish, and without error messages! Yay!
Just before QuickDiag finished, I got a popup asking me if I would let QuickDiag communicate on my local network through the Windows Firewall; I answered Yes, and the program finished with creating its log file on my Desktop.
So, once again;
Thank you for Quic...
Hello!
Thank you for updating QuickDiag, however the same error still persists.
Both of these files belong to the backup and disk imaging program Acronis True Image 2016.
It is a comprehensive program with a ton of features, and therefore its files take up the biggest amount of disk space of all my software.
Please let me know what more I can do to help.
Regards,
midimusicman79
Hello!
Thank you for updating QuickDiag!
The signers of these files are as follows:
aaf275.msi -- Acronis International GmbH and Symantec Class 3 SHA256 Code Signing CA
ab11370.msi -- Acronis International GmbH and Symantec Class 3 SHA256 Code Signing CA
Thank you!
Regards,
midimusicman79
Hello!
Thank you for fixing the bug and updating QuickDiag; I can confirm that it does jump over the corrupted files, however now QuickDiag hangs at another file: C:\Windows\Installer\a0884cd.msi
This is the error message: "Error allocating memory".
Following the pattern from before, the actual error files would be these: C:\Windows\Installer\aaf275.msi and ab11370.msi
Here is the log ex...
Hello!
I am Norwegian, so English is not my first language either.
Done; wininst2.zip
Thank you!
Regards,
midimusicman79
Hello!
Thank you for studying them, and for confirming that the problem lies in the file named 5f6db.msi itself and not QuickDiag.
As it happens, I also have another file named 9acb635.msi, which is equal in date/time, size and MD5, which also is corrupt.
[2015.05.08 07.17.50 | 010,526,720 | ---- | M] () MD5=B3315DBDB28BD24D3AA4AC70566DCECB -- C:\Windows\Installer\5f6db.msi
[2015.05.08 ...
Hello!
Done; wininsta.zip
Thank you!
Regards,
midimusicman79
Hello!
Well, like I mentioned before, I was not sure if this was the right file, so in that case, the right file would be this: 5f6db.msi in stead.
However, this file does not have any signers. I tried to run it, but it would not run either, so it appears to be broken.
He...
Hello!
The problem still persists; now it is on line 7975.
I am sorry I forgot to include the MD5 for the above mentioned file, so I thought I should run a script with OldTimer's List-It (OTL) in order to provide you with MD5 for all the *.mp* files in the said folder, here it is:
========== Custom Scans ==========
< C:\Windows\Installer\*.ms* /md5 >
[2015.03.17 10.48.34 | 002,800,128 |...
Hello!
The error still persists; now it is on line 7973.
C:\Windows\Installer>dir *.ms*
Volume in drive C has no label.
Volume Serial Number is FE77-E905
Directory of C:\Windows\Installer
17.03.2015 10.48 2 800 128 1044ee.msi
04.01.2016 22.49 10 543 616 1437df.msi
26.01.2016 16.11 4 792 320 152fb33b.msi
04.01.2016 22.49 10 543 616 16fa80.msi
26.07....
