First time posting here. On to the problem at hand:
We have a production 2012 R2 terminal server that will not apply any windows updates in any way. It normally scans for updates just fine, downloads, installs, but when it comes time to reboot and apply the updates it always fails and has to revert the changes (which takes over an hour usually). This server has not been upgraded, it is a native 2012 R2 VM on hyper-v with the RDS roles and services installed. When the server was first built all updates were installed that were available at the time and for a while after updates/patches applied just fine. Then out of the blue (not sure when anymore as it has been months) it stopped being able to apply updates during the reboot process. This includes updates manually installed.
SFC /scannow reveals that there is some corruption, and DISM using the /restorehealth always fails with an error of 0x80240021 and says no operation was completed. We've tried running a DISM /startcomponentcleanup first and that completes fine, but it doesn't allow the /restorehealth to complete. We've also purged the windows update SxS directory and removed pending reboots from the registry and then tried installing updates 1 by 1 and still received the same result. We have reached a point where this server is missing quite a few critical security updates and we need to get this issue resolved.
We have run SFCFix which claims to have resolved an issue with corruption, however running SFC /scannow once again reveals there is still corruption. After running the DISM /startcomponentcleanup we have also noticed that windows update continues to scan for updates and never finds anything (meaning the scan never stops). Running overnight still found nothing, restarting the update server did not help resolve anything either. We have renamed the old CBS.log to old and it is included for reference if needed, we did however start a new log just to show the most recent information involving SFCFix, sfc, and DISM. Any help in this situation will be amazing and, ahead of time, thank you. This is a very frustrating issue.
I have tried to attach the CBS.zip but it will not let me and I cannot run the script to upload it to the servers as it does not allow me to download it from the link in the sticky. If someone could please provide information on how to upload it, it is just shy of 60 MB in size.
We have a production 2012 R2 terminal server that will not apply any windows updates in any way. It normally scans for updates just fine, downloads, installs, but when it comes time to reboot and apply the updates it always fails and has to revert the changes (which takes over an hour usually). This server has not been upgraded, it is a native 2012 R2 VM on hyper-v with the RDS roles and services installed. When the server was first built all updates were installed that were available at the time and for a while after updates/patches applied just fine. Then out of the blue (not sure when anymore as it has been months) it stopped being able to apply updates during the reboot process. This includes updates manually installed.
SFC /scannow reveals that there is some corruption, and DISM using the /restorehealth always fails with an error of 0x80240021 and says no operation was completed. We've tried running a DISM /startcomponentcleanup first and that completes fine, but it doesn't allow the /restorehealth to complete. We've also purged the windows update SxS directory and removed pending reboots from the registry and then tried installing updates 1 by 1 and still received the same result. We have reached a point where this server is missing quite a few critical security updates and we need to get this issue resolved.
We have run SFCFix which claims to have resolved an issue with corruption, however running SFC /scannow once again reveals there is still corruption. After running the DISM /startcomponentcleanup we have also noticed that windows update continues to scan for updates and never finds anything (meaning the scan never stops). Running overnight still found nothing, restarting the update server did not help resolve anything either. We have renamed the old CBS.log to old and it is included for reference if needed, we did however start a new log just to show the most recent information involving SFCFix, sfc, and DISM. Any help in this situation will be amazing and, ahead of time, thank you. This is a very frustrating issue.
I have tried to attach the CBS.zip but it will not let me and I cannot run the script to upload it to the servers as it does not allow me to download it from the link in the sticky. If someone could please provide information on how to upload it, it is just shy of 60 MB in size.
