Note: This approach may seem a little heavy handed, but sometimes you have to do it. Once the server is backup, you can comb event logs to see which updates have failed and why. PSTOOLS>psexec.exe \\mybrokenserver shutdown /r -t 0ĥ. This will kill the hung process, and upon next reboot, will skip the updates which are failing. PSTOOLS>pskill.exe \\mybrokenserver trustedinstallerĤ.
Open CMD/Powershell as admin, and run pskill. Disable the Windows Management Instrumentation service and the Windows Module Installer Service.ģ. Open Services.msc, and connect to the Server in question.Ģ.
Download this and unzip it to a directory of your choice.ġ. To fix this issue requires the use of the PSTools suite from Microsoft (). I decided to give it 2 hours before deciding to do something about this, as Maintenance Windows only last for so long. The issue this particular post addresses is following a failed application of Windows Updates on reboot for Server OS's, the screen will say: Windows Updates - We all have to do them, and as much as you try and try to avoid any potential issues with them, inevitably you will get a problem which can be quite scary! SFCFix version 3.0.1.0 by niemiro has completed.It's been a long time since i've posted here but I thought I would share something which I have experienced recently. RegistryScript:: directive failed to complete successfully.įailed to process all directives successfully. After a while it reboots automatically and server comes back normal on login screen. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\ with error code ERROR_FILE_NOT_FOUND. The ones that failed, fail after the reboot with the message: Failure Configuring Windows Updates - Reverting changes. zip script file at C:\Users\barruda\Desktop\SFCfix.zip Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
0 kommentar(er)
