What Happened With New Update?

[uffbros]

That was to be issued a week ago for the memory problem I and many others are experiencing? Thanks.

[noknojon]

Hi uffbros -

If you are refering to upping 1.42 to 1.43 then that is still being tested - It will not be released until it has had full tests and found to be 100% OK -

There is a lot more than just adding a number onto the versions - As of about 3 hours ago it was 1.42 / Version 3445 -

Thank You for your interest -

[uffbros]

Thanks

[sys-eng]

That was to be issued a week ago for the memory problem I and many others are experiencing? Thanks.

The new version is supposed to be released this week according to this post:

http://www.malwarebytes.org/forums/index.p...rt=#entry173789

In the meantime, I suggest closing Malwarebytes and ending the mbamservice in Task Manager. You will have to do this after each reboot though.

[noknojon]

Hi to both / all reading (and hoping) on this subject -

Field testing is under way as we speak - This must be fully completed prior to release to the public -

Re ; Your referals to the post from GT500 - He is also a part of the team who are testing and refining the update over the Christmas period -

Until then please wait for completed updates to be released -

Thank You -

[exile360]

The new version is supposed to be released this week according to this post:

http://www.malwarebytes.org/forums/index.p...rt=#entry173789

In the meantime, I suggest closing Malwarebytes and ending the mbamservice in Task Manager. You will have to do this after each reboot though.

Terminating mbamservice.exe through the Task Manager is a very bad idea and could lead to system lockups or crashes. It is not made to be stoppable while running. To properly keep it from running do the following:

Disable a Service on XP:

• Click on Start and click Run
  
• In the run box type services.msc and press Enter
  
• Once the Services window opens, scroll down the list until you find the MBAMService and double click on it
  
• Click the drop down menu next to Startup Type and select Disabled
  
• Click the Apply button and click on Ok
  
• Close the Services control panel
  
• Reboot your computer
  

Disable a Service on Vista:

• Click on the Start Orb and type services.msc and press Enter
  
• Click Continue at the User Account Control prompt
  
• Once the Services window opens, scroll down the list until you find the MBAMService and double click on it
  
• Click the drop down menu next to Startup Type and select Disabled
  
• Click the Apply button and click on Ok
  
• Close the Services control panel
  
• Reboot your computer
  

You can also open the Malwarebytes' Anti-Malware scanner (mbam.exe) and look under the Protection tab and uncheck the Start with Windows entry, that will not disable the service, but that will prevent error messages due to the tray icon trying to run when the service is disabled.

[TeMerc]

Release dates are always 'pending' as beta testing can and does occasionally pick up new bugs. That's why we test.

This is the nature of software and cannot be avoided.

We appreciate your patience as we try to deliver as bug free a version as we can.

[sys-eng]

You are correct. In this case, there is no service dependent on mbamservice.exe after exiting malwarebytes so it does not cause a problem. Since we don't know when the fix will be available, disabling the service is the best course of action.

[exile360]

The potential crash comes in when stopping the kernel level driver used by the service (MBAMProtector), I can vouch for the fact that forcing it down through the Task Manager does indeed cause lockups in some cases because I've had it happen to me . Disabling through the method I described and rebooting is the safe method to make sure no one else on this forum runs into the same problems I did.

[sys-eng]

I can appreciate application testing. I was an IT Project Engineer at BellSouth for 28 years. I do wonder though why this problem was not picked up in the testing of 1.42. I have several customers running Vista 32, and they all have this same memory problem.

Looking forward to the new version. Hope to see an e-mail notice announcing it. WIth the service disabled, it will not automatic update.

[exile360]

Interestingly enough, I never had this issue with the beta version of 1.42, it's possible that either it was modified before release or the definitions were altered slightly later on in subsequent updates, causing the escalation of memory usage. Either way, I too look forward to the releas of 1.43 .

[GT500]

Looking forward to the new version. Hope to see an e-mail notice announcing it. WIth the service disabled, it will not automatic update.

In the current version (1.42), and all previous versions, the automatic updates rely on the Windows Task Scheduler, and not on our own service.

Now 1.43 was supposed to contain a new scheduling system, but since it had to be a quick bugfix release (several bugs being fixed, and not just the memory issue) our developers were unable to incorporate the new features.

[marktreg]

Malwarebytes' Anti-Malware version 1.43 has been released. This is primarily a bugfix release, and fixes a number of stability and functionality issues in the previous release. If you had issues with 1.42, please let us know if 1.43 resolves them. The new version is available here.