Hacker News Reader

So this comes up every time Windows comes up. I have a "Pro" version, went into Group Policy Editor and changed updates to require user action. This setting is supported by Microsoft and persists through updates. It only updates if I tell it to update.

Is that too hard to discover? Do you use a Home edition? (Obviously if you use any unsupported registry hacks it can revert to default behaviour any time...)

View on HN

I have already tried this and all of the other recommendations out there including Shutup10 (on Win 10 Pro). It's quite possible it was working and got reset on an update, lots of things seem to get reset.

But whatever the actual case, it's not at all obvious what triggers the reboots or why. It doesn't even have the courtesy to ask. It just does it and loses all my current work and VM states. The deliberate removal of direct user control is absolutely nuts. I didn't buy my computer with its primary purpose being applying Windows updates and rebooting. It's there for me to use for doing work, and it's failing at that by placing Microsoft's whims above my needs.

You think Microsoft hid that in a GPO because it has great discoverability?

Reply on news.ycombinator.com