gooberbear

Sorry it took so long to get back to this topic . I had to revert to Windows 8 because I was having too many issues in Windows 8.1 . Under Windows 8 the log windows resize just as expected . I intend to try to do a clean install of Windows 8.1 and see what happens . I t may take a couple of weeks before I can repost here with the results . Too much going on with the holidays .

I started having this issue today as well . It runs all the way up to the end of the update , then stops with this error. I am also seeing the Eset Service take up huge amounts of ram . I wonder if there is a major memory leak ?

Ok , disabled Windows Defender through Autoruns as suggested and that solved the issue of not being able to schedule anything ! Thank you so much . I thought that I had Windows Defender turned off , but I guess the Windows 8.1 update re-enabled it .

Ok , apparently I DO have some issues with Eset Nod32 V7 . One , in any window that displays lists of information within Nod32 ( like for example the list of the schedulers items , columns cannot be widened out so you can see everything ) . This is just annoying but not breaking functionality. What DOES break functionality is that although I installed in Administrator and am running in Administrator , ESET Node32 V7 seems not to recognize this fact and will not allow me to change certain settings because I am "not in administrator mode". I cannot change , add , or delete any items from the scheduler, it keeps erroring out . It doesn't say that it is because I'm not administrator , but I am assuming that is it's meaning because of the same happening on other screens.

On Windows 8.1 Pro x64 , right click menu integration fails . I can right click something to scan and I get a popup window saying Shell Extension Error Communication with ESET NOD32 Antivirus kernel failed ! and that is it , nothing else . Eset Nod32 doesn't scan the target. Is anyone else getting this ? Update : Never Mind . Apparently I had a bad install of Eset Nod32 . Other things started going wrong . I had to use the uninstall tool 3 times to get it completely uninstalled in safe mode before I could reinstall it . It finally took and seems to be working fine now.

Awesome ! Thanks ! I searched the forum ,but it turned up blank , guess I just didn't have the right search terms entered !

With HIPS activated , Stardock's Windowblinds program fails to load correctly, leaving the program useless. Apparently others know of this issue and think it is a DLL that is causing the problem . I have just submitted a ticket to Stardock , but was curious if anyone else had this issue. If you disable HIPS , Windowblinds loads correctly. If I knew which DLL was the issue , I would try creating a rule in HIPS to ignore it , but no information is being logged by HIPS even saying it is blocking it ( I enabled full logging in HIPS ).