Discussion in 'ESET NOD32 Antivirus' started by yongsua, May 8, 2011.
Is pre-release update really that bad?Thanks.
The way it is written sounds band for them. Had no probs with Eset pre-release(s) which must be implemented differently
I think they are refering mainly to PCU
Just to clarify something. Eset doesn't release a beta/pre-release unless they've tested it and have fixed the major bugs and bugs that might **** up your system.
Many ESET users run pre-release updates without any ill effect, including myself.
They are thoroughly tested before they are release for public consumption.
The avast pre-release updates are whole new program versions, Eset's are just individual program modules, and are better tested before releasing.
Hi,Guys.Thanks for the replies.
Just to add a quick followup/summary, how each antimalware vendor deploys and tests prerelease software and updates is going to vary based on the vendor, the product and even individual updates.
The recommendation of having a backup and recovery strategy by Avast! is an excellent one, actually, however, I would extend that to say it should cover production systems as well: The old saying, "If you don't have any backups, than the data must not have been important." comes to mind. If you have any data that is valuable (which is to say, unique and not available elsewhere) than you should have multiple backups of it. There are plenty of things which can happen to a computer beside a bad beta build, like a hard disk drive failing, computer getting stolen and so forth.
Are there any new pre-release at this moment?
You must enable pre-release updates to determine this. If they were previously disabled in your configuration, you would obtain these available updates. Export your settings before taking this opt-in action.
You may copy and paste your system information to a text file for comparative purposes.
Separate names with a comma.