Beta 4 morphed into a virus...

...at least it manifested several characteristics of a virus...gets into the OS and won't get out, unable to delete files, still functions after you thought you had deleted it, gets all intertwingled with the OS...

But seriously, I was very surprised and quite irritated at what happened tonight. I decided I would install the release candidate and I would do so after I uninstalled the previous beta 4 version. When I deliberately delete something I want it gone - I don't want any vestiges hanging on for the ride. What happened is after I uninstalled it, the eye in the task bar was still there telling me that I was unprotected...no kidding Dick Tracy. I rebooted the machine and when it came back up there was the eye...what this about? I tried deleting some hangers on files but was denied access. So, I went into safe mode and deleted everything I could find in the registry relating to NOD32, eset, and ekrn - this took about 30 minutes. I rebooted thinking to myself - that bloody eye better not be there staring at me now - it wasn't - so I then installed the RC without a hitch and everything is working fine.

BUT...why did ESET put me through this...how do you justify refusing to vacate the premises when I say begone!...that's just not right.

 

It doesn't, at least not normally. You're the first person I've heard of that's gone through this, are you sure the uninstaller completed successfully?

 

It completed as best as I could tell... I forget the exact wording but the last dialog box indicated the uninstall had completed and I clicked the finish button which seemed to work OK.
If something strange is going to happen it will happen to me.

 

Hello,

Please keep in mind that you are not using a production release of ESET's software, but rather upgraded from a beta test version to release candidate version. To quote from ESET's beta test portal at http://beta.eset.com/:

If you are uncomfortable with testing non-production code, then you may wish to install the production version of the software, v3.0.684.0, and use that until v4 is released.

Regards,

Aryeh Goretsky

 

I understand and accept that knowing full well that operational problems can and do occur with beta software...what I didn't understand is that it would have been so difficult to completely remove it should any problems actually occur. Maybe I missed the words to the effect that uninstalling could be a problem...In my opinion if nothing else is fully functional in beta software at least the ability to remove it should be.

Obviously it's no big issue with me as I was able to remove it on my own to my satisfaction and then went ahead and installed the RC but it is something that I think should be hi-lited for those less inclined to work around possible uninstallation problems.

 

Did you know that Norton and mcafee have released tools too properly uninstall their software and there final versions!!!!!

You're right it shouldn't be difficult too uninstall however you're still not grasping the meaning of beta. Beta means things may not go as intended. Or may not work as intended. Or if it's Microsoft beta means wait til sp2 before it works properly.

Perhaps in very roundabout way you're asking eset to provide a tool to remove reluctant beta software?

 

Thank you...indeed I am aware of the special removal tools for those and altogether too many other poorly designed programs. Trust me...I fully grasp the concept of alpha, beta, and other intermediate pre-release software packages having worked in this business one way or the other since the hardware was programmed by patch panels and paper tapes. And, you hit my nail squarely on the head on my (apparently) too tongue-in-cheek attempt to illuminate the need for a much better removal process. Above all else you should not ask a user to install something on their hardware that is impossible to remove by those who only want to use the tool. An uninstall glitch or three is certainly acceptable but what I experienced was way beyond that.

Right, those who are in the "I only want to use the tool" category have no business installing a beta in the first place but that's another colored horse. I would go so far as to suggest beta testers sign up to download the software from a protected area and communicate via a closed forum.

BUT, that eliminates a very valuable resource, maybe more valuable than those who know what they are doing. The best way to stress test your software is to give it to a non expert and wait for the "what the crap is this about" comments to start rolling in (not to be taken too literally).

Perhaps my concept of testing software is rooted too far back in antiquity - I would not take issue with that.

 

Hello,

I think you will find improvements to installation and uninstallation of the software in the release candidate now available for download.

Regards,

Aryeh Goretsky

 

i had the same problemw ith itunes, but instead of going into safe mode i used a program called revouninstaller and i was unable to unistall all properly without going into safe mode