3 ms·
There is a nice little tool to stop the reboots: https://www.udse.de/en/windows-10-reboot-blocker https://www.udse.de/en/windows-10-reboot-blocker It changes
by ganomi 8y ago
There is a nice little tool to stop the reboots:
https://www.udse.de/en/windows-10-reboot-blocker https://www.udse.de/en/windows-10-reboot-blocker
It changes the active hours every hour so that you will never be outside of active hours.
- AckSyn 8y agoI find this one to be more palatable, and it being powershell exposes the user to the actual commands that update and change the active hours: https://github.com/Maimer/update-active-hours https://github.com/Maimer/update-active-hours
- mintplant 8y agoYears ago I followed a guide I found online [0] which involves renaming the "Reboot" scheduled task file and creating a folder with the same name in its location, so that the OS fails to re-create the task file. Haven't had an unexpected reboot since. This technique was familiar to me from the Kindle jailbreaking scene, in which creating a directory with a certain path would cause the Kindle's auto-updater to error out when it tried to `rm` what it saw as a preexisting partially-downloaded update file (the Kindle's OS is Linux-based, so the file-delete operation fails on a directory). [0] https://www.windowscentral.com/how-prevent-windows-10-rebooting-after-installing-updates https://www.windowscentral.com/how-prevent-windows-10-reboot... (including the "Additional Steps")
- robocat 8y agoBut when you need to reboot for any other reason (e.g. Windows bugs out), then the update happens, and your have to wait. Shift-shutdown didn't prevent this either. Unexpected updates was a primary reason I am now using Linux full time (rather than part time as previously).