New-Item -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\ -Name ScheduleRestart This needs to be done only once per system. This will create a registry key to track server restart schedule.
A small 101 on the Automatic Server Restart script.įirst run the following powershell commands. Given this challenge of restart, I have written a powershell script that schedule & restart the servers. My team was in similar situation where we have to restart some 40 – 50 odd servers. It would be completely fine to restart few handful of servers however, as the number increases it may become quite laborious to restart the servers manually. System Configuration tools like SCCM provides a way to suppress the restart so that servers can be restarted in planned manner. The values that I set two days ago have not changed.Often after monthly security and critical updates, a system requires a restart. The machine has stopped trying to upgrade to Windows 10, so the registry change must have worked. We'll see if this successfully blocks the upgrade going forward. I ran Disk Cleanup and removed "Temporary Windows installation files." That folder is now gone. I updated the registry on the "upgrading" machine to match the registry of the "blocked" machine, then rebooted the machine.Īlso, thanks to the comment from I found a $Windows.~BT hidden folder with 5.1GB of content. The machine that was trying to upgrade had these values: Īnother Windows 7 machine, where I had removed KB3035583 before Windows 10 was released (and thus successfully blocked the upgrade), had these values: Further Googling led me to a registry key that looks like it controls the upgrade process.
0 kommentar(er)
