ESET SysInspector v1.1.2.0 released

Tried the safe mode using the Administrator's login (WinXP SP3 32b) - exactly the same crash.

 

Hello,

That increases the chance that the problem is due to a kernel-mode and not a user-mode process, or at least something that runs across all accounts and not just the one you normally use to log in to the operating system.

While I check with the developers is there anything else you can tell me about the operating environment on the computers which is non-standard? Perhaps some additional security, system management, backup or data integrity tools that might be installed and running in the background?

Regards,

Aryeh Goretsky

 

Surprisingly, I've renamed the `hosts` file and the SysInspector started successfully.
I've made some tests with hosts file and now, I believe, found the issue. I'm using editor which configured to use unix type line ending (\n) and SysInspector expects win style (\r\n).

 

Hello,

That is very interesting; I have not seen that before. Then again, I suspect most people who edit their hosts file use an MS-DOS (CR/LF style) text editor.

Regards,

Aryeh Goretsky

 

New version is out: 1.2.012.0

http://www.eset.com/download/sysinspector.php

 

Is there an email or official feedback method for SysInspector?

I would like to request that SysInspect also check the following key as I had been beating my head in trying to find out how malware was starting... turns out it was an added "aux" key that loaded with WMI and Explorer.exe (and probably others).

The interesting thing about this is that once loaded, there were no references in memory or open handles to the file. Process Monitor just shows the image was loaded and threads were created.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

 

Perhaps if you send a request to support@eset.com someone will have a look at it.

 

Hello,

Your enhancement request has been noted.

Regards,

Aryeh Goretsky

 

Thanks for the update!