Jump to content

ESET products degrading with every upgrade


Recommended Posts

Today I finally overcame my reluctance to try the new EIS 11, especially after the bad experiences with ESS 9 and 10 which were disappointing. I thought maybe this time it's gonna be different, but I was wrong, EIS 11 is just as disappointing. I can look past problems such as there being no way to open the GUI except through the system tray icon, every other way results in an EIS restart. But I can't stand a BSOD, only after a few hours of installing EIS the system BSOD on me. I'm blaming this on EIS 'cause the hardware is new and till now there had been no BSODs.

I've tried reporting bugs and problems before with the previous versions, but they've just been ignored so I'm not gonna waste my time reporting this properly this time.

ESET used to be really great and I've used it with satisfaction for years, but the current state which it's in is unacceptable.

I'm gonna install ESS 8 (the last usable version) for now, and look for better solutions, I'm tired of this.

 

P.S. I'm experiencing these problems on Win 7, I don't know how EIS performs on other OSs.

Link to comment
Share on other sites

  • Administrators

V11.2 has been out for a quite long time and no other users have reported issues with BSOD. I'd rather expect another driver to be the culprit. Before making any conclusions, continue as follows:

1, Provide us with logs gathered by ESET Log Collector.
2, Configuring Windows to generate complete memory dumps as per https://support.eset.com/kb380/. When BSOD occurs, after a restart compress the memory dump and provide it to us for analysis.

Link to comment
Share on other sites

  • Most Valued Members
8 hours ago, Leonsk said:

P.S. I'm experiencing these problems on Win 7, I don't know how EIS performs on other OSs.

I'm running EIS v11.2.49.0 on two Win 7 systems without issue since it's release.

Did you install over the previous version or a clean install? 

Edited by SCR
Link to comment
Share on other sites

4 hours ago, SCR said:

I'm running EIS v11.2.49.0 on two Win 7 systems without issue since it's release.

 

Same here. No issues. Me thinks there is more to be heard.:unsure:

Link to comment
Share on other sites

20 hours ago, Marcos said:

V11.2 has been out for a quite long time and no other users have reported issues with BSOD. I'd rather expect another driver to be the culprit. Before making any conclusions, continue as follows:

1, Provide us with logs gathered by ESET Log Collector.
2, Configuring Windows to generate complete memory dumps as per https://support.eset.com/kb380/. When BSOD occurs, after a restart compress the memory dump and provide it to us for analysis.

I'm dead sure the culprit was EIS because I've had no BSODs (not once) since I bought this new PC for months, and after a few hours of EIS installation there's a BSOD.

Sorry, but as I said I'm not gonna waste my time this time since I did this a year ago and I'm still waiting for an answer. You didn't even bother to reply.

Link to comment
Share on other sites

18 hours ago, Nobody2145 said:

Since you're using Win 7, see this antivirus notice from Microsoft: https://support.microsoft.com/en-us/help/4072699/windows-security-updates-and-antivirus-software. Might be the problem.

I don't think that's the problem because I haven't updated Win 7 in a long time.

Link to comment
Share on other sites

17 hours ago, SCR said:

I'm running EIS v11.2.49.0 on two Win 7 systems without issue since it's release.

Did you install over the previous version or a clean install? 

Win 7 Ultimate SP1 x64 ?

Clean install. Can you open the GUI through the start menu without EIS being restarted ? That happens to me every time I try to open the GUI, except through the system tray.

Link to comment
Share on other sites

  • Most Valued Members
4 hours ago, Leonsk said:

Win 7 Ultimate SP1 x64 ?

Clean install. Can you open the GUI through the start menu without EIS being restarted ? That happens to me every time I try to open the GUI, except through the system tray.

I'm not sure I understand what you mean by  "EIS being restarted." Clicking the Eset entry in the start menu has the same effect as left clicking the icon in the system tray and the same effect as right clicking the Icon in the System Tray and left clicking "Home" on the Icon Menu, the GUI opens.

 I have monitored the exercise in Sysinternals Process Explorer and find that by clicking the start menu entry a second egui.exe process starts and then immediately closes if that's any help. However I do not see it having any effect on my system other then described.

I have Windows 7 Professional on this system and Windows 7 Home Premium on the other, both SP1.

Link to comment
Share on other sites

3 hours ago, SCR said:

I'm not sure I understand what you mean by  "EIS being restarted." Clicking the Eset entry in the start menu has the same effect as left clicking the icon in the system tray and the same effect as right clicking the Icon in the System Tray and left clicking "Home" on the Icon Menu, the GUI opens.

 I have monitored the exercise in Sysinternals Process Explorer and find that by clicking the start menu entry a second egui.exe process starts and then immediately closes if that's any help. However I do not see it having any effect on my system other then described.

I have Windows 7 Professional on this system and Windows 7 Home Premium on the other, both SP1.

I mean it gets restarted!

egui.exe is already running under ekrn.exe, if I click its icon in the sys tray it opens the GUI without any problems, but if I click on the start menu icon a new egui.exe process opens which results in the termination of the old one; sys tray icon also disappears and reappears again.

Link to comment
Share on other sites

  • Most Valued Members
7 hours ago, Leonsk said:

I mean it gets restarted!

egui.exe is already running under ekrn.exe, if I click its icon in the sys tray it opens the GUI without any problems, but if I click on the start menu icon a new egui.exe process opens which results in the termination of the old one; sys tray icon also disappears and reappears again.

I apologize. I was not clear on exactly what was restarting egui.exe or ekrn.exe or both.

That's pretty much describes my finding, as I previously stated, when I click the Start Menu entry for Eset, including the Icon closing and reopening. If I had to guess I'd say it's just replacing one instance with a new one. I must admit that I have never used the Start Menu entry for Eset in all the years I've been using it. I use the System Tray Icon to open the GUI.

Having said that I don't see any issue caused by the Start Menu except it closes the existing GUI instance and opens a new one. Are you having issues as a result of the action described?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...