I have a Windows Server 2025 setup as a Domain Controller and file server for a client. I'm trying to get it to install monthly patches and automatically reboot at 3 AM without needing any manual intervention. However, it just refuses to do this, and it's becoming a hassle. I checked yesterday and found it still hasn't rebooted after the latest updates. I've attached some screenshots of the settings I'm using, and they don't seem to help. It's frustrating because I have to wait a month after every tweak to see if it actually works. Any tips on how to make this server cooperate?
3 Answers
This issue has been around since the release of Server 2025. I’ve noticed that the Core edition works fine, but anything from 2022 and earlier functions better. Sometimes, it gets stuck after applying updates and won't recover unless you manually reboot. I ended up using a script to replace WSUS policies for it, which handles installation and then triggers a reboot afterward. Might be worth a shot!
Consider creating a scheduled task that reboots the server every weekend at a lower traffic time, like Saturday or Sunday at 11 PM. This way, you can run the updates whenever they’re ready and handle reboots automatically during off-hours, so it won't disrupt usage.
Honestly, Server 2025 feels like the Windows ME of server systems. It's plagued with issues, especially after certain updates. If you're using the October patches, make sure to check the Windows Release Health messages—there seem to be bugs popping up almost daily!
Thanks for the heads-up! It’s good to know I’m not the only one facing this challenge.