Windows 2000 computer crippled by 3435 update

Windows 2000 users are unable to run any programs including opening My Computer after the 3435 update. They receive an error that they do not have the rights to do so.

Please advise as most of our users cannot use their pcs.

 

What permissions were modified?

 

Have a whole windows network here crippled by the same update, mostly XP machines. Hordes of permissions/loading errors. Only able to bypass by killing ESET service via local admin account the moment.

 

We have seen the same error on XP. Every app on some boxes are failing to start with a 0x00000022 error. It appears that disabling NOD32 cures the issue, at least temporarily. It looks as though something in the update is causing the problem.

 

By restarting the computer, Windows XP has been able to function again.

No changes were made in permissions on our end.

I did watch a computer go from working perfectly. Update ESET to 3435, and all of the errors started.

 

Same problem here! Windows 2000 machines and Windows XP machines are affected by this problem.

Who in their right mind released a virus definition file that kills computers? And I don't think this is the first time it has happened!

Someone please FIX IT!

Brett

 

Same issue here, many enterprise computers affected with the failing to start 0x00000022 error, all XP. Need a fix asap.

 

I'm not sure what the common theme is, but computers with NOD32 v2.7 are all fine after 3435.

XP Computers with SP2 and NOD32 v3.0.650 have been hit so far. They instantly stop being able to run programs after 3435 update.

At least 1 XP computer with SP3 and NOD32 v3.0.621 is still working fine.

All computers effected so far have had NOD32 v3, none with v2.7 are having any issues.

 

Upgrading to 3.0.672.0 seems to fix the lock-up problem with 3435 on one system, trying to deploy it to another now to see if the issue is resolved. Were using 3.0.657.0 previously.

 

But does it fix the problem because it downgrades the update to one previous to 3435 Or do they continue to work after re-updating to 3435 ??

 

I'm at 3.0.672.0/3435 and haven't noticed anything yet...

 

We have the version 3.0.657.0, and we are currently trying to upgrade to see if this is a solution.

 

This has got to be addressed. NOD32 doesn't push binary updates automatically. I can't be expected to visit hundreds of workstations to update them all every time a binary update is released... 650, 657, 672...

This is the third bad update in only a few months. These updates are costing countless HOURS of downtime for many users every time they cause issues.

Where is NOD32 even acknowledging that they are working on this? Why can't I roll back to a previous update easily when this happens? This has been asked for before.

 

I allowed it to update to 3435 from our update server, although I'm revising my position to 'fixes but slows the computer down immensely'. This could be due to domain controllers still running previous version (apparently botched). Both systems I've installed 3.0.672.0 on (with 3435) are faster after the first reboot.

 

I have 3 other PCs at 3.0.669.0/3435 and they too seem ok.

 

They are packaged as MSI files now. Why don't you just roll them out over the existing installs with Group Policy since it will keep the existing configuration settings?

 

Add my organization to the list. We have about 15 pc's down now. All xp prosp2-3 and 2ksp4, nod32 3435...

 

We're having success here pushing out 3.0.672.0 via the console to clients and then rebooting the clients (problem will not be resolved as far as I can tell until after a reboot), but some clients seem to be turning away the logon information randomly which is slowing the process down. I imagine that their systems are probably barking 0x022 errors about the installer or similar.

 

Same problem here, thanks ESET.

It happens only on machines running version < 3.0.672 with signature v. 3435.

A reboot did the trick ( in pushed out the new version right away to those machines)

 

Eset was called and knows about the problem. SUPPOSEDLY working on a fix. The "temporary" solution we came up with over here was to disable real time protection (which of course you can only do manually, the config file doesn't have permission to run). As a side note, I think Eset is based out of Afghanistan....9/11 v. 3435?

 

This is absolutely ridiculous. I have ~150 PC's down and I have to manually disable real time protection until I can get the msi distributed? Refund please.

 

The config file will "run" if you reboot after sending it out. So the easiest temporary fix is to edit your config to turn off real-time scanning. Then go ahead and reboot the computer after the user has received the new configuration.

 

Surely that's not meant to be funny

 

Count me as affected as well. I haven't noticed any desktop problems. HOWEVER, I have a Windows 2008 server which began crashing after receiving this update. Disabling AV has temporarily fixed things.

Meanwhile, at about the same time, my NOD32 server is showing "Virus signature DB: Unknown." I have no idea what to make of that. Hopefully right now ESET isn't making any updates available until they fix this.

For what it's worth, we're running 3.0.650.0 and the affected server is an x64 box.

 

Add us to the list. More than half of the computers in our office (20ish) stopped cold the minute 3435 was applied. Weird errors, as if they didn't have NTFS permissions to their own hard drives (the entire drive), even people who are administrators on their computers. Disabling NOD32's virus protection or, if necessary, disabling the ESET services in MSCONFIG and a reboot brought them back up immediately.

All affected PCs are XP SP3 running NOD32 3.0.657.