'Automatically upgrade to new versions' option not keeping software up to date

[sethf2015]

The 'Automatically upgrade to new versions' option is not keeping the software up to date.

 

Latest available download of MBAE is version 1.07.1.1015, however installed version of MBAE still shows 1.06.1.1019 even though 'Automatically upgrade to new versions' is checked.

[axe0]

In a week or two they'll start activating the automatic upgrades, so if you prefer not to do anything, simply relax and wait for your MBAE to upgrade itself.

[sethf2015]

Does anyone know if there is a standard length of time or delay between which a new version in made available for download, and the software will automatically upgrade to that new version?

 

Normally I would expect this to take place immediately, and am concerned that several _weeks_ are being allowed to lapsed before clients upgrade themselves.

[ky331]

1.07.x has gone through several BETA releases, as it was being tested for bugs.   They want to be reasonably sure a version is sufficiently stable, before pushing it out via automatic updates.   Typically, the wait lasts a week or two [once they believe they have something viable to offer].   Users who don't want to wait can manually download either a Beta or "semi-stable" release whenever they wish.

[rwharold]

REQUEST REPLY BY MBAE EMPLOYEE!

 

The MBAE "Settings" check marked "Automatically upgrade to new versions" settings option in MBAE has NEVER, EVER worked for ALL your previous versions. Fortunately, I have the program named: " File Hippo App Manager" which constantly automatically checks for updated versions of all my installed programs. Fortunately, File Hippo, alerted me this morning that a new version of MBAE, 1.07.1.1015, was available for download and installation. I clicked on the "download and install" button, and now have this new version of MBAE installed and active. CAN YOU PLEASE EXPLAIN WHY, WHY, WHY, YOUR AUTOMATICALLY UPGRADE OPTION NEVER, EVER, WORKS????????

[pbust]

It does work. In fact the vast majority of upgrades between versions happen via the automatic upgrader channel. But as mentioned above we typically wait a few weeks between release of a new version in the website (for new downloads) and release of the same version in the auto-upgrade channel. We do this in order to make sure we did not miss anything major during QA before we deploy a mass upgrade to the entire user base.

 

In fact in order to verify that the auto-upgrade does work, you can downgrade to a 1.05 version and you will see how the auto-upgrades work.

 

Of course if you have disabled the auto-upgrades or are somehow blocking connections from MBAE to the Internet, the feature will not work.

[rwharold]

Thank you Staff Moderator. I know for a fact that I have NOT disabled the auto-upgrades or that I am somehow blocking connections from MBAE to the Internet. Your statement that I would have to wait a "few weeks" for the auto update to work, seems to me to be absolutely ridiculous! It is a very poor corporate "policy" that makes loyal unwitting customers subject to certain, previously unknown new exploits, that the "new improved version of MBAE that has been updated to detect and block them. In such cases, IMMEDIATE update action is required, not in a "few weeks" or so! That is just my PERSONAL opinion. Fortunately I have the File Hippo App Manager program which satisfies my desire to be as up-to-date as possible for ALL of my installed programs. I am "almost" sure that my frustrations that I have expressed about your corporate policies, won't change, but at least I am on record for others to read and comment.

[pbust]

Thanks for your comments.

 

It is in fact a very widely used policy to not auto-upgrade immediately after a release. In most cases the auto-upgrade will be enabled only be a few days after release for new downloads, unless of course a bug gets reported that we think is important to fix before the massive upgrade. Such was the case with MBAE 1.07. A few users reported some crash conditions under Chrome and we felt this was an important thing that needed to be fixed before putting all our users at risk of crashing their browsers. The MBAE build 1015 released two days ago finally fixes this issue and will be released to auto-upgrade on Monday (i.e. only 3 business days after release to new downloads).

 

In terms of risk of exposure to new/unknown exploits, this is minimal due to the way that MBAE's techniques work (i.e. non-signature proactive approach).

 

Our policy in this regards will not change in the short term. However the discussion is good as there might be alternative solutions like for example a "update to available beta versions" feature which is something that many third-party applications use.

[daledoc1]

Hi, rwharold:
 

but at least I am on record for others to read and comment.

 
The auto-updating works just fine.
 
As has been repeatedly stated, new builds are released gradually, to test for stability and other issues.
This is the norm in the software industry, and is sometimes referred to as "beta-testing".
A "beta" build may NOT be as stable as one that is approved for general release.
 
The process here for MBAE builds, whether they are formally designated as a "beta" or not -- which is quite reasonable -- is to release new builds via a special, manual download link first.
Then, soon after, they are made available via the standard download link.
Then, soon after, they are made available via the auto-updater.
This is accompanied by in-house testing along the way.
 
As mentioned, you are always welcome to download the latest build as soon as it becomes available from the link that @pbust posts for such announcements.
That way, you need not wait to get the final, stable, general release build via the auto-updater.
However, in such cases, one must reasonably expect that such early or beta builds may very well be replaced soon thereafter by others that are more stable, as was the case with MBAE 1.07.1.x.
It's your choice.
 
No matter what, NO software program -- neither MBAE nor MBAM -- can guarantee 100% protection for any computer.
The most important part of computer defense is the component between the chair and keyboard.
 
 
Cheers,

[rwharold]

Staff Moderator.

 

Thanks for your comments.

 

It is in fact a very widely used policy to not auto-upgrade immediately after a release. In most cases the auto-upgrade will be enabled only be a few days after release for new downloads, unless of course a bug gets reported that we think is important to fix before the massive upgrade. Such was the case with MBAE 1.07. A few users reported some crash conditions under Chrome and we felt this was an important thing that needed to be fixed before putting all our users at risk of crashing their browsers. The MBAE build 1015 released two days ago finally fixes this issue and will be released to auto-upgrade on Monday (i.e. only 3 business days after release to new downloads).

 

In terms of risk of exposure to new/unknown exploits, this is minimal due to the way that MBAE's techniques work (i.e. non-signature proactive approach).

 

Our policy in this regards will not change in the short term. However the discussion is good as there might be alternative solutions like for example a "update to available beta versions" feature which is something that many third-party applications use.

Staff Moderator.

 

Thank you very much for your lucid reply. Your final statement: "there might be alternative solutions like for example a "update to available beta versions" feature which is something that many third-party applications use." That would be MOST desirable, and I, and am  sure many others, would greatly appreciate that option. I will look forward to your possible consideration.

 

Best regards,

 

Richard Harold

[sethf2015]

Richard, as a troubleshooting measure, try disabling Windows User Access Control (UAC) and then restarting your computer to see if MBAE autoupdates from 1.05 to 1.06.

 

I've had issues in the past with other software failing to autoupdate due to UAC.

[pbust]

MBAE checks after boot and then periodically thereafter for new versions. Try leaving the #2 computer up and running for about 12 hours and it should upgrade.

[pbust]

Yes good point! We'll add that to 1.08.

[ky331]

I'd like to make a request for an option for the "opposite" feature:  to be able to disable the update prompt if one so desires.

 

Sometimes, I intentionally uncheck the box to "Automatically upgrade to new versions" (because I'm still testing, or happy with, the version I have installed).  When the new version is made available to the program's updater, I get prompted each time I boot up the system, and so have to repeatedly decline it.

 

To give you a practical example, I see from another thread that some people are having an issue with x.1015 traybar not displaying the protection "balloons".  I've encountered that issue on my 8.1 tablet, and so have regressed, intentionally, to x.1010 which still works just fine.   [interestingly, I'm okay running x.1015 on my Win7x64 system.]   But it gets to be a nuisance to have to repeatedly decline the update offer every time I boot up the system.

 

So my suggestion, is that you allow the user to select between:

1) automatically update me when a new version is available

2) notify me when a new version is available

3) do not check for updates -- I want to do so manually