Why Windows Defender Firewall Blocks Chrome Connections
Windows Defender Firewall can block Chrome’s outbound TCP connections if the application is not listed in the allowed apps list or if a third-party installation modified the firewall rules incorrectly. This is particularly common after Chrome updates, which may reinstall the executable to a new directory path that is not covered by the existing firewall rule.
Windows 11’s built-in firewall also implements a stealth mode that silently drops inbound connections from unfamiliar sources. While this does not directly affect outbound connections from Chrome, it can interfere with the server’s ability to send a SYN-ACK if the server’s response is routed through an interface that Windows Defender considers untrusted.
Resolving Windows Defender Firewall TCP Timeouts
Adding Chrome to Windows Defender Allowed Apps
Open Windows Security → Firewall & network protection → Allow an app through the firewall → Change settings. Click Allow another app → Browse → navigate to C:Program FilesGoogleChromeApplicationchrome.exe → Add. Ensure both Private and Public checkboxes are enabled for Chrome.
Resetting Windows Defender Firewall to Default
If Chrome was previously allowed and is now timing out, the firewall rules may have become corrupted. Open Command Prompt as Administrator and run:
netsh advfirewall reset
This resets all firewall rules to their Windows 11 defaults, eliminating any corrupted rules that may be blocking Chrome connections. After running this command, re-add Chrome to the allowed apps list as described above.
Disabling Windows Defender Firewall Temporarily for Testing
Open Windows Security → Firewall & network protection. Toggle Microsoft Defender Firewall to Off. Test Chrome’s connection. If the timeout resolves, the firewall was the source of the block. Re-enable the firewall after testing and apply the Chrome allowed app fix.
Call to Action
Use the webs.ninja gateway to test TCP handshake latency with Windows Defender Firewall temporarily disabled. If the diagnostic shows successful handshakes without the firewall, apply the Chrome allowed app fix and firewall reset as described above.