It's not the most convenient way to postpone a reboot but it works I do understand the logic of having to reboot after doing certain important and maybe bulky updates but it is funny that we were able to just not reboot with previous versions of Windows Server but just has to reboot and schedule it right away.
I think it is Microsoft trying to enforce better stability. Despite telling people for years and years that they should not apply patches and then wait extended periods of time before rebooting, people continue to do it. Running a system that has been patched, yet not rebooted, is one way to have a less stable system. Some files which do not need a reboot to take effect have been placed into operation.
Other files which need a reboot to take effect have not been placed into operation. The stable environment wants all patched files in effect. Yes, the system works, but the longer it works in this manner, the higher the probability that something will occur that was not tested, as the tests include the content of the patch. The counter argument is 'it is my system and I want to have full control of it', which is a valid point.
But at the same time, the arguer will hold Microsoft accountable for any type of instability, even if they are not following Microsoft's recommendations for patch application. If you want to control reboots, implement a complete system that controls the application of patches. Then you can apply the patch at the time you will allow a reboot. You are in complete control of the patch and the reboot, thereby satisfying the desire to have complete control of the system while at the same time ensuring your system is as stable as Microsoft can make it.
How about crazy idea microsoft lets me schedule one day a week to reboot? Sure, i CAN implement patch control software. I might even find something that's free. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals.
Sign in. United States English. Ask a question. Quick access. Search related threads. But you probably hate just as much when all of a sudden, right when you were in the middle of something important, your device restarts.
It just finished some important updates. Windows 10 is the most complex OS that Microsoft released so far. One of the reasons why it performs so well is the fact that it receives constant updates, almost on a weekly basis. Important fixes are introduced, useful patches are implemented, the system installs it automatically and then, it has to reboot, for the changes to take effect.
We have something extra for you. Step 4: Right-click Windows from the left panel, select New and then click Key to create a new key. Name the new key WindowsUpdate. Name this new key AU. Once you complete the steps above, you can prevent Windows Update from automatically restarting your PC.
If you want to disable automatic reboots after installing updates in Windows 10, follow the steps below. Step 2: Find the Reboot file and take ownership over it. All users and groups should be removed. You can remove the left ones manually. After performing this process, check if you successfully disable Windows 10 automatic restart after updates. Troubled by the issue Windows Updates cannot currently check for updates?
0コメント