Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I know people who never update their machine because of this.

HA!

I was just testing a VR app that has a Windows component when things started failing in VR. I took off my headset and noticed my test machine going through power-on self test.

"Oh crap!", I thought, "a bug caused the system to reboot".

Nope. Just Microsoft deciding it's time to apply some updates. Doesn't matter that I scheduled for a time that I wouldn't be testing.

I've NEVER been able to successfully gain control of this, despite reading up on it and doing all the recommended things.



This way has always worked for me

    %windir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator
rename Reboot files and add them as folders (you'll need to override file permissions).

https://www.joe0.com/2019/10/17/how-to-prevent-windows-10-au...


I'm convinced the "schedule" thing doesn't actually do anything. It worked in Windows 8, and that's the last version of Windows where updating was (almost) tolerable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: