Malware Protection Service slowing my PC (did not before ~2 days ago)

[John_Wayne]

Hello,

My PC started to act very slowly about~2 days ago. Applications would take minutes to launch, internet browser tabs would take seconds to open, and etc. I started to troubleshoot why. There were no obvious indicators. Today I found the culprit, MalwareBytes Malware Protection Service. I know this is the culprit because turning it off makes my computer run normally/smoothly/quickly (i.e. Applications launch instantly as they always have).

As this has never happened before, was there a recent patch that could have caused this? Is there a fix patch coming? Or are there other suggestions?

Right now I am having to leave 'off' "Malware Protection" in order to even use my computer...

Thanks,

John

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

1. Download Malwarebytes Support Tool
2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
3. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
4. Place a checkmark next to Accept License Agreement and click Next
5. You will be presented with a page stating, "Get Started!"
6. Click the Advanced tab
   
    
7. Click the Gather Logs button
   
    
8. A progress bar will appear and the program will proceed with getting logs from your computer
   
    
9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
   
    
10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
       

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

Spoiler

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

[John_Wayne]

grab logs ran and attached

mbst-grab-results.zip

[Firefox]

Hello and Welcome!

While we wait for your logs to get reviewed, what happens if you reboot your computer? It seems its been up for at almost 6 days?

Machine Information
==================================
System has been up for:  5 days 15 hours 55 minutes 52 seconds

[John_Wayne]

Hey FF,

Very Odd, I literally rebooted it this morning in an attempt to speed up the PC (prior to switching off the service).

I also (just) rebooted my machine (as in shut down, and pressed the power button on) and the cmd> systeminfo still shows a boot time of "System Boot Time:  11/29/2018, 8:05:47 PM"... well another bug for another time I guess

[Firefox]

With windows 10, a shut down is not the same as a reboot... a shut down sort of puts in in sleep mode per say, so you need to select reboot from the menu.

[exile360]

It may also be worth checking to make certain that Fast Startup is disabled.  It is on by default in Windows 10 and has been known to cause problems with some programs as well as some hardware/drivers, including Malwarebytes, in the past.  You can find more info, including instructions on how to check and disable it here as well as here.

That may not be the cause of the issue, but it is worth a try at least to eliminate it as a possibility.

[John_Wayne]

1 hour ago, exile360 said:

It may also be worth checking to make certain that Fast Startup is disabled.  It is on by default in Windows 10 and has been known to cause problems with some programs as well as some hardware/drivers, including Malwarebytes, in the past.  You can find more info, including instructions on how to check and disable it here as well as here.

That may not be the cause of the issue, but it is worth a try at least to eliminate it as a possibility.

Thanks, but it appears that this option is disabled !? eh....

[exile360]

No, actually, according to that image fast startup is turned on (the box next to it is checked and grayed out; likely because you need to click the Change settings that are currently unavailable link at the top with the security/UAC shield next to it to modify it).

[John_Wayne]

Just now, exile360 said:

No, actually, according to that image fast startup is turned on (the box next to it is checked and grayed out; likely because you need to click the Change settings that are currently unavailable link at the top with the security/UAC shield next to it to modify it).

well, im an idiot. done and done. testing now.

[exile360]

No, you're not.  Honestly there's a reason there are so many tutorials about this feature and how to enable/disable it.  It really isn't very clear or easy to find unless you know where to look, and Microsoft enables it by default even though it's a completely new feature known to cause issues with a lot of hardware and software because of how it functions.

[John_Wayne]

21 minutes ago, exile360 said:

No, you're not.  Honestly there's a reason there are so many tutorials about this feature and how to enable/disable it.  It really isn't very clear or easy to find unless you know where to look, and Microsoft enables it by default even though it's a completely new feature known to cause issues with a lot of hardware and software because of how it functions.

well I work in IT and use to be a sys admin, so yea idiot me haha

ok... so I did this, and I shut down/started and enabled the malware protection service. Now everything appears to be running smoothly which is crazy and I am having trouble buying this... so I must ask, how do I see if malware-bytes has received an update or no?

[Firefox]

1 hour ago, John_Wayne said:

how do I see if malware-bytes has received an update or no?

Funny you should ask, just about an hour ago they release a new update, you can read about it in the topic below (which shows you how to install the update by clicking on Install Application Updates)

 

[John_Wayne]

ah

So that may likely be the source of resolution.

Anyhow, my issue no longer exists after the update and/or the fast boot correction. Thanks for your help!!

[Firefox]

Your welcome, glad we could all help... should you have further issues or questions don't hesitate to ask.

[John_Wayne]

will do thanks!

[exile360]

By the way, just in case you're curious, the issues caused by fast startup range from problems with drivers and services not loading on boot, to program crashes, to registry read/write issues because of how it keeps some components stored in volatile memory while others are unloaded/closed normally, resulting in many programs and components not starting again properly or even at all once the system is woken up/booted again (because they're coded to function under a normal startup process, where they are not expecting other components to already be in memory as though they were never shut down/closed, which is usually where problems with Malwarebytes and other security software and drivers occur due to dependencies between their drivers, services, and startup executables).

That said, they did highlight some fixes with protection in the changelog for the new release so it's entirely possible that this is what fixed the issue for you.