2.0.2 Upgrade - An Observation during Installation

[Tabvla]

.

Product  :  MBAM Premium upgrade from 2.0.1 to 2.0.2

 

I have recently upgraded several machines from 2.0.1 to 2.0.2.  In each instance I logged-in as the Administrator and ran the same downloaded Installer.  All runs installed without any issues.  However, I noted the following differences, even when the platforms were almost identical.

 

1.  At the start of the install : On some installs the Installer first terminated the currently running instance of MBAM and then performed the install.  On some installs it did not do this.

 

2.  At the end of the install :  On some installs the installer requesed a system Restart.  On some installs it did not ask for this.

 

I am trying to get my head around these differences. 

 

At the start of the install one may assume that the code in the Installer will at the outset look for an existing instance of MBAM.  If it finds such an instance it takes some pre-coded action.  It is difficult to comprehend why the action would sometimes terminate the current instance and sometimes not.......

 

At the end of the install one may again assume that the code in the Installer should request a system Restart - this would be normal practice with any software of this type.  So why would the Installer code be written in such a way that it sometimes requests a system Restart and sometimes it doesn't.......

 

No, I am not half-asleep..... I have already had two cups of Java this morning.

 

T.

 

[Firefox]

Hello and welcome back...

 

I am not on the staff or the development team, but if I had to guess its probably due to the settings that were set in Malwarebytes on each computer that may be different, especially if they had the option "Explorer context menu entry" set to Yes.

 

For best performance I always reboot my computer after I install new/updated software.

[Tabvla]

Hi Firefox, thanks for your feedback.

 

And of course I agree, when installing any type of new software or major version update a Restart is compulsory.  For those who are technically experienced that would be an automatic thing to do.  My concern is that there are surely many users of MBAM who have little or no technical ability and would not necessarily take that last step - which means that the step may never be taken

 

I have found that many users never Restart their computers.  At the end of the day they simply put them on Standby.  Those who work from laptops (which are now the majority) simply close the lid.

 

And...... I still cannot get my head around why the Installer would have this type branching code at the outset and conclusion of the install.  Why would  a developer even write that branch into the code - it does not really make much sense.

 

As for your insight with respect to the "Settings" my assumption would be that the User Preferences (or Settings) are kept in a separate file and that these would only be applied after the new updated version was installed.  Perhaps the MBAM develpers do things differently but that is how I would have written the code.

 

T.

 

[daledoc1]

 

And...... I still cannot get my head around why the Installer would have this type branching code at the outset and conclusion of the install.  Why would  a developer even write that branch into the code - it does not really make much sense.

 

Neither Firefox nor I am an employee or developer.

 

However, it is my understanding from a post by the MBAM Product Manager a while back, during beta testing, that one reason that the contextual scanning option (aka "right click context menu scan") option was disabled by default in version 2, was so that many end users who do not use the feature could perform minor in-place program updates without a restart requirement.

Those users who DO have that feature enabled will have to reboot after program updates, because Windows cannot update that file while it is in use.

 

Having said that, as Firefox mentioned, a system restart before -- and certainly AFTER -- a software upgrade is always a good idea or "best practice".

 

Hope this helps,