Search

Hello,

@anhthe2812: Can you generate FRST logs for a final check ?

• Download FRST
• Right-click on the file -> "Execute as Administrator"
• Click on the "Scan" button
• The logfile is saved as FRST.txt , and additional informations are in Addition.txt.
• Please host them on Up2Share and share the generated links.

Thanks,

Hello,

@Proton: I'm sending you an email with the coming release which includes the fix for this issue.

Thanks a lot regist for the help :)

Best regards,

Hello,

Can you share the whole logfile please ?

Thanks,

Hello,

Can you share the whole logfile please ?

Best regards,

Can you launch AdwCleaner, click on Tools > Options, and tick "Debug" in "Mode" section. Then, do a scan.

When the crash occured, please host the file C:\AdwCleaner_Debug.log on https://up2sha.re/ and share the generated link here.

Hello,

I am using adwcleaner for years now and I am very happy with it. I use it to clean computers on remote using logmeIn Rescue. But after the update in August I can;t connect anymore after a reboot of the computer. By testing it on another computer I saw that after the first reboot logmein won't start up but after a second reboot it comes back and I have full control again. So it seems ...

Hello,

As cocochepeau said, sorry for the confusion.

@Albertsudarto:

Did you uncheck the following elements prior AdwCleaner cleaning ?

***** [ Services ] *****
 
[!] Service not deleted: UCGuard
[!] Service not deleted: backlh
[!] Service not deleted: Quoteex
[!] Service not deleted: Kuaizip Update Checker
[!] Service not deleted: KuaiZipDrive2
[!] Service not deleted: SoEasySvc
 
 
*****...

Thank you for taking the time to work with me on this. It is greatly appreciated.

In the debug log I see SimpleService.exe as a service being killed with no whitelist line under it but it appears that file isn't actually the file that keeps the remote session active anyways.

I manually killed the SimpleService.exe service and the remote session stays active with no problems.

Please see scree...

Ahh yes, my mistake. Here are the two logfiles from a scan I just ran in Debug mode.

AdwCleaner_debug:

2016-09-03 18:38:49 :     <INFO>    [main] - Saving current options to the configuration file 2016-09-03 18:38:50 :     <INFO>    [main.gui] - Scan requested 2016-09-03 18:38:50 :     <INFO>    [scan] - Running from: C:\AdwCleaner 2016-09-03 18:38:50 :     <INFO>    [scan] - Progress: 0% 20...

Hello,

Also, if you still have the software killed, please share the debug log from AdwCleaner:

• Activate the options with Tools > Options > "Debug" in "Mode" section,
• Do a scan and a clean,
• Share the file C:\AdwCleaner\AdwCleaner_Debug.log.

Best regards,