Re: Win XP support

dans AdwCleaner par fr33tux

Hello,

There is a possibility to realize an XP support in current version.

Yes.

I wrote back in August to fr33tux and sent him screens with explanations on how to add XP support to your project. So for now it seems like a MBAM PR action that you don't want to realize such support (though you can).  

It's not a question of technical difficulty, it's a choice to not support an OS no longe...

Re: adwcleaner 7.0.2.1 won't run on windows 10 64-bit?

Hi, I came from a thread (https://toolslib.net/forum/viewthread/12767-my-adwcleaner-has-problem/?p=1#!messageId-13228) where one of the administrators had gave out another link to this thread here. As if this were to be the problem solver. But it only brings me from the problem that I'm having, where an error message pops up after attempting to clean ("*** Caught unhandled unknown exception, te...

Re: Major difficulties with AdwCleaner v. 7.0.3.1

dans AdwCleaner par notnats

No response in TWO days!

It sure would be nice if this could finally be fixed. It appears these problems with AdwCleaner and PUP.Optional.Legacy and PUP.Optional.AdvancedSystemCare  listings have been going on since the release of v. 7 months ago. The reply always seems to be . "Thanks for the details. We'll look into it". or "it will be fixed with the next update"

I for one have been helping...

Required Registries Removed?

I recently did scans that removed the listed registry files. Will this cause problems, or are they safe to remove?

 

PUP.Optional.Legacy, [Key] - HKU\S-1-5-21-1745523471-2157326767-3355521870-1000-{ED1FC765-E35E-4C3D-BF15-2C2B11260CE4}-09242017083000032\Software\Host App Service

PUP.Optional.Legacy, [Key] - HKU\S-1-5-21-1745523471-2157326767-3355521870-1000-{ED1FC765-E35E-4C3D-BF15-2C2B11260...

Re: Major difficulties with AdwCleaner v. 7.0.3.1

dans AdwCleaner par notnats

This is the only log available that says clean. This was done when he removed ALL check marks from all items found. Otherwise, when he removed check marks only from the registiry section the program did not go through with clean it just shut down. .

Hello,

This time he hit clean and the program closed, the computer shut down but when it rebooted it had not cleaned anything.


notnats, 2017-1...

Re: Major difficulties with AdwCleaner v. 7.0.3.1

Hello,

This time he hit clean and the program closed, the computer shut down but when it rebooted it had not cleaned anything.


notnats, 2017-10-02 03:31:16 (UTC)

Can you please share the cleaning logfile?

Thanks.

Re: Major difficulties with AdwCleaner v. 7.0.3.1

dans AdwCleaner par notnats

Update:

As per this thread; https://toolslib.net/forum/viewthread/13432-adwcleaner-7031-has-stopped-woring/

I had my friend try this suggestion;

Try to uncheck every registry element detected before pushing the Clean button. Then, it should work as expected.

It did not work. He tried in both normal mode, and received the message that "AdwCleaner stopped working" as soon as he hit clean. S...

Major difficulties with AdwCleaner v. 7.0.3.1

dans AdwCleaner par notnats

I am helping a friend clean a grossly infected computer. Windows 10. Uses McAfee AV.

He ran Malwarebytes 3 without difficulty and it cleaned with no problem at all. I do have the log if needed but cannot find a way to attach the text file

He then attempted to use AdwCleaner v. 7.0.3.1 but it would not complete cleaning and received a box with notification that a problem had stopped the clean....

Bitdefender Agent WatchDog Task and 7.0.3.1

dans AdwCleaner par Krunk01

Hello:

I just installed AdwCleaner 7.0.3.1  on a Windows 10 Version 1703 for x64-based System.

The post-clean Logfile has the following message:

***** [ Tasks ] *****

Deleted: Bitdefender Agent WatchDog_65D6944A0EF74FDAB96E31112AD39864

After a reboot and  rescan the Bitdefender Agent WatchDog is tagged again as a threat but  I believe this is a valid Bitdefender scheduled task.

Please inv...

Re: AdwCleaner 7.0.3.1 has stopped woring

Greetings,

Sorry for the late answer.

Try to uncheck every registry element detected before pushing the Clean button. Then, it should work as expected.

This issue is known and will be resolved with the release of the 7.1 version.

Regards.