[SOLVED] Error 0x80073701 w/Windows Update & New Roles/Features Add (Win Server 2016)

I'm not far behind you on bed. No special software or hardware modifications, just a straight vanilla rebuild.
 
Good news! I was able to source the missing key

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put
    Code:
    tags around the log to break up the text.
 

Attachments

Outstanding! Here's the output:

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-09-27 07:13:34.686
Microsoft Windows Server 10 Build 14393 (Updates Deferred) - amd64
Using .txt script file at C:\Users\sansnil\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_updateservices-deployment-languagepack_31bf3856ad364e35_10.0.14393.0_tr-tr_09713de2258287d0.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_updateservices-deployment-languagepack_31bf3856ad364e35_10.0.14393.0_tr-tr_09713de2258287d0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2018-09-27 07:13:35.318
Script hash: HDxx+Sf2fwa4GDVNnGVU1JWyXf2mdLakwtQtAvpuMW4=
----------------------EOF-----------------------
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.




  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-09-27 11:09:07.848
Microsoft Windows Server 10 Build 14393 (Updates Deferred) - amd64
Using .txt script file at C:\Users\sansnil\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5e845539f7ee5a63e50738dd71d16b1b_31bf3856ad364e35_10.0.14393.1914_none_28dee46428ae0957.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5e845539f7ee5a63e50738dd71d16b1b_31bf3856ad364e35_10.0.14393.1914_none_28dee46428ae0957.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2018-09-27 11:09:08.410
Script hash: bSWuUrHqVhoqWSg+KvvBh8gxVgZrZrtHt4lBOqQBXRE=
----------------------EOF-----------------------
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log
 
FRST Registry Search
 1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. 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.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4345418 into the Search box and click the Search Registry button.
8. 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.
9. You may close any remaining open windows now.
 
At Step 4 on Windows Server it brings up the Server Manager to add/remove roles and features. Is this okay to proceed to #5?
 
The fix is huge. It may take a lot of time to complete. That is normal. I would recommend creating a manual system restore point prior to running it just in case.

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 attached file and save it to the Desktop.
3. Extract it.
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).
4. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
5. 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.
6. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
7. Try updates and if any fail, attach CBS.log.
 

Attachments

The fix was still running when I went to sleep last night but I was excited because when I ran the update it made it all the way through and prompted to reboot...unfortunately, after rebooting it came back with a fail message. Still that's definitely progress.

CBS log below.

CBS.zip - Google Drive
 

Attachments

Can I see the fixlog.txt that was created?

Also, can you clarify if the update reverted (Failed at configuring) on reboot or there was an error message after the install itself.

Thank you!
 
Sorry I forgot to attach the fixlog.txt file but edited my post before I saw your reply so it should be there now.

It actually looked like it was going to work. It gave me the usual Windows updating messages whilre rebooting and I didn't see any error message until I checked Windows Update where it just said in the history it failed to install.
 
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