[SOLVED] Windows Server 2012 R2 Error 0x800F0902 Installing Monthly Rollup KB4103725

devonwoods

Contributor
Joined
Feb 8, 2018
Posts
110
See CBS log attached and SFCFix.exe results below:

Code:
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-05-28 13:16:48.730
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.








AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.3.9600.17415.








SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-05-28 13:28:49.294
----------------------EOF-----------------------
 

Attachments

See attached CBS zip file and the results of the sfc /scannow and the dism RestoreHealth option.

Note: I don't have approval from my company to use your SFCfix.exe at the moment, can we troubleshoot this without the use of 3rd party apps?

Code:
C:\Users\C806577>sfc /scannow

Beginning system scan.  This process will take some time.


Beginning verification phase of system scan.
Verification 40% complete.


Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


C:\Users\C806577>Dism /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


[===========                20.0%                          ]
Error: 1726


The remote procedure call failed.


The DISM log file can be found at C:\windows\Logs\DISM\dism.log
 

Attachments

Hello again ...just checking again to see if you were able to put together a fix? Or do you need an updated CBS.log or folder at this point?
 
FYI, I was doing some further troubleshooting on my own and now I am thinking this may be an issue with IE rather than Windows Update or a component store corruption. Here's this one particular line that I am seeing that stands out in the CBS.log file ...

Code:
2018-06-19 18:12:56, Info                  CBS    Failed to enumerate store versions on component: amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.3.9600.19003_none_6ac4bf812c44076c [HRESULT = 0x8000ffff - E_UNEXPECTED]
2018-06-19 18:12:56, Info                  CBS    Failed to enumerate related component versions on component: amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.3.9600.19003_none_6ac4bf812c44076c [HRESULT = 0x8000ffff - E_UNEXPECTED]
2018-06-19 18:12:56, Info                  CBS    Failed to load current component state [HRESULT = 0x8000ffff - E_UNEXPECTED]

Comparing this to other servers just like this one for the most part, it seems as if the update is having an issue putting down the folder amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.3.9600.19003_none_6ac4bf812c44076c. This folder holds 2 IE related DLLs. I have attached the latest CBS folder content. I took ownership of the WinSxS folder to be able to copy this folder to the WinSxS folder and retried the update but it failed as well.
 

Attachments

Thank you. Please start with the following:

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][/CODE] tags around the log to break up the text.



Export Component Based Servicing



  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\Component Based Servicing\
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  7. Right Click on the ComponentBasedServicing file on your Desktop and choose Send To -> Compressed (Zipped) Folder.


Once done please upload ComponentBasedServicing.zip via DropBox OneDrive or SendSpace
 

Attachments

Here ya go ...I sent you a direct message with the OneDrive link to the ComponentBasedServicing.zip

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-06-20 14:38:24.121
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\bsa\stage\SFCFixScript.txt [0]
 

Trace::
Failed to trace component amd64_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.3.9600.19003_none_6ac4bf812c44076c with return code 1 and conditional return code ERROR_FILE_NOT_FOUND.
Trace:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-06-20 14:38:24.856
Script hash: MwZopOFSlN5nTYK4afGuH50x/qqx/j9FuFvCXE0h0mk=
----------------------EOF-----------------------
 
I need this as well:

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 toa file sharing service and just provide the link here.
 
OK will do but it may be about 3 hours before I can reboot this server in our production environment.
 
I will most likely be away for some time, please send me a PM when you are able, and I will refer you to a colleague who will be taking care of my threads until I return.
 

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

Back
Top