John A

On my three Windows 10 computers with Malwarebytes 3, I had a very strange issue this morning. I don't know if Malwarebytes is involved but I thought I would post this here because there have been issues raised about Malwarebytes interfering with System Volume Information. Following the monthly Windows updates today I ran Disk Cleanup then again with "Clean up System files" On all three computers the Windows update cleanup offered to clean an impossible amount of storage. On the example attached - 3.99TB on a computer that has a single 580GB disk drive! Same story on the other two computers. I let Disk Cleanup delete these files and it took a long time (about 45 minutes) and this cleared the issue. Is anyone else experiencing this issue?

I recommended Malwarebytes Pro to my neighbour a few years ago. He has Windows 7 x 64 running MSE only. Today, his Malwarebytes did an auto upgrade from 2 to 3. On restart his computer was "weird" and he couldn't access email/docs, etc.so I went and had a look. This is what I found Windows had started with a temporary profile MSE had stopped, would not start and would not update I stopped Malwarebytes starting with Windows, turned off all protection layers, changed the setting to never register MB in the Action Centre Restarted and all was back to normal. Logs could not be obtained. He only wants to use Malwarebytes as a scanner now.

OK Shall do

Happened once only so far.

Brief description of the issue Started Win 10 Desktop today, Malwarebytes Malware Protection was off. Tried to start it manually, got stuck on "Starting". Restarted computer, all good. Any screenshot(s) of error messages(s) or other incorrect behavior None If the system crashed (aka blue screen of death or BSOD), please include the error message N/A Details on how you encountered the bug and any steps that can be taken to reproduce it Already covered, cannot reproduce Do you get the same result more than once if you follow the same steps? Y/N N Obtain and post a copy of the Malwarebytes logs See previous post Create and obtain Farbar Recovery Scan Tool (FRST) logs Will send by PM if requested, devs already have it from previous issues Create and obtain an mb-check log: Attached MB-CheckResult.txt

Started Win 10 Desktop today, Malwarebytes Malware Protection was off. Tried to start it manually, got stuck on "Starting" Restarted computer, all good. MBAMSERVICE.zip

I have had one instance of Microsoft Publisher hanging when starting it from an entry in its jump-list. Publisher starts but hangs trying to open the file. Had to force close it. Publisher version is 16.0.4498.1000 x32. Unfortunately I did a clean reinstall of Malwarebytes and lost the logs for that event.

Are the errors in the attached logs of any concern? MBAMSERVICE.zip

Thanks for letting us know

Thanks 1PW, I should have put it there instead of this forum.

First of all, have you installed the latest beta version? A workaround for this issue is : Malwarebytes > Settings > Application > set Windows Action Centre to "Never register Malwarebytes in the Windows Action Centre" Restart and check that Windows Defender is OK Malwarebytes should not cause Defender to turn off. Staff may request further info about your system.

When I turn a protection layer on, it says "Starting" But when I turn a layer off there is no indication acknowledging the switch. Turning off Web protection takes around 10 seconds before the switch goes off. Turning off all four layers at once takes about 18 seconds. I suggest that the protection layer switches should say "Stopping" during this period so we know something is happening.

Installed over the top of previous beta. Lower controls on UI partially hidden on many screens Maximise > Minimise Malwarebytes UI fixed it.

@ Super Dave Yes, I was surprised also.

@galileo I have had two periodic unexplained issues. They are BSOD, and Ethernet adaptor failure on wakeup from Sleep. I haven't mentioned these to this point because I need more determine what causes them. I am currently running with MB3 RTP off and so far haven't experienced either issue, but early days yet.

@galileo The profile corruption is apparently rare, although there may be users out there experiencing it who don't realise that MB is causing it. It happens on Windows 10 x 64, x32 and Windows 7. I understand each computer is different, but MB should not interfere with basic Windows functions like user profiles.

x64 - that is very interesting. All I can add is that on three Windows 10 computers, I never had this user profile corruption with Malwarebytes 2. But after installing MB3, it starts happening on all three computers. I didn't try logout/login, I always recovered but restarting.

I have fiddled with this setting some time ago with no luck. You might restart a few times and it seems fine, then try a few hours later and it happens again. Tricky to pin down.

Yes, it is has been known about since beta testing but not listed as a known issue, so who knows when it will be fixed. The fact that it happens is a worry though. I understand that it is a difficult issue to track down. I am reluctantly using Malwarebytes 3 just as a secondary scanner at present, not starting with Windows.

You should be able to quit and uninstall.

Yes it does

Clean install Malwarebytes version: 3.0.6.1469 Component package version: 1.0.69 Windows 10 x 32 Ransomware failed to start on install and restart. Manually started Ransomware, OK so far This version working fine on two other Win10 computers MBAMSERVICE.zip

My experience is that delaying RTP doesn't help with this particular problem.

What probably happened is that Malwarebytes caused a Windows Profile corruption, so it opened a "Temporary profile" so you had some access to the computer but appeared to have lost your documents. This is a known issue but for some reason is not listed as such. If you got it once you will get it again. The only way around this problem at present is to set Malwarebytes NOT to start with Windows. Start it manually after you log in. Also see this thread for a way to start Malwarebytes at Login.

No, they weren't. See this thread