The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Indeed, I always thought there was something fishy about that. But done properly, they do kipper long time. I tend to overdo mine, usually herring on the side of caution. I'll get my coat now. In fact it's raining, so I'll get my mac-kerel.
So my work PC rebooted some time in the middle of the night, and I'd forgotten to save a notepad file with some notes, and another app that contains my "engineering log notes". Needless to say, those edits (fortunately minor) were lost.
My coworker has been using this for a month now, and hasn't had a single reboot from a Windows update:
I've made the observation just a few days ago somewhere here in the lounge that the problem isn't in stopping updates...it's stopping the unwanted reboots. Subtle, but oh-so-important difference.
I use WSUS to control what updates get offered to my systems, and I have my systems set up to prompt me when they find something new (nothing gets installed automatically). But once an update is installed and is waiting to reboot - you're still at MS's mercy. It doesn't sound like this particular utility is making the claim it can do anything to prevent the reboot.
My current plan is to use some version of Windows Server as my next development VM. I've never had a server OS reboot unexpectedly, from NT 4 onward (as opposed to client OSes). Server versions will wait patiently for weeks and months.
Last Visit: 16-Jul-19 21:00 Last Update: 16-Jul-19 21:00