tommy456

Ok I set up the boot time logging and rebooted the machine, and have rarred the log i'll pm you the location Eset hips does not like proc mon, it froze it out for over 2 mins

The splash screen is shown by egui.exe which is started by ekrn.exe. Could you measure how much slower Windows loads with and without ESET installed? Do you observe the delay also with default v10 settings? A boot log from Process Monitor could shed more light. Also disabling protection features, one by one, and narrowing it down would help us for further troubleshooting. I'd start off with temporarily disabling automatic start of real-time protection and restarting the computer. Hi, marcos , firstly i'm still running Version 9 ss, & not 10, but was seeing the same freezing issues caused by the Hips module, Currently windows and other programes currently are loaded befor eset appears, though my teamspeak server that i host is unable to connect to authenticate until eset loads , so although the lan icon is in the task bar showing internet , eset FW is actually blocking until it loads ,maybe? as for the loading time from when my desktop loads it's around 45 secs before eset loads , it used to load within 10-20 secs I'm happy to provide a boot log from proc explorer , i think i recall how to set that up, it's been a long time

There was a pre-release module update yesterday contains a new version of hips, But why ESET has a long delay starting after booting into windows the lan network is active prior to eset loading splash screen it used to load faster, and i'm using a SSD

Any news on if this issue with Hips module is going to be fixed or not?

After downloading the pre release modules eset gui even freezes after loading windows, eset is also slow loading after booting into windows in fact it's one of the last things to load up , not normal behaviour going by previous months that V9 has been on this machine (Feb 16)problems started in October so the devs need to review what changes they made to modules at that time because something they did broke eset ss v9 too because it shares the same modules as version 10 every year they manage to screw things up after the release of a new version why keep releasing new versions each year ? Apps that are mostly affected are opera browser , CPUz Microsoft word epson printer config, when trying to print a document So back to running with your laggy drain of resources HIPS disabled

ESS V9 has started freezing& but only for 2-30secs upon opening or running some programmes like flash player in ff , last night EKRN.exe was hogging my CPU at 15-20% for ages, no scanning on anything; but i was able to see it in task manager Well after a little testing with the exploit blocker disabled the problem lag/freezing /pausing when i run a certain programme ( Port forward tool ) runs with no pauses OS Win7 SP1 x64 CPU Intel i7-6700K @4.00GHz (4008 MHz) 16305 MB RAM Well today i noticed delays in running other apps that had previously run without the ridiculous delays from double clicking to them actually running (freezing/pausing) so i disabled completely the HIPS module and everything is lightning fast even web browsers loading web pages, previously opera with several tabs loaded would take an age to actually open, and longer for pages to load , without HIPS loaded it almost instant just as i would expect from the hardware of this machine, ESET there is a serious problem with the HIPS it's crippling even the high-end hardware, please do something ? HIPS support module: 1250 (20161010) was the issue for me using V9

hi yes i know may i use the hips to block it? block this C:\Program Files\ESET\ESET Smart Security\x86\upgrade.exe thanks I would be surprised if that it would block it. I run V7 on a very old and slow by today's standards PC witch is still running XP , yes i could upgrade to win7 but would need more ram ideally , but win7 isn't the best for old direct x 9 games, so would need a sound card to reproduce EAX 2.0 sounds in games as ms in their wisdom failed to include support for it, but seeing as i have already built a( top end 2015) machine which is running win 7 on it , i don't see any real point in spending money on ddr2 ram modules and a pci sound card , just so i can run the latest version of eset ss on it, i have tried v9 and had problems that were not sorted out by support

I too have a similar issue after buying a new 1 yr license digital version so just the un activated key supplied , after i entered it in to eset v9 it displayed this trial info of 365 days ?? and there hasn't been a trial license used on this pc any ideas?

Well i can only report on what i saw in the task scheduler, Also wouldn't it be a little questionable importing old rules/setting from a different version of eset never mind old settings being compatible with a different version of os ? seems likely to be problematic to me,

Running Win 7 X64 on my newly built rig, and have no intentions of upgrading the o/s version to win 10, infact i have been proactive in avoiding downloading/installing all known associated updates that MS has been trying to push to those who do not want win 10 in it's present form ESS had been set to alert me to critical ms system updates, all the get win 10 upgrade nag ware ect where not downloaded/installed , after disabling a task in the task scheduler i noticed a scheduled task for the eset service to reset it's settings for win 10 upgrade to happen on the 11/03/16 at 4:30 am, So as i had not set any tasks for eset, i can only assume it's built into eset based on the win 10 upgrade nonsense , well it won't be resetting anything now because the task that was unauthorised has been deleted This is my rig, and i control what it does or does not do, And if i did wish to upgrade my os, i certainly wouldn't be doing the in-place method, A friend of mine bought a rig ready made, with win 8.1 installed , he upgraded to win 10, and blocking all it's spyware and data collection is a joke, he has probably the worst version for hands on control as its w10 home Just thought i would put it out there about this potential unwanted reset of esets settings for other win7 customers out there, it may even apply to win8.1 users too

I have recently built a new gaming rig and ist's running WIN7 x64 ultimate , i installed the not so greatest but latest version of eset on that rig, and over a period of around 2 days that hogging main eset process was hogging around 2-300mb and that is on an almost ildle machine with very few 3rd party software /drivers installed , The version 7 however seems to run and remain at around 130mb IMO Eset had a reputation for providing a robust security solution that was one of if not THE lightest on system resources this was very popular amongst online gamers and others who enjoy a snappy PC but over the recent past eset seems to have almost abandoned what they where good at and followed like sheep the other security suite vendors with it's annual new versions, as well as adding imo some bloat, All i can guess is eset are aiming at the clueless home user now, Just why does the latest version consume more physical memory and other resources ?

Has there been any changes to Eset smart security regardless of version (v7-9) during the past few weeks that would cause connectivity issues with online games in particular when hosting online games , ? just that all of a sudden freinds that i have regularly joined my game server can no longer connect to it, i can see their ip addresses attempting to connect but they mysteriously get dropped they get a timed out message,, yet they are able to connect to the Teamspeak server that i also run on the same pc it just doesn't make any logical sense, it's either down to something eset have done, or the games publishers as connectivity is via their authentication servers

FF was slow with ssl disabled , i haven't used ssl scanning for years due to the un fixed issue that caused issues with the windows process Lsass.exe and the root cert didn't work properly anyway

When it doesn't work as intended ,or doesn't work with banking sites in central and western EU yes i do, and it's not something that i need or want, slowing the browser down or blocking websites it shouldn't block plus eset referred to it as a secure browser, Like i said I'm not interested in being a beta tester guinea pig for no reward And i did not come here to argue about the latest version, I'm not interested in installing it, So they had better unbreak eset before some say enough is enough and find something that works out of the box Well the cynic in me tried your version 9 ,again clean install ,and ekrn.exe after windows loading was 150+mb this increased every time a browser was opened and each web page opened ,e-mail client same after these applications where closed eset held the same amount of ram, and upon attempting to download a 10gb file, using a download manager MINI DM that allows up-to 10 threads When set at the normal 6 threads ekrn.exe consumed both ram and virtual memory (page file) very quickly even with only 2 threads downloading it made no difference, so much so i could not of completed downloading the file without running out of free ram first EKRN.exe process was showing over 1gb in size, which it did not release after i stopped the download and closed the process/application Secure integration in to web browser doesn't work, it will not load the web page ,in fact it crashes /hangs (firefox set as default browser) Then there is the delay of 20 seconds or more from clicking on the short cut for my e-mail client (outlook express) to it loading , hangs on the splash screen to long, then a shorter delay before i can open any e-mails, ????? Asimilar delay is experienced when launching other apps/browsers eset ss v9 slows everything down , it clearly should still be a beta version as it wasn't ready for release IMO , and before i forget the latest version of the ESET un-installer version 7.0.6.0 although removes the remnants of v9 hangs /window won't close on the pressing of any key Although i am aware that all what i have reported here will fall on deaf ears and result in no further progress as far as them finding and fixing this memory leak is concerned, I'm now past caring but i do this for the benefit of other potential customers who hopefully will read this before spending their money

ESET EKRN.exe Process starts of using 118-120mb both version 7 and 8 , and i have no doubts whatsoever v9 would be the same if not higher, eset broke a working product imo and therefore should fix it , https://forum.eset.com/topic/6654-ess-9-slows-google-chrome-browsing/also firefox hxxp://support.eset.com/kb5657/shows info regarding the addition of eset secure browser ,(bloat) yet you aren't aware of it? I have not incentive or inclination to install version 9 so a waste of time asking me to do this

..

Why, because there is at least one other end user who is running v9 and also has your poxy memory leak, And i do not need the extra bloat of version 9, i am a online gamer i do not want or need extra processes running in the background that are simply not needed , i also ain't your average dumb sheeple end user so don't need or want a extra browser, (that doesn't work with many bank in the EU and uk) , i know i ain't being redirected to a fake site, ect ect, This type of problem occurs every time eset release a new version, and has done since they jumped on the must release something new every year bandwagon it's nonsense,. I want something that just works like it did with version 4 So you don't support version 7 but you do support/ develop version 8 which is only 18mths old at the most ,so just fix it, or you will loose several loyal customers,

I took the issue up with support, and their answer was that although v7 will continue to receive virus sigs ect it isn't being developed any longer, so a eset cop out,!!!!! Looks like their normally good support as gone down the pan as well as them releasing a product that works out of the box and doesn't break earlier versions So i clean installed a fully supported version just for laughs really, and guess what the very same memory leak in eset's main process is still there, just as it would be if i installed the bloated v9 , so what are eset going to do about this ignore it like they have basically ignored me, since i uploaded a dmp file ? IMO the underlying reason for this could lie with any of the primary program modules that were pushed from esets servers and installed to eset without the end user consenting or even being asked /prompted, even though their eset client was set not to download program components automatically, program modules are components are they not? lack of respect for end user imo

Is there any update / progress being made on this issue? I created the Dump file, uploaded it ,PM,ed The file name and info where i uploaded it to ask requested, But nothing since, I also appears that the PM hasn't even been read, So a pointless exercise so far, And rapidly looking like i first thought eset aren't interested in fixing what they have broken

Marcos do you read your PM's or is there a bug with the forum that shows PM's as not read?

Have done, Marcos has a PM

Now got a 711mb DMP file created and zipped

Ok, i have created a DMP file of 345mb in size as per instructions, i can if needed wait a short time longer until EKRN.EXE eats/hogs more memory , or i can rar/zip the DMP i have already and upload on to eset FTP server, please advise what would be better

So just to be clear on what you meant run proc dump using -ma ekrn command when it is hogging nearly a 1gb of ram? but before i will be able to create a dmp of ekrn.exe i will have to disable eset's self defence and reboot ?

I currently run ESS V7 due to esets overkill in v8 and onwards , today after a little browsing of the web using the latest version of fire-fox the EKRN.EXE process is hogging some 890,940k of ram is this some kind of standing joke eset? The reason i chose eset was because it wasn't a resource hog that over the years has changed as it now is such a hog, releasing new versions every year with more and more bloat Some of us do not need all the bloat no one is catering for us it would seem Whats happening regarding this obvious memory leak, will it be fixed or is eset washing it's hands of older versions now?