Bob_Coleman
Honorary Members-
Posts
21 -
Joined
-
Last visited
Reputation
0 NeutralRecent Profile Visitors
731 profile views
-
powercfg.cpl being blocked
Bob_Coleman replied to Bob_Coleman's topic in Malwarebytes for Windows Support Forum
Much to my surprise, that worked. I don't understand what this has to do with Office, what the implications of turning it off are, or why this only started happening in 4.5.8, but I guess I'll just be happy the behavior is gone. Thanks for your help. -
powercfg.cpl being blocked
Bob_Coleman replied to Bob_Coleman's topic in Malwarebytes for Windows Support Forum
Looks like off. Another point: I don't know if there was a 4.5.6 or 4.5.7. This behavior does not occur on 4.5.5 but does on 4.5.8. -
powercfg.cpl being blocked
Bob_Coleman replied to Bob_Coleman's topic in Malwarebytes for Windows Support Forum
Detection log attached. I'd still be interested to know how to add this to the Allow List. I should also mention that after resetting something to default as mentioned above didn't make any difference, I restored my Windows partition to a state before the reset since I didn't really know what I had changed and it didn't seem to make any difference. This is to say that the defaults were not in effect when the attached log was created, but it doesn't seem to make any difference. Malwarebytes Detection Log.txt -
powercfg.cpl being blocked
Bob_Coleman replied to Bob_Coleman's topic in Malwarebytes for Windows Support Forum
After doing that the issue remains. -
Starting apparently in Malwarebytes 4.5.8, the comand start /min /D"C:\Windows\System32" powercfg.cpl entgered at a command prompt works OK, but the same command run from a bat file is blocked as an exploit Malware.Exploit.Agent.Generic. Furthermore, I can't figure out how to add it to the Allow List.
-
I notice reports of this problem back to at least late January. I only started seeing it recently. Not sure exactly when, but I have version 3.4.5 installed and am still having the problem of high and persistent CPU and disk usage. I'm not yet sure about this, but it seems like perhaps the resource consumption doesn't happen immediately after booting the system and may only happen only after running a manual scan. I don't have any scheduled scans. I don't think it happens after every scan either, but it does happen often enough to be a nuisance.
-
It was Edge, not IE, but I seem to no longer have the issue.
-
Forgot Addition.txt . Addition.txt
-
Requested files attached. FRST.txt MBAE.zip
-
I seldom use and have very little familiarity with Edge, but I happened to try it yesterday and got the same problem. So I tried again today, same result. There seems to be a general problem regarding the latest MBAE and Edge.
-
After following the removal and re-install instructions, an initial Threat Scan (before rebooting, I think) completed normally. However, after rebooting Threat Scans produce the Error Code 8. I do note that Threat Scan completed successfully and Scanner Failed with Error Code 8 seem to appear at the same time. When I first observed the problem, I was running a Custom Scan. I don't think it completed before the Error Code 8 appeared, but it seems more sensible to focus on the simpler scenario for now. Requested logs are attached. FRST.txt Addition.txt CheckResults.txt
-
Malwarebytes Anti-Malware Home (Premium) 2.2.0.1024 on Windows 10 Home. For a long time. I've had only one user account on my PC on which I'm the only user. This account, of course, had administrative privileges. Recently, I decided to try to heed advice to perform routine actions from a standard, non-admin, account. My intent was to leave the admin account essentially unused serving just as a vehicle whose password I can enter when required. Now, whenever I run a scan (from the standard user), I get Scanner Failed with Error Code 8. Is it possible to successfully run a scan from a non-admin account? I've attached the log from the latest scan. MBAM Log.txt
-
AxCrypt-1.7.2867.0-Setup.exe flagged as PUP.Optional.OpenCandy
Bob_Coleman replied to Bob_Coleman's topic in File Detections
OK, thanks. I think I understand now. I'm not convinced that it's desirable to have something like this detected, but I understand that doing so is current policy and that there are probably valid points pro and con. -
Axcrypt potentially unwanted?
Bob_Coleman replied to Bob_Coleman's topic in Malwarebytes for Windows Support Forum
Though this could be a too fast reaction without enough consideration being given, I think I would prefer that something not be detected, but I understand that such detection is current policy and that there are probably valid arguments pro and con..