TESTING Malwarebytes 3.0.6 CU4 -- BETA Preview

[TempLost]

Just to say that I've been testing the latest BETA Preview 3.0.6 CU4 which I installed over the top of 3.0.6.1469 Component Version 1.0.75 and all seems to be running well. A scan still sees the CPU running at 100%, but I guess that will be addressed in later releases

I was previously running Malwarebytes Premium 3.0.6.1469 Component Version 1.0.75 which also ran well with the exception of occasional loss of a Real Time Protection module which could be fixed by restarting Malwarebytes or a reboot.

Windows 7 Home Premium SP1 x64
Malwarebytes Premium 3.0.6 CU4 -- BETA Preview
Avast Free 17.2.2288
CryptoPrevent 8.0 Premium
Tweaking.com Windows Repair Pro 3.9.27 (incorporating Registry Backup 3.5.3) 
Casper 10 Backup

Edited March 25, 2017 by TempLost
added info

[syrob]

No luck here same setup as yours, install wanted to restart first, old MB STILL THERE...

[syrob]

Tried again, ontop install, multiple cant write file errors, ignore , finaly aborted as there were to many

 

CU4 NOT working as an upgrade

[TempLost]

21 minutes ago, syrob said:

Tried again, ontop install, multiple cant write file errors, ignore , finaly aborted as there were to many

 

CU4 NOT working as an upgrade

Have you tried uninstalling and reinstalling? If that doesn't work, uninstalling and then using the Malwarebytes mb-clean tool to get rid of all traces of the previous installation before re-installation should work.

 

[Porthos]

1 hour ago, TempLost said:

A scan still sees the CPU running at 100%

This on a MANUEL scan might not change to keep in line with fast manual (A welcome change) scanning but the big one I hope for even thouh it has no noticeable effect on any of my computers is to use low priority scanning even lower than it is now for scheduled scans.

If you open MB to scan you should not be doing anything else, that is what scheduled scans are for.

[Porthos]

45 minutes ago, syrob said:

CU4 NOT working as an upgrade

Re read the instructions.

If you have an earlier version of Malwarebytes 3.0 installed, please uninstall it first and then install this new version.  Typically with these "bundled" installers for testing a clean install seems to work best.

Edited March 25, 2017 by Porthos

[syrob]

Hi,

Uninstalled CU3 through control panel, installed new CU4, CU4 did not remember old licence so had to use up a new one, (ugh thought it would remember license number)

Any way so far so good.

Observation, after putting in license tales about a minute for all protections to turn on, will rushing it and manually attempting to turn them on be the cause of some of the issues on earlier versions? i.e. if you wait one minute you will be good, v.s. immediately going into settings and forcing on manually, where issues will then occur?

Edited March 25, 2017 by syrob

[TempLost]

1 hour ago, Porthos said:

Re read the instructions.

If you have an earlier version of Malwarebytes 3.0 installed, please uninstall it first and then install this new version.  Typically with these "bundled" installers for testing a clean install seems to work best.

Oops! Yes, I should have done a clean install also, but failed to read the instructions in my excitement at having a new version to play with. However, still running without problems

 

1 hour ago, Porthos said:

This on a MANUEL scan might not change to keep in line with fast manual (A welcome change) scanning but the big one I hope for even thouh it has no noticeable effect on any of my computers is to use low priority scanning even lower than it is now for scheduled scans.

If you open MB to scan you should not be doing anything else, that is what scheduled scans are for.

I'd turned off scheduled scans previously because I assumed it would slow my laptop down too much if it started to scan while I was doing something else - I was just testing scan to make sure it completed OK.

[Porthos]

1 hour ago, syrob said:

will rushing it and manually attempting to turn them on be the cause of some of the issues on earlier versions?

Also I reboot after install even since the program does not ask(I believe it should be required anyway.)

Edited March 25, 2017 by Porthos

[Porthos]

4 minutes ago, TempLost said:

I'd turned off scheduled scans previously because I assumed it would slow my laptop down too much if it started to scan while I was doing something else - I was just testing scan to make sure it completed OK.

The back ground scans are not really noticeable in most cases. BUT if you have a lower than a dual core and less than 4 gigs (witch I have always considered bare minimum for any Windows after  XP)  of ram I could understand the visible drain on those systems. This includes any (In my own personal opinion) any computer with less less than Win 7 that came that way so to speak. 

Also I set the scan schedule for Dally hyper scans and threat scans only once per week. And the threat scan is set to recover if missed at 23 hours which will make it basically run the scan at the next reboot after after it is missed making THAT boot and the first several minutes of operation slower. But I set all scans at a time when I know the computer will be on and awake.

I never realize a scan has even run till the much hated pop up stating the scan has completed shows. I learn to expect them and is a clue if I don't notice for a couple of days to check program status.

 

 

 

 

 

[TempLost]

1 hour ago, Porthos said:

The back ground scans are not really noticeable in most cases. BUT if you have a lower than a dual core and less than 4 gigs (witch I have always considered bare minimum for any Windows after  XP)  of ram I could understand the visible drain on those systems. This includes any (In my own personal opinion) any computer with less less than Win 7 that came that way so to speak. 

Also I set the scan schedule for Dally hyper scans and threat scans only once per week. And the threat scan is set to recover if missed at 23 hours which will make it basically run the scan at the next reboot after after it is missed making THAT boot and the first several minutes of operation slower. But I set all scans at a time when I know the computer will be on and awake.

I never realize a scan has even run till the much hated pop up stating the scan has completed shows. I learn to expect them and is a clue if I don't notice for a couple of days to check program status.

 

 

 

 

 

I have a minimal P6100 processor in my laptop for reasons of economy and because I don't run any really demanding programs (and no games), but I jacked the memory up to 8 GB, which helps. I've avoided a setting that might run a scan at startup because Registry Backup runs at the first boot of any day that I use the laptop, and that IS quite processor intensive. But I'll probably follow your example on scanning scheduling if the option to reduce processing priority appears in Malwarebytes 3.0. Thanks! 

[TempLost]

17 hours ago, TempLost said:

Just to say that I've been testing the latest BETA Preview 3.0.6 CU4 which I installed over the top of 3.0.6.1469 Component Version 1.0.75 and all seems to be running well. A scan still sees the CPU running at 100%, but I guess that will be addressed in later releases

I was previously running Malwarebytes Premium 3.0.6.1469 Component Version 1.0.75 which also ran well with the exception of occasional loss of a Real Time Protection module which could be fixed by restarting Malwarebytes or a reboot.

Windows 7 Home Premium SP1 x64
Malwarebytes Premium 3.0.6 CU4 -- BETA Preview
Avast Free 17.2.2288
CryptoPrevent 8.0 Premium
Tweaking.com Windows Repair Pro 3.9.27 (incorporating Registry Backup 3.5.3) 
Casper 10 Backup

UPDATE: Just to add that I booted up the laptop this morning to check the settings again and found that Enable Self Protection Module Early Start was switched OFF and I was not able to change the setting. I'm not absolutely sure that it was switched ON after my reinstall of the BETA over the last version, but I think it was

I deactivated my registration, uninstalled BETA Preview 3.0.6 CU4, rebooted, reinstalled it, entered my registration details and was then able to change Enable Self Protection Module Early Start to ON. Everything else seems to be working as expected.

Just goes to show that I should have probably followed instructions and uninstalled the old version first 

[TempLost]

I can also confirm that I now seem to get consistent behaviour when visiting http://iptest.malwarebytes.org/- I get the warning from the Malwarebytes program and then am redirected to this page https://block.malwarebytes.com/