I didn’t think about sconfig earlier because all the platforms I support don’t support the core edition of Windows Server and I avoid Hyper-V like the plague since VMWare is infinitely more superior. Either way while working on a different project I found a solution to this issue it’s sconfig.

Or even on a more annoying note sometimes automatic updates interferes with your 3rd party managed patching solution. In either case what usually happens is that Windows applies these updates during that day and then the server starts acting a little strangely based on what update was applied until the server is rebooted. Or more specifically now with Server 2016 and Windows 10, your computer starts checking and applying updates based on the loosely defined schedule of “active hours”. I’m sure we’ve all been in the spot, where a Windows Server for some reason or another decided to run windows updates and now needs a reboot.