Skip to main content
Super User

Return to Answer

added 21 characters in body
Source Link
Casey Swett
Casey Swett
  • 1
  • 1

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds, which I see you did.

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds.

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds, which I see you did.

added clarity that HIPS is a detection within ESET
Source Link
Casey Swett
Casey Swett
  • 1
  • 1

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds.

It's ESET. It's been causing issues for several days now. Try disabling HIPS and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds.

It's ESET. It's been causing issues for several days now. Try disabling HIPS detection within ESET and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds.

Source Link
Casey Swett
Casey Swett
  • 1
  • 1

It's ESET. It's been causing issues for several days now. Try disabling HIPS and reboot. Or more crudely uninstall ESET temporarily to prove. You may also find that opening command prompt, it crashes after a few seconds.