It does seem like magic, doesn’t it? The computer’s acting up, you reboot it, and poof, things are better again. At least for a while.
It gets even weirder when you achieve the same effect just by shutting it all down and pulling the power cord for a while.
A friend of mine once provided a nice explanation for the power scenario, and I can speak a little bit to the magical mess that is software.
Become a Patron of Ask Leo! and go ad-free!
Turn it off and back on again
Jerrold Foutz is a friend of mine who is an industry expert in the design of power supplies. Some time ago, he provided a very interesting write up on unplugging the power as perhaps the single most effective electronics-troubleshooting technique.1
The topic came up in a discussion when I recommended power-cycling a router — unplugging it, waiting 30 seconds, and then plugging back in — as a way to resolve a connectivity problem.
The fact is, electronic components can get into an odd state, and as Jerry points out, power-cycling the equipment forces the equipment to reset and restart from a known good state.
The same is true for software.
When in doubt, reboot
Complicated software (and what software isn’t complicated these days?) involves lots of things on your computer as it runs.
The longer it runs, the more it impacts.
Memory is used, released, and fragmented. Same for the disk, as programs open, read, and write local and temporary files. And then there’s the hardware — video cards, networking adapters, mice, keyboards, other peripherals — they’re all accessed continuously.
The result is that any of those (and perhaps all of them) can end up in states that can cause problems.
It shouldn’t be that way, of course, and the inherent quality of the software and/or hardware plays a huge role, but the bottom line is that it happens. Software can get confused over time.
And those technicians who ask you to reboot your device? They do so because it works more often than you might imagine.
A reboot restores all the software to a known state.
A power-cycle restores all the hardware to a known state.
Well, a mostly known state. Temporary files, installed files, registry changes, and more will remain. That’s why in extreme cases, a reformat and reinstall is a recommended solution for some computers: it returns things to a known state.
The router problem that started this discussion? Like many devices these days, routers are actually small single-purpose computers. Their internal memory tracks a variety of information relating to the network connections they manage.
The longer they run, the more likely it is that something will create a problem. It could be hardware related, as explained in Jerry’s article, or something in its software, as I’ve outlined above.
In any case, I typically reboot my own router every few months.
1: Literally unplugging the device. Leaving it physically plugged and just flipping a power switch instead will often not remove power from absolutely everything.