bikemanAMD

Yeah i Keep UAC enabled as well, on all the machines

Hopefully not, though is second time i had to do the same fix on Desktop version of Malwarebytes Free, and still have to fix Laptop, probably work on that one possibly later or tomorrow depending on what else going on. Try to Keep the systems with as close software layout as i can, ((though Desktop has a few more games)) Still need to upgrade Laptops M.2 Drive if i can ever get the Laptops bottom cover off lol, darn screws lol, may have shop do that after pandemic is over i hope.

Yeah well i always did, guess personal preference i suppose on the using limited account for security, i started doing that after major system infection a long time ago, and just kept at it, of course i can start running malwarebytes only on the full admin account for my weekly scans if need be

I'm using my Microsoft account 90 percent of the time, ((Limited account), when i discovered the issue, Admin account used for Admin tasks as needed, always setup my systems like that for years, same for Laptop machine

Well i did grab the results for the Desktop that time, then went ahead and cleaned, and reinstalled, as it was second time i had to do this on the Desktop, so kinda just automatically did the steps lol, uploads the log files mbst-grab-results.zip

Hello All **Note just reporting this issue, already fixed with Malwarebytes Suppport tool on this system for the second time, will have to fix on Laptop though tomorrow or later** Went to open it to do my weekly scan this morning, no response from Open Malwarebytes at all, or from the start menu icon, then download malwarebytes support tool, cleaned it out, restarted, then reinstalled it, then did my weekly scan, and seems to be fine now. Any idea what it's happening? Windows 10 Pro 2004 on this system, and Windows 10 Home x64 2004 on Laptop that i still have to fix tomorrow.

In Addition I've been detecting TheBrighttag.com with Adwcleaner for a while now on all systems, Previous Real time protection was Avast Free Antivirus, and Malwarebytes Free, Decided to run ADWCleaner to make sure nothing was missed, Detected PUP.OptionalLegacy and TheBrighttag.com, cleaned and restarted, on each system, and a few weeks later run ADWcleaner 7.2.6.0 again, and same detections yet again Not sure if false positive, something with Avast or what, Main Desktop currently running Windows Defender built into WIndows 10, I havent' switched the other systems yet til I determine what the cause is if possible

Cleaned with ADWcleaner, then system restarted, then I posted the logs after restart

Ok Here is the requested log file, hopefully this helps AdwCleaner_Debug.log AdwCleaner[S09].txt

Well I got the original scan detection log, second scan now showing clean for the moment, Debug log files with ADW Cleaner not seeing any of those present. I'll attach the cleaning log if that helps any AdwCleaner[S09].txt

Ok I removed it a week ago, Rescanned today 1/24/2019, and still getting detection with ADW Cleaner, regularly Malwarebytes isn't saying any detections AdwCleaner[S08].txt

Hi All Currently Running Windows Defender, and Malwarebytes Free, Later on tonight Swapping to Avast Free, and keeping Malwarebytes free, each time I run ADW Cleaner 7.2.6.0 I end up with detections for Brighttag or something? So little bit uneasy continuing to trust Windows Defender for main protection, plus I used Avast for last 10-11 years Started using Avast back in 2006, when I got a very very very bad infection when I was a tester for WIndows Live One Care in Windows XP Days, and ever since then felt not too safe with Defender I have not removed or Restarted system yet to fix this, will hopefully wait for an answer regarding this and then take care of it AdwCleaner[S02].txt

Hello All Wondering if this is a false positive or a real detection, 2 machines on Network detected Pup.optional.thebrighthub think was name, and PUP.Optional.Legacy AdwCleaner[S01].txt

Having Same issue again!!, Getting annoying, where is the removal tool to remove it fully, and then try 3.05 clean install or should we wait til stable build is out, keeps reverting to 3.0 version and I did nothing to cause that, rebooted a dozen times, then when goto run a scan notice it reverted back to 3.0.0 from 3.0.5 really

Well was working great, noticed it reverted itself again to 3.0.0. Not sure how that happened, I did several reboots, and such since then. Doesn't happen immediately after a reboot, it happened suddenly, as last night I checked and it was still 3.0.5 Go to run a scan tonight since noticed a few issues that I thought may have been malware, so I was like i'll run a scan anyways, then noticed it said Malwareybes 3.0.0 on top of the program

Well Rebooted a few times, and can't seem to get it to Revert now to 3.0 on my system Guess whatever it was, isn't happening now Still shows Malwarebytes Free 3.0.5

Will Try rebooting a few times, and see if it does, if and when it does, will then send the logs.

Will Do, Will have file in a few minutes here, Ok Restarted System, What is weird on this system this time it stayed at Malwarebytes Free 3.0.5, whereas last reboot it didn't after updating to 3.0.5 version on December 19th. Would you like the data gathered still sent?

Will Do, Will have file in a few minutes here

Same Problem, Free Malwarbytes user, know I updated on the 19th to 3.0.5.1299, ran it last night as part of my weekly scan I do with the free edition, and discovered it was 3.0.0 version, then it said update available, so installed that program update, went to 3.0.4, then did 3.0.5 Manually, Haven't rebooted yet the system to see if it sticks or not, or reverts back to 3.0.0 Antivirus if that helps any is Avast Free 12.3.2280 Windows 10 Pro 64bit Build 14393.576

Have that issue as well, Using Avast Antivirus Free as my primary protection, in Windows 10 Pro 64bit build 14393.576, Excluded the files they said in email to try excluding, so I did that, still high CPU with Malwarebytes 3.0.5.1299 Is it a Conflict with Avast? is Avast too much protection now with Malwarebytes Free? what should I do next to fix this issue?