John A

Then why are my 4 installations at 1.0.40?

My beta 3.0.4.1269 is exactly the same size as the current release 3.0.4.1269

Thanks for reporting the results.

Just out of interest, if you start Malwarebytes manually after Windows startup, do you still get the error? Turn off "Start Malwarebytes at Windows Startup" in Settings > Protection

KB3201845 Cumulative update has been causing internet connection issues, may be relevant. Reboot seems to fix it. Happened to my desktop https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/problems-connecting-to-the-internet/f121306e-fab5-411d-833f-e4490ecb8b5c

I have Malwarebytes set to start at login, not Windows startup, and still get this error occasionally.

Mine are 1.0.40, 1.0.688

I ask because it caused my systems to freeze See

Do you have mbamservice.exe added as a Process exclusion in Defender settings?

In Malwarebytes > Settings > Application, try changing the Windows Action Centre to "Never register Malwarebytes in the Windows Action Centre" Restart and see if Defender starts

Windows 10 Current release, Defender I don't often use IE but the last two times I have it has crashed when I try to close it. Event details below. Unsure if this is related to Malwarebytes 3 but I don't recall this happening before. Logs attached Log Name: Application Source: Application Error Date: 11/12/2016 6:29:52 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: PC Description: Faulting application name: iexplore.exe, version: 11.0.14393.0, time stamp: 0x57899953 Faulting module name: IEFRAME.dll, version: 11.0.14393.479, time stamp: 0x58258af8 Exception code: 0xc0000005 Fault offset: 0x000000000015ac81 Faulting process ID: 0x2160 Faulting application start time: 0x01d253145b132681 Faulting application path: C:\Program Files\Internet Explorer\iexplore.exe Faulting module path: C:\WINDOWS\SYSTEM32\IEFRAME.dll Report ID: 262fca31-b9bb-4931-a9cb-327cd52de169 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-12-10T19:29:52.490811000Z" /> <EventRecordID>32556</EventRecordID> <Channel>Application</Channel> <Computer>PC</Computer> <Security /> </System> MBAMSERVICE.zip

In Malwarebytes > Settings > Application, try changing the Windows Action Centre to "Always register Malwarebytes in the Windows Action Centre"

I had this issue during beta testing. If you are experienced with editing the Windows Registry, and you can restore it if something goes wrong ... Uninstall all Malwarebytes products Restart Start RegEdit Locate each incidence (I only had one) of the Registry key "ESProtectionDriver", delete the key. You can find it by searching for mbae64.sys (or mbae.sys for 32 bit systems) Restart and install Malwarebytes 3. Acknowledgement to share3141

I'm running 3.0 on Windows 7 with MSE uninstalled at present - works fine. Malwarebytes takes a few minutes to start up but this is a very slow computer.

See point 2 here

See point 2 here

Current release Windows 10 Defender I start Malwarebytes at login, not Windows Startup to avoid an issue with Windows user profiles. - Turned off "Start Malwarebytes at Windows startup" - Added the MB shortcut to C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup System runs well until I add the following "Process" exclusion to Defender: C:\Program Files\Malwarebytes\Anti-Malware\MBAMService.exe On restart, after Malwarebytes UI appears (sometimes earlier, sometimes after the UI is initially closed), Windows totally freezes, only way to restart is to force power off using the power button. I can easily reproduce this on two computers. To recover: Start Windows in Safe Mode Delete Malwarebyres startup entry Start Windows normally Delete MBAMService.exe process from Defender exclusion list Add the MB shortcut to C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup again Restart Windows All good Note: Excluding other Malwarebytes processes from Defender does not cause this issue.

We don't know what has happened yet. We will have to wait for a statement from Malwarebytes staff.

If you have IBM Trusteer Rapport installed you need to disable either Trusteer or MBAE until the issue is sorted out

Do you have IBM Trusteer Rapport installed? If so disable either MBAE or Trusteer until Malwarebytes corrects this issue.

There is no update, there was a problem at Mlawarebytes server end. As Battlefists suggests, uninstall MBAR, restart computer, reinstall MBAR and the problem will be fixed.

Interesting. Until Malwarebytes staff respond with a fix, you need to disable either Trusteer or MBAE

Sorry, the latest version has the same issue, I meant that the developers should update (fix) it in a future version.

Zaffy, there are plenty of others now who have submiited logs so don't worry about it unless a Malwarebytes staff member requests it. For future reference, you don't get at the logs via MBAE, you do the following: Open File Explorer Tick the View option to show "Hidden items" Navigate to the folder C:\ProgramData\Malwarebytes Anti-Exploit Select all the files in that folder (CTRL A) Right click on the selection area and choose Send to > "Compressed (zipped) folder" You will see a new folder appear that has an icon with a zipper on it Attach that file to a forum response here Meanwhile, do you have IBM Trusteer Rapport installed? It appears that this may be causing a conflict with MBAE.

Very useful, thanks. However Malwarebytes Anti-exploit should be updated to use an alternative Help system.