Every. Single. Time.
-
This post did not contain any content.
That's always so annoying, because Windows isn't my default boot entry, so I need to babysit its "totally not a reboot" update.
-
This post did not contain any content.
Idk how it's working for you guys, but I've not once had it actually shut down after clicking update and shut down. It always restarts myb once or twice and finishes at the lock screen, it just doesn't shut down. I always have to manually turn it off after it finishes.
-
That's always so annoying, because Windows isn't my default boot entry, so I need to babysit its "totally not a reboot" update.
I somewhat get it - end as much processes as possible, apply everything that is possible, then restart and apply the remainder. My pet peeve is just that it should automatically shut down after applying the updates instead of staying at the lock screen, when I say install and shutdown...
-
I somewhat get it - end as much processes as possible, apply everything that is possible, then restart and apply the remainder. My pet peeve is just that it should automatically shut down after applying the updates instead of staying at the lock screen, when I say install and shutdown...
it should automatically shut down after applying the updates
Okay, that part it does for me though. That's extra annoying for you then.
apply everything that is possible, then restart and apply the remainder
Yeah on one hand I get the concept, on the other macOS and Linux manage without, and I don't really remember older Windows doing this either, so I wonder if there is a real reason why it's needed, or they just engineered themselves into a bad corner...
-
This post did not contain any content.
Windows is so full of stupid little shit that should have been fixed years - if not decades - ago. Sleep mode broken, folder customize options don't apply to subfolders despite offering that choice, the OP. Sigh.
-
Idk how it's working for you guys, but I've not once had it actually shut down after clicking update and shut down. It always restarts myb once or twice and finishes at the lock screen, it just doesn't shut down. I always have to manually turn it off after it finishes.
Dunno what to tell you, man. Update and shut down always works perfectly for me. It updates, restarts to finish the update, then shuts down. Works every time.
The only thing I can think of is that you're being impatient and manually shutting he machine down after the restart, instead just letting the OS do its thing.
-
Dunno what to tell you, man. Update and shut down always works perfectly for me. It updates, restarts to finish the update, then shuts down. Works every time.
The only thing I can think of is that you're being impatient and manually shutting he machine down after the restart, instead just letting the OS do its thing.
I'm most definitely not interrupting it, I can go away, do something else, and it will still be on the lock screen after rebooting. I'd then have to click on shut down again.
-
it should automatically shut down after applying the updates
Okay, that part it does for me though. That's extra annoying for you then.
apply everything that is possible, then restart and apply the remainder
Yeah on one hand I get the concept, on the other macOS and Linux manage without, and I don't really remember older Windows doing this either, so I wonder if there is a real reason why it's needed, or they just engineered themselves into a bad corner...
I wonder if there is a real reason why it's needed, or they just engineered themselves into a bad corner...
Same. They do have some features that sound kinda sane and may play a role here - like the system field are write protected. Programs can request to run a script on start-up to modify them before the write-protection kicks in. Also they might want/think it's a good idea to run some part of the updates on the new kernel version instead of the old one or maybe do a cleanup on a successful boot or so. Also, maybe they want to force a reboot straight to Windows before the update is finished to prevent problems with dual boot - that could rule out "install and shutdown and only continue with the remainder on the next boot". Also it might be for convenience, as the next boot is as fast as usual and you do not see 10 mins of "applying updates" when you didn't calculate with that.
But if you offer "install and shutdown", it should shutdown in the end and not stay on the lock screen and hopefully go into sleep mode...
-
I'm most definitely not interrupting it, I can go away, do something else, and it will still be on the lock screen after rebooting. I'd then have to click on shut down again.
The only other thing I can think of is that you're dual-booting and Windows isn't playing nice with GRUB as usual.
If that's the case, well then this is why I gave Linux and Windows their own dedicated drives, with a switch installed on my case to physically select the drive. That way they can both have their own bootloaders so Windows can't get in the way. They're not even aware that the other OS exists.
-
The only other thing I can think of is that you're dual-booting and Windows isn't playing nice with GRUB as usual.
If that's the case, well then this is why I gave Linux and Windows their own dedicated drives, with a switch installed on my case to physically select the drive. That way they can both have their own bootloaders so Windows can't get in the way. They're not even aware that the other OS exists.
Yeah no I've never dual booted on these devices.
-
Windows is so full of stupid little shit that should have been fixed years - if not decades - ago. Sleep mode broken, folder customize options don't apply to subfolders despite offering that choice, the OP. Sigh.
I had to disable the power button on my tower. By default, if you click “shutdown” the computer will freak out about the possibility someone might lose work even if nothing is happening but if your cat bumps the physical power button, even in the middle of a game, the whole thing shuts down faster than than those safety table saws that blow themselves up to save your finger.
