Jump to content

Automatic computer restart when Eset Internet security installed


Recommended Posts

Hello,

i have big problem with Eset Internet Security on desktop device.

When I install the program PC is automatically restarting. I cannot work properly. 

Every time i try to turn on PC it automatically restart when desktop is reached. After uinstalling the Eset Internet Security desktop is working well and not restarting.

I use Esset on other devices and i have problem only with one PC.

Can you help with this issue?

Link to comment
Share on other sites

  • Administrators

Strange that an ESI log in the temp folder could not be found:

[11:20:33.126] "C:\Users\eXXXr\Desktop\SysInspector.exe" /wantcloud /silent /gen="C:\Users\eXXXr\AppData\Local\Temp\elc7B1B.tmp.xml"
[11:21:03.807] Adding file: C:\Users\eXXXr\AppData\Local\Temp\elc7B1B.tmp.xml -> Config/SysInspector.xml
[11:21:03.807]   WARNING: File was not found or could not be opened - skipped.

Could you please check if it's created while collecting logs with ELC?

Link to comment
Share on other sites

  • Administrators

Unfortunately there are no details about the crash in the system event log. There's only a record "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

You can generate a SysInspector log as per https://support.eset.com/en/kb762.

Link to comment
Share on other sites

  • 4 weeks later...

Hello

today i tried to install a new version of Eset Internet Security.

unfortunatlly after install and run the app the copmputer started to reset on it own.

I cant't work properly. 

The only solution is to uinstall the eset internet security.

Can you help me to solve this problem.

Link to comment
Share on other sites

  • Administrators

Unfortunately the system event log only reads the following without any details about the issue:
The system has restarted without a clean shutdown first. Possible causes of the error: The system stopped responding or crashed, or there was an unexpected loss of power.

If you received a BSOD, a memory dump should have been created in c:\windows\memory.dmp.

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...