KB4474419 and KB4516065 fail on reboot and then revert

[RDIII]

Inherited an older Windows 2008 R2 server and it's way behind on updates. I'm guessing the previous admin ran into the same problem I'm having but just ignored it instead of trying to figure out. Ran through SFC, SURT, and did the SFCFix. Here is my CBS log and SURT info.

CBS.zip

 

[x BlueRobot]

2022-02-04 00:28:14, Error      [0x018007] CSI    00000038 (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2022-02-04 00:28:15, Info                  CSI    00000039 End executing advanced installer (sequence 66)
    Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

2022-02-04 00:34:03, Info                  CSI    0000003d@2022/2/4:05:34:03.322 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-SMBServer, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;30691960
2022-02-04 00:34:03, Error      [0x018007] CSI    0000003e (F) Failed execution of queue item Installer: Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) with HRESULT HRESULT_FROM_WIN32(14109).  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]
2022-02-04 00:34:04, Info                  CSI    0000003f End executing advanced installer (sequence 67)

Step#1 - FRST Scan
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. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

 

[RDIII]

Thanks for the reply. Here are the files you asked for.

 

[x BlueRobot]

2022-02-03 18:43:49, Info                  CSI    00000129 Begin executing advanced installer phase 38 (0x00000026) index 139 (0x000000000000008b) (sequence 178)
    Old component: [ml:322{161},l:320{160}]"Microsoft-Windows-WorkstationService, Culture=neutral, Version=6.1.7601.24136, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:322{161},l:320{160}]"Microsoft-Windows-WorkstationService, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2022-02-03 18:43:49, Info                  CSI    0000012a Calling generic command executable (sequence 28 (0x0000001c)): [30]"C:\Windows\System32\netcfg.exe"
    CmdLine: [55]""C:\Windows\System32\netcfg.exe" -e -c c -i MS_MSCLIENT"
2022-02-03 18:43:51, Error                 CSI    0000012b (F) Done with generic command 28 (0x0000001c); CreateProcess returned 0, CPAW returned S_OK
    Process exit code 2 resulted in success? FALSE
    Process output: [l:76 [76]"Trying to install MS_MSCLIENT ...




..failed. Error code: 0x80070002.




"][gle=0x80004005]

Thanks for providing those files. I've had another look at your CBS log as well. Could you please provide your COMPONENTS hive using the following instructions:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

You may also want to check the existence of this file as well:

C:\Windows\System32\netcfg.exe

 

[RDIII]

The file you asked for is there. Here is a pic of it. Also here is the link for the Components zip file.

components.zip

 

[x BlueRobot]

Thanks, let's try and get a trace so we can what is happening during the update process. From the error code in the log, there is likely going to be missing registry value or a file.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[RDIII]

It doesn't fail until the reboot process, everything is fine up to that point. I can't monitor that, I just see it going along doing the update on the reboot then suddenly it fails and says it's reverting.

 

[x BlueRobot]

Step#1 - Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install the update just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service of your choice for my review. Examples of services to upload to are Dropbox or OneDrive or SendSpace

 

[RDIII]

Had to download an older version of procmon that was compatible with Server 2008 R2. Here are the files you wanted.

Bootlog.zip

CBS.zip

 

[x BlueRobot]

Thank you, there appears to be a number of Winners key missing, I'll need to source a suitable replacement for them unless the key itself is merely corrupted. Could you please provide the WinSxS hive?

Step#1 - Export SideBySide

1. Click on the Start button and in the search box, type regedit
2. When you see regedit on the list, right-click on it and select Run as administrator
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
   
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (.)
6. Name this file SxS (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or OneDrive or SendSpace.

 

[RDIII]

Sorry I didn't get this to you sooner. Been one of those weeks.

SxS

 

[x BlueRobot]

Thank you, something is odd here...why is it trying to install an old component as the new one? Both versions appear to exist as well. It also seems that KB4474419 and KB4516065 are partially installed already as well.

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:


reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS


4. 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.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4474419 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. 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.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4516065 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

 

[RDIII]

Here you go.

 

[x BlueRobot]

Okay, let's remove the two updates, they appear to be partially installed already which is why Windows Update is failing to install them again.

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.

 

[x BlueRobot]

Same instructions but with a different script.

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.

 

[RDIII]

Ran both the scripts and rebooted after each one. Here are the results. I'll wait until you say something to try and reinstall any updates.

 

[x BlueRobot]

Thanks, could you please try and install one of the problematic updates again? If it fails, then please attach the CBS log.