lordaeron 0 Posted October 28, 2014 Share Posted October 28, 2014 Hi all i have just installed nod32 antivirus 8.0.304.3 on my Windows 7 32 bits system. All is fine except sysinspector function: file created properly but can't load it. A new install of nod32 change nothing. Thanks for any advise. regards. Link to comment Share on other sites More sharing options...
rugk 397 Posted October 29, 2014 Share Posted October 29, 2014 (edited) What happens if you load the XML with use the stand-alone version of SysInspector? You can download the standalone version from the website. Does SysInspector show a(n) (error) message? Edited November 2, 2014 by rugk Link to comment Share on other sites More sharing options...
lordaeron 0 Posted October 29, 2014 Author Share Posted October 29, 2014 It works properly with the stand alone version of sysinspector.. Link to comment Share on other sites More sharing options...
rugk 397 Posted October 30, 2014 Share Posted October 30, 2014 And what does the built-in SysInspector show when you try to load the file? Link to comment Share on other sites More sharing options...
lordaeron 0 Posted October 31, 2014 Author Share Posted October 31, 2014 it shows nothing. After file created, a double click or right click make no appearance of any window showing results. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted November 2, 2014 Share Posted November 2, 2014 (edited) How about browsing to the directory to see if the file was created or not ? Edited November 2, 2014 by Arakasi Link to comment Share on other sites More sharing options...
rugk 397 Posted November 2, 2014 Share Posted November 2, 2014 (edited) And if it exists try to load this XML file in the stand-alone version of SysInspector. Edit: FYI the directory where the SysInspector XMLs (from the built-in version) are saved is this dir: %ProgramData%\ESET\ESET Smart Security\SysInspector for ESS (for NOD32 you of course have to use the NOD32 dir). Edited November 5, 2014 by rugk Link to comment Share on other sites More sharing options...
lordaeron 0 Posted November 5, 2014 Author Share Posted November 5, 2014 to arakasi : file is created. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted November 5, 2014 Share Posted November 5, 2014 Open Sysinspector first. Then load that xml Link to comment Share on other sites More sharing options...
lordaeron 0 Posted November 7, 2014 Author Share Posted November 7, 2014 yes it works like this..thanks for your help,all. Link to comment Share on other sites More sharing options...
rugk 397 Posted November 7, 2014 Share Posted November 7, 2014 But this isn't good anyway. The built-in SysInspector should work too. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted November 7, 2014 Share Posted November 7, 2014 But this isn't good anyway. The built-in SysInspector should work too. True fact, but its apparent that there was an installation problem, or glitch that has caused this. A reinstall should fix the issue. However we also can't determine if any ntfs junction points or drive letter configs are corrupt or being used etc. We would need to really take a look at whats going on, but i would just reinstall. Link to comment Share on other sites More sharing options...
rugk 397 Posted November 7, 2014 Share Posted November 7, 2014 We would need to really take a look at whats going on, but i would just reinstall. Yes, for sure this would be the easiest solution. Link to comment Share on other sites More sharing options...
lordaeron 0 Posted November 13, 2014 Author Share Posted November 13, 2014 just had at the same time a conflict with adobe flash player...the reason for the glitch ? . conflict solved and nod32 reinstalled for the third time, succesfully! all is working properly now. Thanks guys for your help. Subject can be closed. Link to comment Share on other sites More sharing options...
Recommended Posts