I tried with Avast disabled and ran as Admin, but the same result as my first post....
It may be a long shot, but, does v5.108 support non SSE2 CPUs? I have 2 other XP sp3 machines wit similar setups that run v5.108 with no problems, but this problem machine runs an old non SSE2 CPU?
AdwCleaner falsely reports several items related to the tools UpdateStar and UpdateStar Drivers. Here is an excerpt from a log file:
# AdwCleaner v5.108 - Logfile created 04/04/2016 at 11:01:27
# Updated 30/03/2016 by Xplode
# Database : 2016-04-03.2 [Server]
***** [ Folders ] *****
Folder Found : C:\Program Files (x86)\UpdateStar Drivers
Folder Found : C:\ProgramData\Microsoft\Windows\Star...Bonjour,
Pouvez-vous désinstaller entièrement AdwCleaner avant d'utiliser la version 5.108 ?
(Lancez AdwCleaner -> Désinstaller").
fr33tux, 2016-04-01 20:16:11 (UTC)
Bonjour,
Déjà désinstallé, restauration à une date antérieure au problème, passage de Ccleaner, Glary utilities et Wise registry Cleaner, le problème reste entier et obscur.
Can you temporary disable it, then launch AdwCleaner as administrator ?
(Then, reactivate it).
Yes, I have Avast free
Hello,
Do you have a security software running at the same time ?
Yes, I did make sure to uninstall the previous version as ypu describe and downloaded v5.108 from the link that you posted.
AdwCleaner starts up fine, gets into "loading database", and then the error message as above.
Hello,
Did you clean older AdwCleaner versions ? (Launch it -> Uninstall) and get the latest release from here : https://toolslib.net/downloads/viewdownload/1-adwcleaner/
AdwCleaner starts OK, then program error at loading database.
Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 03/04/2016 Time: 7:05:40 PM User: N/A Computer: USER-********** Description: Faulting application adwcleaner_5.108.exe, version 5.1.0.8, faulting module libeay32.dll, version 1.0.2.6, fault address 0x00070...Hello,
It doesn't look like this error is related to AdwCleaner. I'd suggest trying a "sfc /scannow" or replacing SHLWAPI.dll
If the error still occurs, it would be helpful to have an AppCrashView report about this error ( http://www.nirsoft.net/utils/app_crash_view.html )
Regards,