About Us

The Immunet Blog is maintained by the Immunet team as a forum for discussing news and issues related to AntiVirus, security and cloud technology.

Search

Entries in update (2)

Thursday
Jan282010

Updaters are now available to migrate to 1.0.24

All,

The updater files for migration to 1.0.24 are now posted. The updaters will install the new product, uninstall old product if you have it and then load your new drivers. Migration can be done from any Immunet build from 1.0.14 up to current (1.0.24). You will be prompted for a reboot as we are replacing drivers with this install. Windows XP SP2 is not supported, only XP SP3 and up. Vista SP1 + and Windows 7 are also supported.

The Immunet Protect Beta 1.0.24 32 bit Updater is: Here
The Immunet Protect Beta 1.0.24 64 bit Updater is: Here

Next week or the week after we will be shipping 1.0.25 which is purely a bug fix release. We will also ship updaters for this coming build.

Friday
Jan082010

When should I update my Immunet Protect Beta?

Well, that’s a good question and not one that we have been clear enough about. This post will hopefully remedy that! Currently the Immunet Protect Beta has the ability to auto-update itself when it’s flagged from our cloud. We have not flagged an auto-update for the last 4 releases. If you are running Immunet Protect 1.0.18 or up there is no reason to manually upgrade at this point unless your trying to fix an issue and our Support group has asked you to upgrade. Our next release is 1.0.23, we’ll post and let you know our thoughts on that one as we get closer to it (it’s going into QA today). 

It’s important to remember that much of the functionality we build in (like our recent rollout of white listing) is driven from our cloud, not our desktop product. So often when we build new functionality you do not need to upgrade to take advantage of it. The same is true of many (but not all) of our virus detection technologies as well.

The reason we are not forcing people to upgrade (through our auto-update) feature is that we are trying to keep people in their builds as long as possible as long as they have no stability issues. This allows us to ‘persistence test’ over the beta period to watch how our software behaves in-field.

When we hit a point with our release schedule where we feel there is really protective (or stability related) benefit to people upgrading, we will perform an auto-update. This will certainly happen by April, quite possibly before. Once we pass out of beta (Immunet Protect 2.0) we will have fully scheduled update features, automated update etc. exposed in the product.

Cheers,

Al