# AdwCleaner v5.201 - Rapport créé le 01/07/2016 à 19:51:32
# Mis à jour le 30/06/2016 par ToolsLib
# Base de données : 2016-06-30.2 [Serveur]
# Système d'exploitation : Windows 10 Pro (X64)
# Nom d'utilisateur : Alexandre
# Exécuté depuis : D:\Downloads\adwcleaner_5.201.exe
# Option : Nettoyer
# Support : https://toolslib.net/forum
***** [ Services ] *****
***** [ Dossiers ] *****
***** [...Bonjour,
Oui toutes les mises à jour sont effectives sauf la KB3126587 et la KB2952664 que WindowsUpdate me refuse systématiquement.
Merci pourvos recherches.
Cordialement, Jean-Da
Bonjour,
Excusez-moi du délai de réponse.
Avez-vous bien l'ensemble des mises à jour Windows appliquées ?
Bonsoir ! Pourquoi ne pas songer à opter pour des versions plus récentes ? Je te conseille d’utiliser le système Windows 8.1, les fonctionnalités sont plus avancées et faciles à manipuler. Suis cette formation pour mieux t’éclairer : http://www.alphorm.com/tutoriel/formation-en-ligne-windows-8-1-70-688.
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