[tobyjsullivan]

Over my 35 years of computer use, most hardware failures (very, very rare) happen during a reboot or power-on. And most of my reboots happen when installing updates. It actually seems like a very high probability in my limited experience.

Of course, it’s possible that the windows update was a factor, when combined with other conditions.

[fc417fc802]

There's also the case where the hardware has failed but the system is already up so it just keeps running. It's when you finally go to reboot that everything falls apart in a visible manner.

[da_chicken]

This is one of the reasons I am not a fan of uptime worship. It's not a stable system until it's able to cold boot.

Say you have a system that has been online for 5 years continuously until a power outage knocks it out. When power is restored, the system doesn't boot to a working system. How far back do you have to go to in your backups to find a known good system? And this isn't just about hardware failure, it's an issue of configuration changes, too.

[phire]

I also notice that people with lots of experience with computers will automatically reboot when they encounter minor issues (have you tried turning it off and on again?).

When it then completely falls apart on reboot, they spend several hours trying to fix it and completely forget the "early warning signs" that motivated them to reboot in the first place.

I've think the same applies to updates. I know the time I'm most likely to think about installing updates is when my computer is playing up.

[ssl-3]

I try to do the opposite, and reboot only as a last resort.

If I reboot it and it starts working again, then I haven't fixed it at all.

Whatever the initial problem was is likely to still present after reboot -- and it will tend will pop up again later even if things temporarily seem to be working OK.

[close04]

> Whatever the initial problem was is likely to still present after reboot

You only know this after the reboot. Reboot to fix the issue and if it comes back then you know you have to dig deeper. Why sink hours of effort into fixing a random bit flip? I'll take the opposite position and say that especially for consumer devices most issues are caused by some random event resulting in a soft error. They're very common and if they happen you don't "troubleshoot" that.

[ssl-3]

With any system: When I can find and correct the problem out of the gate, then it remains corrected the issue does not recur.

[fc417fc802]

How do you avoid sinking time into chasing illusory bugs?