Skip to content

1. Windows Troubleshooting

A few Windows symptoms show up constantly, each with their own specific diagnosis.

Symptom What's actually happening
"Limited connectivity" / no internet, but Wi-Fi shows connected The adapter couldn't reach a DHCP server, so Windows self-assigned a link-local address instead
Slow profile load at login A large/corrupted user profile, or a startup program hanging before the desktop finishes loading
A service won't start Check its startup type and dependencies before assuming it's broken
Clock drift (time is wrong) Time sync failed — and a wrong clock can itself break certificate checks and logins that depend on accurate time

A real example from this very course

Setting up this course's own network connection, an adapter came up with the address 169.254.9.185 — exactly the symptom in the first row of the table above. That 169.254.x.x range is APIPA (Automatic Private IP Addressing): Windows's way of saying "I never got a real address from a DHCP server, so here's a private placeholder I made up myself." It's not a random glitch — it's Windows telling you specifically what went wrong, if you know how to read it.

Try it

A laptop shows "Connected" to Wi-Fi but nothing loads. You check its IP address and see 169.254.x.x. Explain exactly what that number is telling you, and what you'd check next.

Tip

Any address starting with 169.254 is diagnostic information, not just a weird number — it always means "no DHCP server answered," never anything else.

Play it

Open the Software Troubleshooting Lab and use the Windows tab.

Next: Mobile OS Troubleshooting →