Server 2012r2 Updates failing to install

Thank you.

This fix will reboot the Server:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Sorry about the wait, I had to wait until after business hours to reboot. Here is the log.
 

Attachments

Reverted on the update install. I checked "Control Panel\All Control Panel Items\Windows Update\View update history" right after the reboot and the update is showing 'Pending Restart' even before trying to install it agian.
 

Attachments

That did it for the Important update! I gave one of the optional ones a try and it did the reverting changes after reboot.
 

Attachments

I generally do not recommend installing optional updates as they are (mostly) beta products and can cause issues. If you would still like to proceed, I can tell you that Hyper-V components are the issue and that it would need to be disabled before the update would succeed.
 
We don't need to dig into the optional updates at all. Do you know if the fix for the important update 'should' allow future important updates to install? We have a few other Windows Server 2012r2 VMs running on that same Hyper-V host that have no issues updating. Is there anything I can compare between the working VMs and this one?

Thank you again for all of the help.
 
Very difficult to tell. Everything should work, but depending on the components that have been updated now, there may still be some corrupt or missing entries, which is impossible to detect now. If you get an error in the next feature update just come back and I'll assist.

As for the VMs, I don't know without the logs, but the errors are 100% related to Hyper-V
 
Sounds good. It's doing the reverting changes after each reboot after attempting to install the optional update(s). Is that something we can fix and I will leave the other optional updates alone?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top