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
I don't understang why these files are so big.....
I updated just now , reading only the first 32 digits of msi files instead of 64, maybe It'll be more easy for Quickdiag to scan these files
Say to me what it does.
Regards
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 , 330~500 Mo !!!! it's an entire program lol !!!
can you see the signers of these files ?
Regards
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...
Hi :)
studying your files gave me an idea (reading the offstes) and it helped me and now the bug is fixed and I thank you again
henceforth QuickDiag will jump over the corrupted files
Regards :)
Hello thanks ;)
the files are , like I thougt , exactly the same.
the content of them is 10 280 Ko of zeros , just full of empty space , nothing else :D
Regards :)
Happy for you :)
if you move them in another folder you'll be able to finish the diag in a good way :) ( quickdiag analyses the msi files only in this folder ( Installer ) , you can for example create a folder in C:\Windows\Installer with the name you want and put these files to keep them not so far and do again a scan with quickdiag , I think it'll go 'till the end :)
sorry for my english bu...
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 ...
ok I studied them
you can delete 5f6db.msi, the package is corrupted , It won't never work anymore.
QuickDiag gave me the same message than it gave to you at the same moment , on the same file.
I tried to install it and Windows returned me an error message
all the msi files are signed and this not.
Regards
