Jump to content

cybot

Members
  • Content Count

    38
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    USA
  1. I don't know if I have High DPI enabled on my system, but it's good too know that it's a recognized issue that is due to be fixed
  2. Windows 10 1903 ESSP 12.1.34.0 Sysinspector v10.7.79.0 I have discovered that the Sysinspector tool in ESSP (and possibly other versions of ESET software that include the tool) crashes on load. It can create sysinspector logs, but you can not view them. according to the windows event viewer, the sysinspector is crashing with a 0xc000005 error, with the faulting module being listed as the sysinspector program it self (an internal program error?) The stand alone version of the sysinspector downloaded from the eset site works, but is an older version and takes forever to come up. Fault bucket 2243708203262627270, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0   Problem signature: P1: SysInspector.exe P2: 10.7.79.0 P3: 5ca726a7 P4: SysInspector.exe P5: 10.7.79.0 P6: 5ca726a7 P7: c0000005 P8: 00000000000399aa P9: P10:   Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC914.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC982.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9A2.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9D4.tmp.txt   These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SysInspector.exe_8bf46cbe28d02d14db50a662d67fcf6d511f96c2_ee6e4bfc_223d13f8-a307-4797-a8bb-ad1273023770   Analysis symbol: Rechecking for solution: 0 Report Id: 89c9e574-29d7-4838-bb51-ea278453d03c Report Status: 268435456 Hashed bucket: 662e45029cc2e6d16f2340b923194dc6 Cab Guid: 0 Faulting application name: SysInspector.exe, version: 10.7.79.0, time stamp: 0x5ca726a7 Faulting module name: SysInspector.exe, version: 10.7.79.0, time stamp: 0x5ca726a7 Exception code: 0xc0000005 Fault offset: 0x00000000000399aa Faulting process id: 0x5860 Faulting application start time: 0x01d5265210dec022 Faulting application path: C:\Program Files\ESET\ESET Security\SysInspector.exe Faulting module path: C:\Program Files\ESET\ESET Security\SysInspector.exe Report Id: 89c9e574-29d7-4838-bb51-ea278453d03c Faulting package full name: Faulting package-relative application ID: - <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-06-19T03:50:31.823535500Z" /> <EventRecordID>7953</EventRecordID> <Channel>Application</Channel> <Computer>MSI</Computer> <Security /> </System> - <EventData> <Data>SysInspector.exe</Data> <Data>10.7.79.0</Data> <Data>5ca726a7</Data> <Data>SysInspector.exe</Data> <Data>10.7.79.0</Data> <Data>5ca726a7</Data> <Data>c0000005</Data> <Data>00000000000399aa</Data> <Data>5860</Data> <Data>01d5265210dec022</Data> <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data> <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data> <Data>89c9e574-29d7-4838-bb51-ea278453d03c</Data> <Data /> <Data /> </EventData> </Event>
  3. Not true. I am in contact with ESET Technical support technical management team they and I have found that enabling the secure data feature in ESSP, while Condusiv Diskeeper 18 Pro is installed, results in a 0x1e K_mode_Exception_not_handled BSOD which does not allow the system to boot until the ESET uninstaller is run from safemode. the case is actively being investigated. case #285912 according to the support tech, endpoint encryption and ESSP's secure data feature both use the same software, originally made by DESLock. Also found out just today, that the Sysinspector crashes on load. you can create sysinspector logs, but you can not view them. I will be creating a separate post about that issue.
  4. don't know if your system is used by others, but if it is not, then I would not worry about this issue. the security hole from the article can only be exploited locally, as in sitting at the machine. Unless you are going to be performing DDOS attacks or hacking into your own system, then your safe. If it's your own system, your should already have Admin level access to the OS available to you. the only way for to be vulnerable is if you allow access to your machine to a untrusted remote user using Remote Desktop, Teamviewer or other similar software.
  5. Just got off the phone with ESET support, and the Advisory for the ESET Endpoint Encryption and Windows 10 1903 should eventually be updated to include ESET Smart security premium, but until then, I am notifying all users here. If you use Eset Smart Security Premium's Secure Data feature on Windows 10 v1903 and certain other third party software such as Condusiv Diskeeper 18 Professional, you will run into non recoverable BSOD at startup of the OS. the BSOD stop code is 'K_Mode Exception Not Handled' Windows will only boot into safe mode the only way to recover from the BSOD is too temporarily uninstall ESSP using the ESET uninstaller from here ->(https://support.eset.com/kb2289/) <- and uninstall ESSP temporily. although removing the offending third party software only will also fix the issue, this is usually not possible due to the fact that the Microsoft Installer service will not run under windows safe mode. after windows is back up and running again, you may reinstall ESSP, but for the time being, UNDER NO CIRCUMSTANCES, TURN ON THE SECURE DATA FEATURE.
  6. actually it's the same thing what do you mean it's the same thing? there is a clear difference in the UI of ESS7, 8 and ESS9
  7. I would like to see, when implementing a major UI overhaul, an option to use the previous versions UI design, when I went from ESS 8 to ESS 9, I was a little disoriented by the UI change, and still find the new UI more clunky and more difficult to navigate than ESS 8's simpler UI
×
×
  • Create New...