davidm71 0 Posted September 8 Share Posted September 8 Hi, Eset is blocking my Starfield mod from working and only fix I have is to disable protection. I tried creating exclusions to the path of the main install folder but not sure if it translates all way down to sub folders or is there an easy way to get Eset not to block my mod? Thanks Quote Link to comment Share on other sites More sharing options...
itman 1,602 Posted September 8 Share Posted September 8 1 hour ago, davidm71 said: Eset is blocking my Starfield mod from working and only fix I have is to disable protection. Just what Eset features did you disable? Hopefully, not all of Eset. If you temporarily pause the Eset firewall, does the issue not occur? Quote Link to comment Share on other sites More sharing options...
davidm71 0 Posted September 8 Author Share Posted September 8 Its just like I said at the start. Eset blocks the mod from working. Want to create an exception. Thanks. Quote Link to comment Share on other sites More sharing options...
itman 1,602 Posted September 8 Share Posted September 8 Assumed is it is the Eset firewall that is blocking the Starfield mod from establishing network connectivity. Start the mod. Then open Eset GUI and navigate to Network Protection section. Under the "Resolved blocked communication" area, it should show a non-zero blocked communication count. Mouse click on Resolved blocked communication and it will show all connections blocked by the firewall. You can then unblock the activity and have Eset create a firewall rule for it. Ref.: https://help.eset.com/essp/16.2/en-US/idh_wizard_epfw_troubleshooting_type.html Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,844 Posted September 9 Administrators Share Posted September 9 Is it a file that is detected and cleaned? Could you provide the appropriate record related to the issue from ESET's logs? Quote Link to comment Share on other sites More sharing options...
davidm71 0 Posted September 9 Author Share Posted September 9 Well I think I solved the problem. I went to logs and found the log for the Eset blockage and right clicked and selected created exception and now it works. I also submitted it as a false positive file to Eset directly. Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.