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...
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...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...
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
hello ok :)
would you like to send me these files :
[2015.09.22 17.16.32 | 000,774,144 | ---- | M] () MD5=9F39DC9027B92456016455A32B68478D -- C:\Windows\Installer\3ef7a91.msi
[2016.06.02 06.48.41 | 002,772,992 | R--- | M] () MD5=557170C4FCC0754B372A5FC174735242 -- C:\Windows\Installer\427ad05.msp
[2016.05.19 05.30.11 | 001,429,504 | R--- | M] () MD5=C233BD1DB45AF8BACD0F3C0D8A646740 -- C:\Wi...
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
I'm surprised cause I only control and read msi files with quickdiag, not .msp files.....
$aList = _FileListToArray(@WindowsDir & "\Installer", "*.msi", 1)
You're the only having this problem, I don't have anymore returns from others users about that ....
Regards
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 |...