Malwarebytes 3.1.2 Not Starting Properly - unable to connect to service

[J5I]

I am running Windows 10 without the Symantic application.  Since installing 3.1.2, my Malware application will not launch.   I have to re-install it in order to launch the application.  I tried a clean uninstall prior in re-installation, and installing over the current version.  Neither method allows MB to start after reboot.  I get the following error.

Unable to start.  Unable to connect to the service.

Edited June 16, 2017 by J5I
Added error message

[Porthos]

1 minute ago, J5I said:

I am running Windows 10 without the Symantic application.  Since installing 3.1.2, my Malware application will not launch.   I have to re-install it in order to launch the application.  I tried a clean uninstall prior in re-installation, and installing over the current version.  Neither method allows MB to start after reboot.  I get the following error.

 

 

• Create and obtain an mb-check log
  1. Download MB-Check and save to your desktop
  2. Double-click to run MB-Check and within a few second the command window will open, then click "OK" 
  3. This will produce one log file on your desktop: mb-check-results.zip
     • Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area
• Create and obtain Farbar Recovery Scan Tool (FRST) logs
  1. Download FRST and save it to your desktop
     Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
  2. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
  3. Press the "Scan" button
  4. This will produce two files in the same location (directory) as FRST: FRST.txt and Addition.txt
     • Attach both of these logs to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the files to the attachment area

 

[J5I]

Attached is the log file, and FRST scanning results

Addition.txt

FRST.txt

mb-check-results.zip

[Porthos]

There's a known issue with MB3 and F-Secure. To fix this, go into F-Secure settings to the following page and click the exclusions link at the bottom. Then add C:\Program Files\Malwarebytes\Anti-malware to the exclusions. Then restart and your issue should be resolved

Edited June 16, 2017 by Porthos

[3cellhosting]

Hi there,

I have the same problem but do not have F-Secure

I have added the files as requested.

Regards

David

FRST.txt

Addition.txt

mb-check-results.zip

[Porthos]

41 minutes ago, 3cellhosting said:

I have the same problem but do not have F-Secure

Hi and welcome, Your issue is an old version of MB. installer_version" : "3.0.6

Let us get a clean install of the current version.

We a tool called MB-Clean which will automate the whole process for you.

 Tool can be found at https://downloads.malwarebytes.com/file/mb_clean

1. After downloading the tool run the tool.

2. The tool will automatically clean up the older possibly damaged installation and will ask you for a restart.

3. Restart your system and then the MB-Clean tool will prompt you to re-install the latest product.

4. Click on "Yes" to reinstall MB 3.×.

5. Now you will have the latest product installed.

Please let me know if you are still seeing issues after the latest product install.

 

[J5I]

Porthos, adding the exception to F-Secure settings resolved the issue.  I couldn't add it to the application exclusion tab, but was able to add it to the Object (folders) tab.  See the attached F-Secure exception screenshot.  Again, thanks for the quick response and resolution.

 

[Telos]

16 minutes ago, J5I said:

Porthos, adding the exception to F-Secure settings resolved the issue.  I couldn't add it to the application exclusion tab, but was able to add it to the Object (folders) tab.  See the attached F-Secure exception screenshot.  Again, thanks for the quick response and resolution.

 

You are in the right place. It is the Objects tab. FWIW, I excluded \Program Files\Malwarebytes instead to cover any future issue that may involve the higher level folder.