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

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

Bonjour,

Je suis tout nouveau et vient d'installer adwcleaner,apres l'analyse dans registre il me sort 4 lignes qui sont

pouvez vous me dire si je peut les nettoyer ou  si je peut les suprimer Merci.

# AdwCleaner v5.200 - Rapport créé le 27/06/2016 à 13:04:57
# Mis à jour le 14/06/2016 par ToolsLib
# Base de données : 2016-06-26.1 [Serveur]
# Système d'exploitation : Windows 8.1  (X64)
# No...

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

Bonjour.

Depuis plusieurs mois, à chauqe mise en route de l'ordi (qui fonctionne très bien par ailleurs) j'ai toujours la même faute qui se produit

Nom d’événement du problème : APPCRASH

Nom de l’application:                      lpksetup.exe

Version de l’application:                  6.1.7601.17514

Horodatage de l’application:          4ce7a1f7

Nom du module par défaut:           msvcrt....

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

[Deleted duplicate post]