Why does firewall turn off by itself




















Windows 10 Forums. BiNightMan Win User. BiNightMan, Apr 5, Anne Fuj Win User. Anne Fuj, Apr 5, Yashwanth Kotakuri Win User. We regret the inconvenience you have experienced. You mean to say, the option is grayed out? Is this started to happen recently? What happens when you tried to turn on Firewall? Usually, Windows Firewall shouldn't be in turn off state unless you have another firewall turned on.

Turning off Windows Firewall might make your PC and your network, if you have one more vulnerable to damage from worms or hackers. Select Turn Windows Firewall on or off on left pane. You might be asked for an admin password or to confirm your choice. Select Turn on Windows Firewall checkbox's and click OK Note : If your PC is connected to a network, network policy settings might prevent you from completing these steps. For more info, contact your administrator. Keep us posted if you require further assistance.

Before the reformat, this escalated to where I had to turn it back on, and eventually it would not stay on regardless of what I did. I also get an occasional error message warning me that instructions at referenced memory location cannot be accessed because a particular memory location i. This is my primary office computer and I need to get it happy. Share Flag. All Comments. Collapse -. Windows firewall is cr p anyway - Get another one. Thank you No idea - but it happens on my system too.

Firewall Turns itself off. Back to Hardware Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.

Track this discussion and email me when there are updates. Reset Post Submit Post. Related Discussions. Stephen: even by permanently shutting down AVG the firewall stills gets disabled. Moreover, AVG is only covering the antivirus purpose, it has not the firewall module activated nor purchased. If I get back to the previous update, however, it probably will still try to someday re-apply the update though like it did now , so I was wondering whether there was a cleverer solution.

Not sure about a clever solution but if you uninstall the Anniversary update and it stops, you know it's the update. There's been a number of issues with the AU which Microsoft are looking at so I presume future patches will fix any errors that have been discovered. Stephen Ok thanks, I will revert to the previous update and update the question : — briosheje. Stephen Reverting to the previous-update version seems to have fixed the issue, hence I think I will not update until I'm forced to.

Thanks for the tip :. Add a comment. Active Oldest Votes. Improve this answer. Run5k : Yes, it is in a domain environment. I was unable to guess the issue because we hadn't full control on the server, hence we were unable to understand where the problematic was.

After formatting the machine multiple times and noticing that the issue was only happening once the machine was being put in the domain, we guessed that the issue was probably server related and it was, as expected. In a nutshell: windows firewall was of course not the issue, though it was very hard to guess what the problematic could exactly be.

We are always glad to help, but this may serve as a rather valuable "lesson learned" regarding the need to be very thorough with the details you include when you originally post your question. For example, I manage several Windows domains. If you had told us back in October that this machine belonged to a domain, we probably could have helped you reduce those "months of investigations" down to merely hours of troubleshooting, instead. It makes a big difference. Run5k : You're right, I wouldn't even say that I didn't think that it could've been a "relevant" point, I just had excluded such because other machines in the same domain had no issues, while this one had which kind of lead me to believe that the issue should've been related to that machine specifically.

I understand what you are saying, but within the Super User realm it is better to provide too much pertinent information, rather than not enough. As I said before, we are always glad to help. However, when you author a new question and ask the volunteers for their expertise, it is unwise to assume that some factor is not a potential root cause of the problem.



0コメント

  • 1000 / 1000