In order to vote, comment or post rants, you need to confirm your email address.
You should have received a welcome email with a confirm link when you signed up. If you can't find the email, click the button below.

@iAmNaN after thinking about it. Could also be a hardware problem that makes the pc reboot. And windows sometimes "fixes" it with a update function. But it's a VM so probably you just need to update when asked

@AlgoRythm Win 10 Enterprise can definitely set to not automatically update. It would be rather embarrasing for a system to start updating in the middle of a prod implementation, so MS did give that control to the Admin for that very reason.

Why u don't save? I always have my fingers over Ctrl+S. Too many bad moments of blue screens, crash, power outage, accidentally pressing the shutdown button in the keyboard, etc. (Yes, the last one really happened to me).

@AlgoRythm if it's Enterprise then it's your fault for not configuring the update properly. There's a policy to never ever restart while there's user logged in without user's consent.

Mine configured to auto install all updates which do not require restart and never bug me for restart, because I shut down the computer eventually every day. So it quietly dies its job and almost never asks me anything and never forces restarts (because most updates don't even need restarts).

Are you fucking serious? Default config should be a SENSIBLE default that may require some changes here and there to meet individual needs. Randomly rebooting your PC for updates is not sensible at all.

And that's nice that it didn't happen to YOU. Doesn't mean it never happens. By default, and I'm quoting Microsoft's support page here, "Windows will try to restart your device when you're not using it". https://support.microsoft.com/en-us...

Looking further into it, this means Windows restarts when the user has simply been inactive (for example away from the machine, or in this case using the host OS instead of the virtual machine) for a while. How is it sensible to just restart in that case, completely disregarding potential data loss? That's a fucking horrible default.

@kenogo I will repeat myself: I've never had forced reboots ever even without my tailored configuration. Default config is pretty sane. I don't know how people get forced reboots if they use their PCs in normal ways, like, fucking, shutting down the PC at least sometimes instead of constantly keeping it on hibernation/sleep.

Forced reboots are most probably PEBCAK. There are at least active hours which block such "inactive" reboots.

@kenogo normally it says application x has unsaved shit and you have to press "do as I say".

On my workstation it even says that when there is nothing.

And I never have had windows just rebooting without a message or shit. I think he might have a virus or trojan maybe. I think we never know. It doesn't matter since his rant is he lost stuff, which is sad. He didn't save like a paranoid like I do, that's his lesson.

@sigfried virtualization can always go tits up. Especially gpu implementations are hard and if windows loads and unloads some shit for updates or restarts them unexpectedly, the driver could fuck up. Also could be a fuck up in the representation only

Case in point. I use a Win 10 Home laptop to remote access into work. This morning it installed a bunch of updates, and notified me that it will reboot outside of active hours. That's the point. Even home won't reboot on me during active hours, which is why I haven't ever experienced that. Maybe it's different if your are running a very old version of the OS. Dunno.

@kenogo When you set up the PC it asks for the active hours. If you updated it won't ask, but it's only going Settings, typing "active Hours" open the page and the set them. If you care about that it's not much.

@kenogo dud just fking do your updates regularly and windows will NEVER Ever shut down on its own.

I do my updates when they arrive and it only shows me that in the shutdown menu with its "update and power off" label.

After during on my surface after a few months it only showed me the "hey you have some important updates would you like to reboot now or later" dialog. After clicking later windows is cool with that. It only bothers you again if you do not reboot it and do the pending updates.

It only does this if you neglect updates for an extended period of time. And it does that only when there is an update that is relevant to the security of the system.

Just like @irene I never had unexpected reboots with any of my windows computers