zamar27

The problem is, I don't want to get rid of this app, as it conveniently and reliably blocks Cam and/or Mic access at driver level as I choose. It looks we are back here to Application Control issue. What Eset module causes this particular popup? Can I add blocking this URL as a new Rule to suppress the popup?

I will post it with logs, but the address is always exactly the same, it looks like the started app tries to load some script from the website, may be update check or such? Of course its not related to Webcam protection, I just posted it as an example of annoying popups coming up every time, and no way to stop them. 😊 What Eset module is engaged here?

Thanks for pointing to that option. But I think, the issue is a bit more generic. Look at screenshot below, this popup comes each time the app is autostarted at Windows boot. How would I get rid of this one? Another issue is, the user would be expected to master in-depth knowledge on Eset functions and UI to get to the bottom of it. As a bonus, its a good thing to learn more about PC protection modes, but can an average Joe do that? Or instead he would press the Forum Panic button - the big red one?

I think there's misunderstanding here. Once the rule is created, Eset remembers it fine. But it still shows a popup each time Skype is launched, informing access to webcam was allowed. What I suggest is adding a checkbox on such kind of popups "Don't show again". 😊 However, its not really that annoying, when popup time is set to 5 sec if important from marketing prospective.

I think what the OP wanted to ask: how to suppress repeated notifications? Like about the same program accessing your webcam, or when the same URL is always blocked when starting a certain application etc. I too seen the same popups coming each and every time. While most users have no intention to suppress relevant Eset protections, it would reduce annoying aspect of popups by offering a checkbox on them "Don't show again". For example, Skype users can read one time "Skype access to webcam was allowed" after they allowed it, but many would prefer to not read it every time when launching Skype. In fact, Eset in Firewall Interactive Mode doesn't show popups "Access to a website was allowed based on previously saved rule". Same "no annoyances" notification logic should persist throughout other Eset modules, except when repeat notification is required or preferred by user. As the product gets more diverse and complex, it does require more coherent notifications control.

Hi Marcos, IMHO this forum will only benefit from some share of humor. Its not really a generic panic button, but rather a place to make people interested in Eset protection tech, and give you some bugs feedback. Also I found improper that some folks suddenly allowed to mentor others while refusing to address the OP concerns. Why this offtop is allowed here?

Pls post screenshots marking problem areas in red circle. I beg you sir. 😂

I don't think you read it right: 64К Private Bytes / 160K Working Set.

Check next time if these files are Read Only, and your user has Write permissions.

What's the difference btw OBJECTS and FILES in Real-time File System Protection? Why FILES are separated to Additional Threatsense Parameters? 😉

At changing settings, Eset may be saving several files to different dirs, so it looks like some of these files may be saved with Read Only flag, which may be visible in ProcMon log, and also in Resmon.

Try resetting your PC BIOS.

Try to relogin to Windows instead of reboot after the error happens.

Some VPN plugins do not encrypt https traffic at all, in contrast with VPN desktop apps, or encryption level is degraded. Generally, VPN purpose is not only encryption, but obfuscating traffic origin using other techniques. Also, what is the purpose to inspect regular archives? They can be inspected at extract time to save resources. How would Eset differ an encrypted archive from not?

As to VPN plugin, it allows to encrypt browser traffic including file "downloads", so it all comes to the sequence, whether the traffic is decrypted by the plugin before Eset checks it.

Try refreshing Firefox. Something in its Profile might be wrong to cause such behavior regardless which program launches it.

Giving more examples, not a single modded Android apk was detectable regardless how malicious, they all have encrypted content, hopefully catched at run time. 😉 Broader speaking, the definition of "malicious action" is also at review. Yesterday's Windows MS Office updates led to constant OneNote crashes. Was it by design to push folks documents to MS cloud by forcing to upgrade to new OneNote app? Or unintended consequence of previous Reg changes not expected by the update? One can say, the update IS a virus. 😋

For extra precaution, always check questionable origin archives with VirusTotal, but make sure beforehand they're not encrypted, including archive parts, thus making virus detection impossible. Though not all detected files by any A/V are in fact malicious.

What kind of network connection do you use? Is it established before programs check for updates? If using VPN service, which one? What's your Windows version? As to Firefox issue, try this: - set MS Edge as Default Browser in Windows Settings. Does the issue remain? - Refresh Firefox, then set it Default Browser again. Was the issue fixed? As to Grand Theft Auto 5 error, Eset modules, set by you Firewall rules, or Registry settings may be blocking or conflicting with certain game files or traffic for some reason. Try multiple solutions listed in Exception code: 0xc0000005 Crash, whitelist mentioned files or folders in several Eset Advanced Settings sections (Network protection, Internet protection, Computer protection), reset Firewall rules, and report back results.

I just tested it again, and indeed the error persists. Eset Firewall in Interactive Mode doesn't re-read saved rules DB after being disabled for some time, and then re-enabled. I had to re-login, meaning restarting Eset, to force it read the existing rules. Switching to pre-release resulted in no improvement, since network Protection module wasn't updated for awhile. I don't know why the issue shows up intermittently. It might be linked to using a VPN.

I reported the same bug a few weeks ago. But then these errors seems to stop, so it looks like either it was already fixed for some time, or may be you need to cleanup your PC using some system cleaner and reboot. I do cleanup after some programs updates, including Windows updates if there are some issues. It also allows to auto recreate large system service and boot files. Sadly some programs leave remnants at update, which may conflict with new code. If that does't help, may be try to uninstall & cleanup & reinstall Eset. Consider resetting to defaults your Windows Firewall as well. The reason is, there may be other Eset features that didn't work in your setup, but you simply don't know that since you never tried to change other settings. 😉

Since Trusted zone is computed correctly in Eset Network Adapters window, this seems to be rather broken config file or Registry key issue likely caused by numerous Eset updates, or possibly relevant Reg cleanups.

For me, full device names on LAN as broadcast show up on mouse hover or clicking the device, and they are editable. Company name isn't always part of the device name, one may change device names in their own GUI. 😄

For the test, I manually added some IPs to various default Eset Zones. Then I tried to add any of default Zones to any Firewall rule. The above error persists for *any* default zone in *any* rule despite the zone being populated with some extra real IPs. But if I create a new zone, it can be added OK to rules, which accept Zones. I wonder if Eset periodically needs remnants cleanup and reinstall, since regular program updates possibly leave conflicting settings in Registry or config files. I'm always shocked by some programmers culture to leave garbage everywhere at uninstall, like its their own system, and not the user's.

No, the error occurs when submitting this Form. Also, the actual issue is its impossible to add Trusted Zone to firewall rules in some installations.