Search

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 :)

Ok I modified and updated it

Logically , theses files are bypassed ( even if you change thier name or their extension ^^ )

Regards

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 , 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...

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 :)

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