For the home user, this is a giant PITA for which I wholly blame MS.
For business machines, I lump the company IT in with MS, because there are Policies for this stuff they should be managing.
I say this as an IT person responsible for things like this. The first rule is don’t fuck with user machines during business hours, the second is to allow them to postpone stuff as needed.
Can only imagine getting an update, then a reboot, while I’m on an outage call trying to get a critical system back up. And hoping my laptop comes back up and my VPN still works.
Can’t say I’ve experienced forced reboots on either my home or work PC; I always have gotten an option.
Do you have to ignore updates for a while until they’re forced? I’m pretty quick with updating when I’m notified- typically that evening when I’m done with the computer.
I’ve been building my own windows PCs since 99, using every main version of consumer Windows except ME. Never been forced while in the middle of something.
With Win10 and later (I honestly don’t remember with Win 8), by default updates happen in the background, and will be applied and a reboot scheduled.
It won’t necessarily force a reboot, but it can reboot when you’re not there. I’ve had updates with reboot happen when I was away for 30 minutes, on a machine I was setting up and hadn’t yet configured policies.
The updates quietly happening in the background are still a problem because they can’t be paused or canceled and they use a lot of sysrme resources to get done. And when they’re complete, your experience is less stable till the reboot.
I usually notice them when my work computer slows down and things start having more bugs than usual. My work computer has very respectable specs
For the home user, this is a giant PITA for which I wholly blame MS.
For business machines, I lump the company IT in with MS, because there are Policies for this stuff they should be managing.
I say this as an IT person responsible for things like this. The first rule is don’t fuck with user machines during business hours, the second is to allow them to postpone stuff as needed.
Can only imagine getting an update, then a reboot, while I’m on an outage call trying to get a critical system back up. And hoping my laptop comes back up and my VPN still works.
Can’t say I’ve experienced forced reboots on either my home or work PC; I always have gotten an option.
Do you have to ignore updates for a while until they’re forced? I’m pretty quick with updating when I’m notified- typically that evening when I’m done with the computer.
I’ve been building my own windows PCs since 99, using every main version of consumer Windows except ME. Never been forced while in the middle of something.
With Win10 and later (I honestly don’t remember with Win 8), by default updates happen in the background, and will be applied and a reboot scheduled.
It won’t necessarily force a reboot, but it can reboot when you’re not there. I’ve had updates with reboot happen when I was away for 30 minutes, on a machine I was setting up and hadn’t yet configured policies.
The updates quietly happening in the background are still a problem because they can’t be paused or canceled and they use a lot of sysrme resources to get done. And when they’re complete, your experience is less stable till the reboot.
I usually notice them when my work computer slows down and things start having more bugs than usual. My work computer has very respectable specs
I agree, but this echo chamber doesn’t accept such alternate realities.