Search

Oh! As your advice, I did it, and AdwCleaner worked OK. Thank you very much, Mr.Developer!  (I don't know how to share the file "AdwCleaner_Debug.log" to Forum). Sorry.

Hi,

Just a quick intel, the version described above won't be up-to-date in term of detections.

Regards.

Hi,

Just to let you know that the official 7.0.1.0 version has been released since several hours now. The scan crash issue should be resolved.

Regards.

I did the same with my second machine with WIN 8.1. The same problem, the same error message. Atgtached pls find the content of the debug log file.

2017-08-01 13:14:15.535 DEBUG [9084] [MainUI::buttonScanClicked@294] [i] Scan button clicked (-31986) 2017-08-01 13:14:15.538 DEBUG [8304] [MainUI::Entry@1271] [+] Checking for update... 2017-08-01 13:14:16.040 DEBUG [8304] [AdwCleanerSDK::checkCA...

Hi again,

Alright, I was expecting the debug logfile but at least we know where the error comes from.

Nevertheless, the findings of the "PUP.Adware.Heuristic" in the folder "C:\ProgramData\Audyssee Labs" you cannot find in the protocol file!

 Can you develop a bit?

Thanks.

OK, can you please share the scan logfile from AdwCleaner?

I guess, i found out, where the error came from.  After the scan has finished, following screen can be seen:

http://abload.de/image.php?img=2017-08-01_123851thsvf.png

Nevertheless, the findings of the "PUP.Adware.Heuristic" in the folder "C:\ProgramData\Audyssee Labs" you cannot find in the protocol file!

# AdwCleaner 7.0.1.0 - Logfile created on Tue Aug 01 10:37:27 2017 # Updated on 2017/0...

Thank you for reply,

i used both, 7.0.0.0 & 7.0.1.0 and always the same popup

Best regards

Greetings,

Before doing what is described above by JoshRoss, please try the following manipulation:

1. Activate the debug mode (go to Tools > Options > tick "debug")
2. Then, do a scan and a clean to trigger the crash
3. Finally, please share the file C:\AdwCleaner\AdwCleaner_Debug.log in your next answer

Thanks!

Weird how older version works but never doesn't.... That shouldn't be the case, let's hear if the new version solves the problem.