NOD32 4.0/Vista SP2 Fix Finally In

TechLarry

RIP [H] Brother - June 1, 2022
Joined
Aug 9, 2005
Messages
30,481
Update module released to resolve compatibility between ESET Smart Security and ESET NOD32 Antivirus 4.0 and Service Pack 2 for Windows Vista and Windows Server 2008
News ID: NEWS35|Last Revised: June 04, 2009

Problem

The ESET icon next to the system clock turns red after installing Service Pack 2 for Windows Vista or Windows Server 2008.

We have received reports that, in some instances, Service Pack 2 for Microsoft Windows Vista and Microsoft Windows Server 2008 conflicts with ESET Smart Security 4.0 and ESET NOD32 Antivirus 4.0, causing the ESET icon next to the system clock to turn red and notifying users that maximum protection is not ensured. The conflict results in the real-time file system protection in both programs and the Personal firewall in ESET Smart Security being disabled when the computer starts.

Resolution

A fix for affected systems has been released as an update module. The updated module will be downloaded automatically when a virus signature database update occurs in ESET Smart Security and ESET NOD32 Antivirus.

After the update is downloaded, the entry for the Anti-Stealth module in the About window for ESET Smart Security and ESET NOD32 Antivirus 4.0 will appear as Anti-Stealth support module: 1012 (20090526). The update is also installed if your Anti-Stealth module has a newer version or release date.

Please read the frequently asked questions below if you have been affected by this issue. If you had previously disabled the Anti-Stealth and Self-Defense options in your ESET security product, please click here for instructions on re-enabling these options.


FAQ

Which ESET security products are affected?
All 4.x builds of ESET Smart Security and ESET NOD32 Antivirus are affected. ESET Smart Security 3.0, ESET NOD32 Antivirus 3.0 and ESET NOD32 Antivirus 2.7 are not affected.


When will a fix for ESET Smart Security 4.0 and ESET NOD32 Antivirus 4.0 be available?
The fix was released as an update module, distributed via automatic virus signature database updates, the morning of June 4, 2009.


How is the fix being delivered?
The fix is delivered via normal update channels, which means it is downloaded and installed automatically by all copies of ESET Smart Security 4.0 and ESET NOD32 Antivirus 4.0, without any need for a computer restart or user intervention.


Which operating systems are affected?
Microsoft Windows Vista and Microsoft Windows Server 2008 with Service Pack 2 are affected. RTM and SP1 versions of these operating systems are not affected. Microsoft Windows 2000 and Microsoft Windows XP are not affected.


Why did it take so long for a fix to be made available?

Low-level changes made to the Windows Vista and Windows Server 2008 operating system kernel by Service Pack 2 introduced an incompatibility with how the internal modules of ESET Smart Security/ESET NOD32 Antivirus 4.0 interface with the operating system when the computer starts. Because the issue does not occur in a consistent fashion, it was difficult for ESET's test engineers and developers to reproduce the issue and then identify the underlying cause. As soon as it was identified, ESET developed a fix.
Product/Beta Release
 
I see one problem. On a lot of systems (including my own) affected by this issue with NOD32 4.0 and Vista SP2, the update system is broken.

How the hell do you get the update if the update system is broken?

There is no released full installer that contains the fix, which is stupid.
 
Back
Top