Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by cybot

  1. issue is not fixed when running the Dragon Center 2 setup file, a message from ESSP saying that the file setup.exe was infected. it had the following message: Time;Scanner;Object type;Object;Detection;Action;User;Information;Hash;First seen here 1/10/2020 7:29:58 PM;Real-time file system protection;file;C:\Users\Cybot\AppData\Local\Temp\{E3E1BF59-57C1-4792-BC38-9C2F0F58204B}\setup.exe;a variant of Win32/GenKryptik.EBBO trojan;cleaned by deleting;MSI\Cybot;Event occurred on a new file created by the application: C:\Users\Cybot\AppData\Local\Temp\{686B90F5-2E1E-4F34-BBA4-F8D0F93C66
  2. apologies. in the previous case, I did follow that guide, but when the same issue reoccurs, it looks like nothing was done about the false positive. ESSP is no longer flagging the setup files. thanks and sorry for how I went about reporting the issue this time around.
  3. I am trying to update my laptops MSI Dragon Center 2 software, but it is being blocked by both windows defender, ESET ESSP, and windows smart screen. I try and extract the files, and the setup file files are deleted/quarantined as soon as they are accessed. the files that are falsely being marked as being a virus are: "setup_G.exe", "setup_P.exe", and "setup_W.exe" the files for the setup program are contained in a .ZIP file and are downloaded from the manufacturer website from the following URL: https://download.msi.com/uti_exe/nb/ap_DragonCenterv2.6.1912.2601_2.6.1912.2601_0xc5b28391.zip .
  4. 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
  5. Windows 10 1903 ESSP 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 t
  6. 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
  7. 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.
  8. 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 fro
  9. so it looks like they repacked the version and fixed what ever was the problem. (as denoted by the .1 at the end of the version)
  10. my built-in web cam is also under the "camera" category in device manager. It worked fine under, but had problems when i upgraded to 11.1.4x.0 It's on a 2010 Toshiba satellite laptop and the device is called "USB 2.0 UVC Webcam" My solution was to do the following: export your current EIS settings in the settings menu of EIS. goto eset.com and either download the smart installer or the full package (i prefer the full package) write down or find a copy of your EIS license info (you will need it when you re install EIS) uninstall EIS and then
  11. believe it or not... a clean install of will solve the problem of the camera and device control not working. I don't know why it would not work after upgrading, but i can only assume the there is a major change under the hood between the two versions ( and that is not working well with the upgrade process. At least Eset was quick about packaging up the new version for a full install, which solves the problem. the windows 10 store app titled "Camera" by M$, works and triggers the camera protection when loaded for the first time, as does the camera application
  12. well you may not have an issue as your running win7. this may or may not be a win10 only issue
  13. when i checked the other day the setup program link on the eset site was for the only way to get to 11.1.42 is through updating via the program. NOTE: just checked the downloads page, and EIS is now available for download
  14. that's what i found happens too. so annoying. my error message says it only affects newly connected cameras until the computer is restarted, but this is clearly not the case. i'm on now as well only real fix I have found is to run a repair from app and features, which reverts you to then let it update to and then turn off application updates in eis advanced settings. i admit this is more of a workaround than a fix, but it's all i could come up with so far.
  15. Found a temporary work around, running a repair from apps/settings in win10, the repair reverted EIS to after the restart, i turned off application updates. under, web cam protection and device control are now working under the older version. i appear to have that version module installed, and under the version i talked about above, the web cam protection and device control work. but updating to causes those two features to not work.
  16. found a fix of a sort, for me at least. I went into apps and settings, and found the entry for EIS and clicked modify, then repair. EIS reverted from to then i restarted when asked to. after the restart, i went into advanced settings > updates and turned off application updates. I don't know how long it will take ESET to fix the issue, but for now has working device control and web cam protection, while version does not.
  17. after updating EIS to version both web cam protection AND device control have stopped working. both features were working prior to the upgrade via program update. going to try rolling back the update through EIS advance program settings to see if that will get it working for now.
  18. looks like my fix for web cam protection didn't stick. after a restart, it was showing the error again.
  19. might have found a solution for this. go into ESET and turn off the Web Cam protection open device manager (Win+X and select device manager) and uninstall the camera device (in my case "USB 2.0 UVC WebCam" enable webcam protection in ESET. go back to device manager and select the scan for hardware changes button (or with the device manager open press this key sequence : ALT > a > a) Web cam protection should be enabled properly now. I don't know what changed in from the previous version, but something obviously change so that Device Control and Web Cam Protec
  20. I'm having this issue too. Device control is not working either. issue started after application update to
  21. I am on west coast USA, so by 11pm 1/3/18 i should have had it available. but it wasn't
  22. i have a 1st gen i7 and the update was not pushed to me. I don't know if it was because the required regkey was not present in the system or not. but after installing the update(s) as instructed above, I then activated defender's periodic scan feature, and updated the signatures for that. the key then appeared in the registry. I tried getting the module update for eis, but it would not update till this morning, at which point the key was already present. I am assuming that if i had activated the periodic scan and updated defender prior to installing the update, it would have installed the key
  23. Product used: EIS was just about to post on this when i spotted this thread. I checked my system, and I don't even have a subkey called 'QualityCompat'. So my guess would be that EIS and NOD32 ARE NOT compatible. whether this changes is most likely up to Eset.
  24. EIS is only available in german atm. I live in USA and don't speak german. so EIS 10 which is available, is a downgrade.
  25. is it possible for someone from eset to do a feature comparison between ESS 10 and EIS 11? (if one has not already been done) It would make me feel easier about switching over to EIS. The only reason I have not switched our systems over yet, is because I fear losing functionality between versions. I don't want a downgrade. I want the equivalent level of features. I am glad anti theft is in EIS 11, but if there are other features that ESS has that EIS does not, then I will not switch over. I do plan on switching over to ESS Premium when my license expires, but that wont be until late 2018
  • Create New...