Jump to content

Tetranitrocubane

Members
  • Content Count

    26
  • Joined

  • Last visited

Everything posted by Tetranitrocubane

  1. I admit I used the copy I had on my hard drive already rather than download the newest one. I had it on hand from a previous troubleshooting attempt. If everything seems to be working, though, I guess I should just chalk it up to being a fluke? It certainly isn't red on the protection status at all.
  2. No errors reported on the home screen. Protection status is green. EAV logs attached as requested. eav_logs 3.zip
  3. Hi all. Today when I started up my computer, ESET started to update itself as per normal. When it began to attempt to apply the update, I got a series of errors: ESET then instructed me to reboot to complete the update of ESET, which I did. Upon restarting, ESET seems to be running just fine, but I presume that is with the older drivers or without the appropriate drivers installed (due to the errors). Updating again does not seem to do anything, unfortunately. Are these errors something to worry about? ESET appears to be functioning just fine now, but I'm not sure. Thank
  4. I admit I'm a touch confused and unsure of what's responsible for the detection/lack of detection based on time. However, I do want to thank you both for your insight and your explanations, as well as your analysis! Just to be fairly sure about this, though: At any point were these DLLs malicious, or was this indeed a false positive?
  5. I admit I'm out of my depth. On Friday the 17th, I returned to my computer to find this in the log file: ESET auto-deleted and quarantined the files, and my own response was to delete the program entirely out of an abundance of caution. The files have not been altered since then. Today, when I restored the files from quarantine and scanned them through the windows context menu, I got these outcomes (Scanned one file on it's own, then the other two together - Restored the file to a different folder, because the original location was deleted along with the program):
  6. Huh. Well, I did scan them around 3 hours ago, I'll confess. This might lend more credence to itman's theory?
  7. I don't know what to say - I restored the DLLs from Quarantine, scanned them via ESET Context scan, and the ESET Context scan did not flag them as malicious. I would presume because ESET's definitions have been updated to unblock the files?
  8. Hi Marcos. The only DLLs I have were ones that I pulled out of quarantine, so I don't believe they've been updated. I deleted the program after the DLLs were flagged. The DLLs in question should be in the logs I attached above. I used the ESET log collector as you instructed. Thanks!
  9. ESET Context scan does not detect any of these files as suspicious or malicious. Though I wonder if definitions might've been updated between Friday when the on-demand scan picked them up, and now?
  10. Thanks for the tips. Here are the links to each file's VT profile. Each one came back with zero detections - that makes me wonder exactly why ESET flagged these files to begin with? Could that be a signal of a deeper problem? Unity.Timeline.dll PhotonUnityNetworking.dll UnityEngine.Monetization.dll
  11. Thanks for the Detection log tip - Though for some reason, the detections aren't in there? I can find the detections in the Scan log, it clearly labels them as suspicious objects and says "Cleaned by deleting" - But there aren't any hashes there. And again, the detection log doesn't have them for some reason, which is odd.
  12. The files were auto-deleted by ESET. The developer of the software in question did verify, however, that the files were legitimate. I reached out via email.
  13. No problem. Log files attached. Hopefully these files are only accessible to forum admins and moderators! eav_logs_Black_Ice.zip
  14. Hello, Today I performed a full system scan, and was shocked when ESET (version 13.2.15.0 on Windows 10 x64) reported three detections, where I usually have zero. I hadn't installed any new software recently, so this got me very worried. Digging into the scan log, it seems that three files were flagged as being 'suspicious objects': PhotonUnityNetworking.dll Unity.Timeline.dll UnityEngine.Monetization.dll All three of these files are associated with the video game "Black Ice" sold through steam. This game has been on my computer for years, and never caused a pr
  15. After updating to cleaner module 1199, the problem has returned with consistency. Edit: Check that - It is still happening periodically, but it was only consistent for the first few times after updating the cleaner module. It's happening only very rarely afterward. Just to add to the confusion, I guess!
  16. Hi Itman, I've tried adding the exception for Deep Behavior Inspection in ESET, but unfortunately the behavior seems to be persisting. I've seen the suggestion on the Sandboxie forums - but I am similarly worried that blocking ESET in Sandboxie will cause more problems than it will solve. Marcos, I'm currently using Sandboxie 5.31.2 64-bit on Windows 10. I recommend using the latest Sandboxie beta, as there are some lingering issues on the 5.30 build. The latest betas are here: https://community.sophos.com/products/sandboxie/sandboxie-beta-versions/f/sandboxie-beta-5-
  17. Temporarily disabling HIPS and rebooting does in fact allow me to empty the sandbox.
  18. Hi Marcos. I have collected the requested logs and uploaded them here. I do want to note that since I posted this message that the issue has gotten worse - That is to say, I have been unable to delete the contents of the sandbox at all, even after multiple reboots. This means that if the HIPS issue is happening at the initiation of the Sandbox population, the logs won't capture this. I switched my logging options as you indicated, then tried to close all programs in the sandbox. This initiated the access denied error. I then disabled that logging option, and exported the log files t
  19. Hi Marcos, I will do my best to enable logging and get the files upload here when I'm able. Before I do that, is there any risk of personal information being included with the log, since I'll be uploading it to a public location? I admit that I don't know what the logging will record. At present, even a reboot of my machine doesn't let me clear out the sandbox - or even manually delete the files in the sandbox. Even uninstalling Sandboxie isn't an option now, as the files in the sandbox (specifically the RegHive files) are still being opened and constantly accessed. EKRN.EXE is the p
  20. Thanks very much for your insight and advice, Itman! I'll try reaching out to ESET via their official support channels. In the event that I find a reasonable resolution, I'll report back here for sure.
  21. No, nothing of the sort. In fact, I made no changes whatsoever. On the 2nd of July, everything was fine. Suddenly on the 3rd, this started happening - Despite my not installing any software, updates, or changing settings between those two times. That being said, I do agree that it's rather odd. Some other folks on other forums have observed this behavior before - apparently it's not the first time that it's been happening. When I asked in the Sandboxie realm, the advice was to uninstall ESET to get Sandboxie working. I'm hoping that the advice from ESET isn't to uninstall Sandboxie!
  22. Hello, Recently, changes to either ESET's definitions or modules have caused a problem with the program Sandboxie. Everything was working splendidly until yesterday morning (03July2019, ~7:00AM Pacific Standard Time). I have a Sandbox set up so that Chrome will launch within it automatically, and upon closure of Chrome, the sandbox is purged via an auto-delete command. The autodelete command is now failing due to the fact that ESET is keeping files within the sandbox open, even after all processes in the sandbox are closed. Tracking the issue with Process Explorer reveals that,
  23. Hello, My ESET Cyber Security for OSX License was set to expire very shortly, so I renewed the license in order to maintain protection. Despite the charge for the purchase showing up on my credit card just fine, and despite re-entering my license key, ESET is still telling me that I'm about to expire in less than a day. Is there a way to remedy this, since I have been charged already?
  24. Thanks very much! I've sent along the ESET Log Collector logs in a private message. Any help you can provide would be greatly appreciated. Should it happen again, I'll do my best to collect a Procmon log for certain.
  25. Hi All, Recently, ESET auto-updated its modules (just a few minutes ago). I'm currently on the latest version of Windows 10 (NOT in the insider program). I only noticed the modules were updated, because ESET started throwing errors. The following error popped up in the lower right of my screen: Afterward, ESET said to reboot, so I did. After rebooting, everything seemed fine, but ESET took a while to fully load. Then, once loaded, I noticed these errors in the Event log: Is this a problem? Is ESET working appropriate now, or is something broken? It appears to be f
×
×
  • Create New...