Operating System: Windows 7 Home x64 Long time user of NOD32, I decided that, as I moved off my family-home group of licences and onto my own specific-to-me set of licences, I also felt like going with Smart Security. Apparently this was my first mistake? An attempt to install off the bat it asks if I want to perform an "upgrade installation," so I figured that this installation would be safe to perform. The installation fails saying I need to restart first. Fine, fair enough. A restart later it tells me I haven't restarted yet. Sceptically I restart again, and once again get the same message. At this point I've decided that it's definitely not me acting up. A glance at the program folder shows me that the program has deleted its own uninstaller, so I delete the Program Files folder and its matching ProgramData folder and restart (for good measure). No success. I downloaded the Eset Uninstaller offered for the manual removal and booted my computer in safe mode, running that uninstaller successfully. After rebooting and removing the Program Files / ProgramData ESET folders again, I am STILL getting the installation errors. This wouldn't be so bad if I could at least fall back on NOD32, but even with the manual uninstall et al I am unable to load even that. While the irony of installing Eset Smart Security leaving me literally unable to install any Eset products has not escaped my attention, I hope you can appreciate why this doesn't really cheer me up. Is this typical behaviour for Smart Security's installer? Regardless, what can I do?