#troubleshooting
50 solutions
Kill and auto-restart explorer.exe — the classic repair for a dead Start menu, unresponsive taskbar, or glitchy icons.
Inspect any systemd unit's loaded/enabled state, active state, main PID, and its most recent log lines in one command.
Deep-link straight to a specific Windows Settings page from Run, CMD, or a shortcut — no more clicking through categories.
Purge cached DNS lookups so Windows re-resolves hostnames from scratch — the fix for 'the new server is live but my browser still hits the old one'.
One command that prints every interface with its state and IPv4/IPv6 addresses in a short table — the modern, memorable replacement for digging through `ifconfig` or the verbose `ip addr` output.
Stream new log lines as they appear — the classic way to debug services on Linux.
Use shutdown /s /t to make Windows power off automatically after a chosen number of seconds, and shutdown /a to cancel it.
The routing table is the first thing to check when traffic leaves the wrong interface or the gateway seems dead — and `ip route show` is the quick, modern way to read it.
The fastest way to answer 'is the firewall blocking me?' — netcat in scan mode attempts one TCP connection and prints whether it succeeded.
Show every router hop between your machine and a destination with round-trip times, Windows' built-in traceroute equivalent.
Drop the current IP address lease and request a fresh one from the DHCP server — the classic fix for 169.254 auto-configuration addresses.
Immediately re-synchronize the Windows clock with its time server when it drifts minutes behind or ahead.