Windows 10: Windows Defender Firewall won't turn on when connected to my private network.

I am running Windows 10 1909 and when connected to my private network at home the firewall in Windows Defender won't turn on at all, but when i go in the control panel it says it is already enabled. I don't know if it's a bug or a malware infection at this point. Any tips?

submitted by /u/Rios991
[link] [comments]

:)

 

windows defender firewall

Hi Faye,

Third-party antivirus programs usually have their own uninstallers provided by the software developer. We suggest checking the developer's website or contacting their support team for assistance with uninstalling their program. After fully uninstalling the
third-party antivirus software, you may turn on Windows Defender by following these steps:

• Click Start.
• Type Windows Defender Security Center and press Enter.
• Click Firewall and network protection.
• Click Private (discoverable) network and click On.
• Click Public (non-discoverable) network and click On.

Let us know if you have any other concerns about Windows Defender.

 

Turning off Windows Defender Firewall fails

Hi seagiraffe,

I would suggest you turn the firewall off through Windows Defender Security Centre:

- Open Settings

- Select Update & Security

- Select Windows Security (left-hand side)

- Select Firewall & network protection (under the Protection areas heading)

- Select Domain network/private network/public network

- Toggle the switch to Off under the Windows Defender Firewall heading

- Note: you will need to do this for all three networks (domain, private, public)

You will see 'Action needed' from the Windows Defender taskbar/notification tray icon, however this is just because the firewall has been turned off.

Hope this helps,

Nathan

 

Computer not visible on network if Windows Defender Firewall is on

Thank you titetanium!

I allowed apps through the Defender firewall as suggested and all our computers are showing up now in the network. File sharing & Network Discovery were already allowed on private networks, but allowing on public networks in addition seemed to do the trick. Since it is a private network, I didn't think it necessary to allow on public networks, but apparently it is.
Thanks again for your help.