Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
ESET
Configure ESET as default-deny (bye ransomware!)
Message
<blockquote data-quote="davisd" data-source="post: 821887" data-attributes="member: 77647"><p>The first thing I believe is very important, that there's no other security programs installed along Eset, so there's no interference, if one goes with HIPS rules. You might have made some rule too generic if your windows broke apart, make sure you didn't tick "Files/Registry entries" at "Operations affecting", those two should be used only to create very specific rules and locations. You should have received a warning at the end of HIPS rule creation. You must identify very specifically what was blocked via "Log files" to find the culprit, because some important information might slip by through your eyesight at HIPS prompts. But I know the feeling when Eset smashes your PC because of the HIPS rules.. you just don't want to use Eset ever again. One have to overcome frustration after it has happened, at the end, it's just a human error. Shouldn't be an issue with 1903 and standard account, I'm on the same.</p><p>[ATTACH=full]215615[/ATTACH]</p></blockquote><p></p>
[QUOTE="davisd, post: 821887, member: 77647"] The first thing I believe is very important, that there's no other security programs installed along Eset, so there's no interference, if one goes with HIPS rules. You might have made some rule too generic if your windows broke apart, make sure you didn't tick "Files/Registry entries" at "Operations affecting", those two should be used only to create very specific rules and locations. You should have received a warning at the end of HIPS rule creation. You must identify very specifically what was blocked via "Log files" to find the culprit, because some important information might slip by through your eyesight at HIPS prompts. But I know the feeling when Eset smashes your PC because of the HIPS rules.. you just don't want to use Eset ever again. One have to overcome frustration after it has happened, at the end, it's just a human error. Shouldn't be an issue with 1903 and standard account, I'm on the same. [ATTACH type="full"]215615[/ATTACH] [/QUOTE]
Insert quotes…
Verification
Post reply
Top