Well, I'm not affiliated with Eset or anyone else in the AV market, but I think I need to make this point. Yes, Eset screwed up -- what software company doesn't? But, what I feel is most important are two things: they admitted their error and fixed it within 2 hours. Now, will someone please make a list of the other companies out there about which you could say the same thing? Yeah, I can't think of any either. Mistakes heppen, they always will. And it will get far worse as Windows gets more (unnecessarily) complicated. The true test is how the vendor steps up to the issue and deals with it. After over a decade with Symantec Enterprise A-V we switched our 200+ computers to ESet Enterprise a few weeks ago (the rollout is still continuing as we have sites all over the state). Even with this flub my faith in Eset is not shaken and, judging by the last Symantec release (their "Endpoint Protection") I am still very happy with the decision to switch. And yes, the 3217 problem hit us too, but fortunately didn't do any damage that I could not repair in about 10 minutes. I do agree, though, that there should be some manner of temporary "fix" that the IT admins can do to stop a wayward update from klobbering files. I suspect that suggestion has already been made to Eset today!!!