

Sounds like your IT doesn’t know how to properly orchestrate updates.
Best way to do it in a Windows enterprise environment that I’ve seen so far:
- 1 Week: Install in the background silently and finish when the machine reboots.
- After the week, 2 Days: Warn once that the machine will automatically reboot in 48 hours.
- 12 hours before forced reboot: Pop up a warning in the corner with the countdown before reboot. Options are reboot now or warn me again in X hours. If you dismiss it without selecting, it pops up again in an hour.
If your Windows machine hasn’t rebooted in a week and a half, of course you’re going to have performance issues. What, you expect devs to avoid memory leaks?
That all said, the amount of Windows sysadmins who haven’t entirely given up on wrestling Microsoft’s update bullshittery is shrinking every day.

















At around 22 years old, I met an athletic little stick of a 19 year old lady who hadn’t grown out of her rebellious phase yet. She was into a somewhat rare combination of dad-bod and bad boy, trying to maximize parental upset. Going for the complete opposite of how she appeared at first glance.
A friend in their late 20s had brought the young one along to help pretend they weren’t rounding the corner on 30 themselves. Funny thing is, the 19yo and nearly 30yo had a falling out later when the younger one settled into responsible adulthood before the older one.
Younger one got out from under her parents and settled into responsible (and domestic) adulthood almost immediately, dropping the bad boys and keeping the dad-bod thing. Married pretty quick too, to what looked like a kind snuggly bear of a guy, before I lost touch with her.