Hacker News new | ask | show | jobs
by p2t2p 1680 days ago
Darn it, every time MS does something like it I feel an urge to get myself a Windows laptop. Gotta control myself.
1 comments

Just run it in a VM, no random reboots to hold you hostage.
What are these "random reboots" people keep mentioning?

My Windows boxes usually run about 12 to 14 days between (manual!) reboots, and those reboots are normally done to switch between operating systems.

It's been literally years since Microsoft removed automatic reboots and even updates can be be postponed for several weeks and scheduled at the user's convenience.

There are plenty of bad things about Windows, but tired old stories about "random reboots" or bluescreens just aren't part of it anymore.

Windows update will under specific circumstances automatically reboot the system. Any unsaved work will be lost. This, to my knowledge, has not been fixed yet.
I'd be very interested in a source for that as I've not encountered this and haven't read about it in technical publications either.
When there's an update that requires restart waiting to be installed, don't restart Windows for few weeks and leave computer idle outside active hours. Windows will install the update outside active hours and reboot automatically.

It happened to me before. I know of three occurrences of this happening to other people in this year alone.

Quick google search:

https://www.extremetech.com/extreme/316460-how-to-stop-force...

https://superuser.com/questions/957267/how-to-disable-automa...

https://community.spiceworks.com/topic/960453-windows-update...

https://answers.microsoft.com/en-us/windows/forum/all/disabl...

https://techgenix.com/turn-off-windows-10-updates/

Interesting. Still doesn't match the "random reboot" claim.

First of all, rebooting outside of active hours and while the machine is idle is the expected and intended behaviour (esp. in Home edition).

Secondly, pushing back updates only works for several weeks - again working as advertised and by no means random.

Inconvenient? Maybe, though I honestly fail to see a scenario in which continuous operation for weeks is absolutely required on a desktop system, but YMMV.

But it's neither "random" nor unexpected in any way. If a properly scheduled reboot of an online machine once a month is unacceptable, then Windows just isn't the right OS for the use case.

Just a quick question - do you work for or contract with Microsoft or their contractors? Because the whole Internet basically disagrees with your take here.
OH but each time you boot it up, it's slow as molasses as it force runs those updates, ask me how I know.