I see. This now strongly suggests a routing or ARP-level issue specific to Windows — possibly triggered by a misapplied update or a corrupted route/ARP cache entry. You can try this.
- Clear ARP Cache
Open Command Prompt (Admin) and run:
arp -d *
This clears cached physical-to-IP mappings. Corruption here could block local access to your router.
- Manually Ping Router and Trace Route
Try pinging your router directly:
ping 192.168.1.1
Then trace the route:
tracert 192.168.1.1
If ping fails immediately, Windows can’t reach even the local router interface.
If tracert shows a timeout or redirect to a different route, it confirms a route corruption.
- Check for Static Routes
Run:
route print
Look under Persistent Routes and Active Routes.
If you see entries routing 0.0.0.0 or your subnet through something other than your main router, that’s a problem.
Look for anything odd or different compared to the access point route table
Temporarily Disable IPv6
Some routers have poor IPv6 handling, and Windows might prioritize IPv6 improperly.
Go to:
Control Panel > Network and Internet > Network Connections
Right-click your active connection > Properties
Uncheck Internet Protocol Version 6 (TCP/IPv6)
Click OK and test again.
- Check Windows Firewall / Security Software
A recent Windows update may have flipped something in Defender Firewall or a 3rd-party firewall (e.g., ZoneAlarm, Bitdefender).
Temporarily:
Disable Windows Defender Firewall
Disable any third-party security tools
Then retry connection via the main router.
- Try Safe Mode with Networking
Boot into Safe Mode with Networking:
Hold Shift while clicking Restart
Navigate: Troubleshoot > Advanced Options > Startup Settings > Restart
Press 5 or F5 to enter Safe Mode with Networking
Now test the main router again. If it works, a startup service or driver is interfering.
Next Steps
If your other Windows laptop works fine, compare its route print, IP configuration (ipconfig /all), and network adapter settings to the affected one.
You can even export working configs via:
netsh interface ip dump > good_config.txt
and compare with the broken one.
Regards