Search

Adwcleaner removed the spyware/addware i had. Very impressed and would like to thank you for a wonderful product. Is there a pro version that updates itself?.

Thanks

hello :)

very fun :) you'll see in the "Extended" Scan there' s a lot of informations more about the system

I add them since 3 days and it's not finished :)

good way , Regards

g3n-h@ckm@n

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!

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

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