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 ...
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!
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 |...
Hi, Think this is it. If not let me know thanks. Debug report and also the report that showed the infected files
Thanks for your assistance
2016-06-23 01:20:36 : [Notice] Running from C:\AdwCleaner 2016-06-23 01:20:36 : [Notice] Scan started 2016-06-23 01:20:36 : [Success] Internet connection is UP 2016-06-23 01:20:37 : [Success] Loaded C:\Users\Ged\AppData\Loc...Hello,
Click on the Windows menu -> search for "cmd.exe". Click right on it, "Launch as Administrator".
Then, copy paste the following command in it :
sc delete "UCGuard"And then :
sc delete "KuaiZipDrive"You should get a success message afterwards saying the removal operation has succeeded.
Finally, just reboot and share a Scan with AdwCleaner.
Best regards,
# AdwCleaner v5.200 - Registro generado 19/06/2016 en 21:47:49
# Actualizado 14/06/2016 por ToolsLib
# Base de datos : 2016-06-19.1 [Servidor]
# Sistema operativo : Windows 10 Home Single Language (X64)
# Nombre de usuario : migue - DESKTOP-4HI7U09
# Ejecutado desde : C:\Users\migue\Desktop\adwcleaner_5.200.exe
# Opción : Limpiar
# Apoyo : https://toolslib.net/forum
***** [ Servicios ] *****...Hello!
Yes, I still have this problem with QuickDiag.
The error message is still the same, but only the QuickDiag file date has changed;
"Line 7859 (File "C:\Users\TMA\Downloads\quickdiag_2_13.06.2016.1.exe"): Error: The requested action with this object has failed."
The problem file is still this: [22/09/2015 17:16:32] - C:\Windows\Installer\3ef7a91.msi : (Intel(R) Chipset Device Software...