shought Posted May 3, 2009 Share Posted May 3, 2009 I'll describe the problem(s) I'm experiencing: whenever I boot I notice that it takes a very long time before the ESET GUI loads(the icon appears LAST in the list, while before I reinstalled my system it always appeared FIRST) and ESET's driver/kernel takes up to 20 seconds to load, I can see this because the Real-time file system protection can't be turned on or off(the box in the right-click menu of the ESET icon is grayed out), also when I open the ESET GUI it shows me a red exclamation mark.This problem on its own doesn't really bother me, but it seems that Firefox also won't load during this period(around 20 seconds) and well, I would like to solve that. (You should know my computer is pretty fast and normally Firefox starts with the blink of an eye)Software installed: COMODO Firewall, eBoostr(already turned this off, didn't do any good).What I tried: reinstalling ESET to no avail. Link to comment Share on other sites More sharing options...
Bizarre™ Posted May 3, 2009 Share Posted May 3, 2009 How many network connections / drivers do you have installed? Link to comment Share on other sites More sharing options...
shought Posted May 3, 2009 Author Share Posted May 3, 2009 Two at the moment, one for my VirtualBox and the main one, I'll try disabling the VirtualBox one tomorrow morning :P Link to comment Share on other sites More sharing options...
Bizarre™ Posted May 3, 2009 Share Posted May 3, 2009 Well, that's what I was thinking: you have VirtualBox installed.Have you installed the latest version (2.2.2) ?Apparently, v2.2.2 solves this problem. Link to comment Share on other sites More sharing options...
mara- Posted May 3, 2009 Share Posted May 3, 2009 Hm, I think I had this problem. Reinstall of Eset solved it. But, not repair mode. Complete uninstall, reboot, install, reboot.Cheers :P Link to comment Share on other sites More sharing options...
Marik Posted May 3, 2009 Share Posted May 3, 2009 why do you even need eset in a virtual environment?I can see this because the Real-time file system protection can't be turned on or offThat's bshere, dl the attachment at start reading, the txt file before doing anything that might result in a f***ed-up-OS.Pay no attention to this post, move on guys :P Link to comment Share on other sites More sharing options...
mara- Posted May 3, 2009 Share Posted May 3, 2009 Um, Marik, what this has to do with his problem? Touching Windows File Protection won't help, and I would not recommend doing this.Cheers :P Link to comment Share on other sites More sharing options...
Marik Posted May 4, 2009 Share Posted May 4, 2009 Um, Marik, what this has to do with his problem? Touching Windows File Protection won't help, and I would not recommend doing this.Cheers :DIt has nothing to do with it. I just saw that part in his post and it caught my eye. And I only replied to that part alone :lmao:Naturally I'm to lazy to reply to his entire post.Now that I take a closer look he was only talking about the file protection in eset, and not windows :P, oh well I guess I'll remove that attachment.Anyways the problem can be solved with a simple uninstall by either totaluninstall or your uninstaller, a re-download of eav/ess.A simple copy/paste of the respective installed in C:\WINDOWS\Installer. and then you can safely install the damn thing Link to comment Share on other sites More sharing options...
shought Posted May 4, 2009 Author Share Posted May 4, 2009 Well, that's what I was thinking: you have VirtualBox installed.Have you installed the latest version (2.2.2) ?Apparently, v2.2.2 solves this problem.I've got v2.2.2 installed, but I'm going to disable the network adapter now :lmao: (I'll also try uninstalling it)Hm, I think I had this problem. Reinstall of Eset solved it. But, not repair mode. Complete uninstall, reboot, install, reboot.Cheers ;)Been there, done that :PIt has nothing to do with it. I just saw that part in his post and it caught my eye. And I only replied to that part alone :lmao:Naturally I'm to lazy to reply to his entire post.Now that I take a closer look he was only talking about the file protection in eset, and not windows :D, oh well I guess I'll remove that attachment.Anyways the problem can be solved with a simple uninstall by either totaluninstall or your uninstaller, a re-download of eav/ess.A simple copy/paste of the respective installed in C:\WINDOWS\Installer. and then you can safely install the damn thingLazy ass mf :PBeen there, done that.(Except for the copying to the Installer folder, but what good would that do...) Link to comment Share on other sites More sharing options...
shought Posted May 4, 2009 Author Share Posted May 4, 2009 Ok, I did this: Uninstall VirtualBox, disable Self-defense(ESET), reboot, UnFix, uninstall ESET, reboot, install ESET, disable Self-defense, reboot, Fixed it, reboot and now the kernel/driver does seem to load faster, a lot. Where it would take 20 seconds before now it takes like 2 seconds :PThe ESET GUI icon still shows up last, but I guess I'll just have to live with that for now :D Link to comment Share on other sites More sharing options...
Marik Posted May 4, 2009 Share Posted May 4, 2009 there seems to be a glitch with eav/ess and M$ office.Try disabling eset completely (ekrn and gui), and then if you have M$ office installed open a document....M$ won't let you :P Link to comment Share on other sites More sharing options...
mara- Posted May 4, 2009 Share Posted May 4, 2009 Ok, I did this: Uninstall VirtualBox, disable Self-defense(ESET), reboot, UnFix, uninstall ESET, reboot, install ESET, disable Self-defense, reboot, Fixed it, reboot and now the kernel/driver does seem to load faster, a lot. Where it would take 20 seconds before now it takes like 2 seconds :)The ESET GUI icon still shows up last, but I guess I'll just have to live with that for now ;)ESET GUI icon, for me also comes almost last, but that is not important. It is important that Eset service and drivers are loaded first. Did you use mara- fix on that system, which delays self-protection driver. Maybe you should check if everything is OK.Navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ehdrvand check if key "Start" is set to 1.Also, even if mara fix did not touch following registry keys, check them anyway:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ekrnValue of the "Start" key should be 2.HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\eamonValue of the "Start" key should be 2.Cheers ;) Link to comment Share on other sites More sharing options...
mara- Posted May 4, 2009 Share Posted May 4, 2009 A simple copy/paste of the respective installed in C:\WINDOWS\Installer. and then you can safely install the damn thingWhy did you say this? Did you have problems with installing latest version? Because I had. Installer did not want to install ESET complaining that installer is missing from that location. I just copied it there and it installed fine.Cheers :) Link to comment Share on other sites More sharing options...
shought Posted May 4, 2009 Author Share Posted May 4, 2009 My registry is fine :) Haven't used your fix which delays the ESET kernel on this install, but I checked the keys just to be sure ;) Link to comment Share on other sites More sharing options...
Marik Posted May 4, 2009 Share Posted May 4, 2009 A simple copy/paste of the respective installed in C:\WINDOWS\Installer. and then you can safely install the damn thingWhy did you say this? Did you have problems with installing latest version? Because I had. Installer did not want to install ESET complaining that installer is missing from that location. I just copied it there and it installed fine.Cheers :)yes that's why I said that.I uninstalled my eav, but the uninstall process wouldn't complete cause the installer in c:\win\installer was missing. It was prob deleted by registry winner when i performed evidence cleaner....who knows, but that's why I said that ;) Link to comment Share on other sites More sharing options...
mara- Posted May 4, 2009 Share Posted May 4, 2009 I'm not sure if it is a cleaner. It seems when MSI installer is used, it needs to automatically copy itself to that location, but this one did not do it. This could be an error in the installer.Cheers :rolleyes: Link to comment Share on other sites More sharing options...
Marik Posted May 4, 2009 Share Posted May 4, 2009 I'm not sure if it is a cleaner. It seems when MSI installer is used, it needs to automatically copy itself to that location, but this one did not do it. This could be an error in the installer.Cheers :rolleyes:oh, I thought it was just me <_<Seems like there really was something wrong with the previous installer Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.