Safe to run 4.0.424.0????

1-Since it is ESET policy to NOT contact/suggest old/current clients to upgrade to their latest version - and
2-Since there have been no notices since before 3.0.650, where I am now -and
3-Since the latest version is 4.0.424.0 with Consumer Reports giving ESET their highest rating [who knows what version?], then

Can someone tell me if it is now "safe" to upgrade BASED ON WHAT I AM RUNNING Any comments will be appreciated.
Jim

PS I can only run DialUp at 40k as nothing else is available here in the boonies.

 

there's some issues that some people are expericening with internet connections in v4, I'd wait...

 

Those issues were fixed on 03/31/09

March 31, 2009 - 4.0.417
Fixed several issues in firewall module:
Detection for Conficker added
Fixed detection of TCP stream
Fixed detection of binary rules in ipv6
Fixed BSOD on Vista caused by entering mapped drives
Removed potencial deadlock during Windows log on process
Fixed detection for DNS cache poisoning attack
Fixes and changes in ICMP filtering
Fixed scanning of ARP
Fixed issue with disconnecting of routers and data transfer cards from internet
fixed: protocol filtering (correct displaying on list of certificates)
fixed: Settings of scanning size (GB) within archive is displaying correctly

Click Below to read the changelog
http://www.eset.com/joomla/index.php?option=com_content&task=view&id=4113&Itemid=5

 

There are still too many issues with ver4 that need to be resolved before it can be classed as working properly.

 

I've got 4.0.424 running really good on my system.

Nice improvement from the earlier .314 and .417 builds.

No more Application popups during shutdown, Dllhost.exe shuts down after starting the Windows Update/Automatic Update Service.

Still, just one little hair out of place with the ESET Service:

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 5/4/2009
Time: 1:28:25 PM
User: NT AUTHORITY\SYSTEM
Computer: flskjkajdjadljfjjti
Description:
Windows saved user fialkjfadf adf adfad\dodododod registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Maybe they'll even have that worked out in a couple of more new builds.