vbarytskyy

@whb52ford Thank you for confirming. Could you run FRST for me and upload those logs, running MB-Check after FRST will gather the logs as well. See post below:

@msaine Were you able to add exclusions as suggested by Porthos?

@whb52ford Could you try toggle "Fast Start" and let us know if that helps with this issue? Click on Start (Windows logo) and type in "Control Panel" Go to "System and Security" and click on "Power Options" On the left-hand side, click "Choose what the power buttons do" Select the "Change settings currently unavailable" link Uncheck the "Turn on fast start-up" box under Shut-down settings Reboot

@snowing This installation should repair any components that had a problem so theoretically, the next upgrade should work properly for you.

@liewcake I'd like to investigate this issue a little further. How do you connect to PIA? Is it through their client or is VPN setup through Windows?

@tlodge28 I'd like to investigate this issue a little further. How do you connect to PIA? Is it through their client or is VPN setup through Windows?

@Luke4efc I am seeing some issues with config files getting loaded properly. Could you do a full reinstall using MB-Clean and turn on debug logging for us. Once the issue is shows up again, re-run MB-Check and upload logs one more time. Debug logs will have a little more information for us to look over. Run MB-Clean from here Once reinstalled, turn on debug logging: Open Malwarebytes and go to Settings Under Application tab, scroll down to "Event Log Data" Toggle on Once the issue is replicated again, run MB-Check (may take a day or two based on description of the problem) Re-upload logs

Hello @ldarnett I moved your topic its own thread. Could you try installed the latest Malwarebytes on top of your existing installation? Download Latest Here If that has no affect on the problem you are experiencing, could you get us some logs to look into? Look below on how to get logs:

Hello @snowing Could you try upgrading to the latest Malwarebytes 3.3 and report back? Get Latest Version Here

@Gee Could you get us some logs to look over so we can see what's happening? Follow the link below for help with getting logs. Make sure to get FRST and MB-Check logs.

It looks like your Windows Management Instrumentation(WMI) service is not running. Could you make sure it is not disabled. Click "Windows" + R keys to open the "Run" dialog Type in "services.msc" Look for Windows Management Instrumentation service Make sure to set it to "Automatic" if it's set to disabled Right-click and go to "Properties" Change "Startup Type" to "Automatic" Hit "Apply" Make sure to start the service if start up needed to be changed Right-click and hit "Start" If the above instructions don't work or the service is damaged, follow the following instructions to repair WIM: Download the Windows Repair (All in One) tool from here: Click Here When the tool opens look across the top and you'll see tabs. Click the Backup Tools tab and make sure you Backup the Registry and Create a Restore Point. The screen is very clear on how to do that – just click the related buttons. When those have completed, you're now ready to click the 'Repairs' tab. When that window opens, uncheck the "Automatically Do A Registry Backup checkbox and then click the 'Open Repairs' button. Now you will see a list of all the things it can repair. Many (if not all) will be automatically checked off – we do NOT want to repair everything! Uncheck the box at the very top next to 'All Repairs' and that will uncheck them all. Place a check in the following box: 05 - Repair WMI Click the Start Repairs button and give it some time. Do not use the computer while this is carrying out the repairs. Reboot when prompted.

Hello @cobblers Based on the logs that I am seeing, it looks like a few Malwarebytes config files are missing from the system. Could you try to run an installation on top of your existing one and re-run MB-Check? Get Malwarebytes here

@Loc2262 Could you get us full logs to look over. See the link below for help with getting logs, make sure to get FRST and MB-Check logs Thank you

Hello @Luke4efc I moved your comment into its own topic so we can track issues separately. Could you get us some logs to look into? See link below for help with getting logs.

Hello @Luke4efc I moved your comment into its own topic so we can track issues separately. Could you get us some logs to look into? See link below for help with getting logs.

@Jerzy Check this article: Deactivating License

When you go to reinstall again, I would advise to use the MB-Clean tool as it'll give the system another check over for any left overs files (that possibly got corrupted and cause protection layers to turn off) and then install the latest available version for you. MB-Clean

Hello @RL1 Could you get us some logs to look over? Follow the link below for help with getting logs:

This issue is typically due to lacking sufficient virtual memory. What leads you to believe Malwarebytes is causing this issue? Is it still occurring after removing Malwarebytes? Could we get more logs to look into possibly to see what is happening? Follow the link below please and get logs for us to review:

Hello @Joe5211 I moved your topic to it's own thread. Try the following for me: Open Malwarebytes and go to "Settings" > "Scan Schedule" Select your schedule and hit "Edit" towards the bottom Hit "Advanced" and check the box that states "Scan for Rootkits"

@REHammer Would you be able to provide us with logs so we can investigate this issue? See how to attach logs below:

@TheMasterMojo Could we get an FRST log as well, please?

Changing the following setting should enable Windows Defender properly.

Could you get us more detailed logs please? See the following post on getting logs. Make sure to get MB-Check and FRST logs.

@Miha Glad it's working. Let us know if anything arises.