I believe that there is a critical problem with one of the older builds of Eset Nod32 v3 with both the 32 and 64 bit versions of Vista (I am referring only to the AV solution and not Smart Security). Here is what I experienced this morning: I have two computers that have Eset Nod32 v3. One of them runs Windows Vista Ultimate 32 bit and other runs the 64 bit version. This morning, when I attempted to resume my 64 bit computer from Standby, I was unable to login. So, after waiting for 10 minutes with no change, I did a hard reset. After rebooting, I was able to login, but the Start Menu, Task Manager, Ctrl+Alt+Del options did not appear. Besides the wallpaper all I saw was the spinning mouse cursor. After another 10 minutes of no change, I did a hard reset and started Safe Mode which worked without any problems. I then initiated a chkdsk, rebooted and found no errors. Since I had to leave to go to another location, I left this computer as is (not responding). I have a second computer that has the 32 bit version of Vista. When I came in to use my second computer, I was unable to login and I noticed all of the same symptoms as the first computer (task manager, start menu and ctrl+alt+del didn't respond). So, on a hunch, I rebooted and then disabled the Eset services and the 2 Eset programs (egui.exe and the Eset HTTP program) from starting up. After rebooting, everything worked fine. So, to confirm that Eset was the cause of my problem, I re-enabled the service and programs and rebooted and the computer froze again. So, I again disabled the services and programs, rebooted and then uninstalled Eset and reinstalled the latest build. The latest build has resolved my problem. So far, the problem appears to only affect Vista. But, I will verify that this evening because I have a few other computers at home that run XP, although I don't know whether they run Nod32 v3 (they may be running v2.7). I will apply the latest build fix to my first computer later this evening. However, before I uninstall Nod32 from my first computer, I wanted to know if Eset wanted any information from this computer to work on a fix to prevent this problem for other people. If so, please let me know what you need and how you would like me to submit it. Note that I do not use any other AntiVirus products, I use the Windows Firewall only, I have disabled Windows Defender and besides Eset Nod32, the only other security product I have is MalwareBytes' AntiMalware installed in manual mode (I do not have Active protection enabled for this). So, my problem doesn't appear to be a conflict with another security product.