3 replies to this topic

[1PW]

Hello to all:

If the beta tester has v1.44 installed, prior to trying v1.45b, the disposition of any v1.44 Windows Scheduled MBAM Tasks should probably be discussed in terms of possible conflicts with the new Scheduler feature in v1.45b

I uninstalled MBAM v1.44 using the Revo Uninstaller and followed with mbam-clean.exe. I received the following error message after the uninstall while running mbam-clean.exe: "SHGetValue failed with error code 0" A reboot was executed as directed.

The download, install, and registration of my previous Product ID and Key were all uneventful.

V1.45b's MBAM database did not update passed 3907 while I tested.

A manual quick scan, followed by a full scan, took run times quite similar to previous versions and were uneventful. The hardware I beta tested with runs a fully legal XP3 Pro on a 2 GHz x86-32bit mobo w/2Gb of ram.

The new Scheduler feature is very easy to use and should satisfy most users. I have setup Scheduler tasks to update and scan quick & full.

Well done folks!

[noknojon]

Hi 1PW -
If all testing is now finished please run the un/reinstall tool to get the "normal" version back on line - Unless you wish to test it again -
There may be one more BETA to test prior to the release so you will need to remove your current BETA -
To Fully Remove and Reinstall a Fresh New Copy of Malwarebytes - Read Carefully
Windows XP:

• Click on Start and select Control Panel
  
• Open Add/Remove Programs
  
• Uninstall Malwarebytes' Anti-Malware
  
• Restart your computer very important !
  
• Download and run mbam-clean.exe from here

It will ask to restart your computer, please allow it to do so, very important
After the computer restarts, temporarily disable your Anti-Virus and install the latest version of Malwarebytes' Anti-Malware from here
Note: You will need to reactivate the program using the license you were sent via email if using the Pro version only -
Launch the program and set the Protection and Registration. Then go to the UPDATE tab if not done during installation and check for updates.
Restart the computer again and verify that MBAM is in the task tray if using the Pro version. Now setup any file exclusions as may be required in your Anti-Virus/Internet-Security/Firewall applications and restart your Anti-Virus/Internet-Security applications. You may use the guides posted in the FAQ's here or ask me and I'll explain how to do it.
Windows Vista and Windows 7:

• Click on the Start button and select Control Panel
  
• Click on Programs and Features
  
• Uninstall Malwarebytes' Anti-Malware
  
• Restart your computer very important !
  
• Download and run mbam-clean.exe from here

It will ask to restart your computer, please allow it to do so, very important
After the computer restarts, temporarily disable your Anti-Virus and install the latest version of Malwarebytes' Anti-Malware from here
Note: You will need to reactivate the program using the license you were sent via email if using the Pro version only
Launch the program and set the Protection and Registration. Then go to the UPDATE tab if not done during installation and check for updates.
Restart the computer again and verify that MBAM is in the task tray if using the Pro version. Now reset any file exclusions as may be required in your Anti-Virus/Internet-Security/Firewall applications and restart your Anti-Virus/Internet-Security applications.
You may use the guides posted in the FAQ's here or ask me and I'll explain how to do it.
Thank You -

[1PW]

I am now noticing that if the new MBAM integral scheduler has been requested to run a scan, that scan can not be paused like the previous version's scans were. Of course the scheduler can do the new flash scan.

Personally, I know a skilled user could run multiple updates and either scan type with the Windows Scheduled Tasks and make multiple scans with the previous version (v1.44) even with days of the week limitations. Now I see that we may have sacrificed some vision and control in this new version. I believe we were better off before, and if the flash scan could be included as a Windows batch job feature, the new scheduler is not needed.

I suppose I could have made do with the addition of "/flashscan" and "/flashscanterminate" Command Line Parameters instead.

If the new scheduler fails to run a scheduler scan or update, I'm not sure sufficient diagnostic information would be provided to troubleshoot with.

Am I missing something here?

I believe I'll continue to test this version at length though.

[exile360]

Hello

If you review the protection logs, it does indeed indicate whether a scheduled scan or update was executed successfully or not.