[SOLVED] Server 2012 R2U3 - amd64- DISM and Windows Update Fails

C

cmplx

Member
Joined
May 14, 2018
Posts
18
Having some issues with Server 2012 R2 updating.

2018-05-14 10:09:44, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-Networking-RemoteAccess-PowerShell-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, Remote Parent: ServerManager-Core-RSAT-Role-Tools, Intended State: Installed2018-05-14 10:09:44, Info CBS Appl: Package: Microsoft-Windows-Networking-RemoteAccess-PowerShell-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, Update: RemoteAccessMgmtTools, Applicable: Applicable, Disposition: Installed
2018-05-14 10:09:44, Info CBS Appl: DetectUpdate, Package: Microsoft-Windows-ServerManager-Core-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, Local Parent: ServerManager-Core-RSAT, Intended State: Installed
2018-05-14 10:09:44, Info CBS Appl: Package: Microsoft-Windows-ServerManager-Core-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, Update: ServerManager-Core-RSAT-Feature-Tools, Applicable: Applicable, Disposition: Installed
2018-05-14 10:10:15, Info CSI 0000000d Warning: Component (WindowsSearchEngine, Version = 7.0.9600.18759, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral) is not present. Closure expected to be complete: (TRUE)
2018-05-14 10:11:22, Info CSI 0000000e Warning: Component (System.Linq.Expressions, Version = 4.0.9600.21785, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral) is not present. Closure expected to be complete: (TRUE)
2018-05-14 10:11:30, Info CSI 0000000f Warning: Component (Microsoft-Windows-Verifier, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral) is not present. Closure expected to be complete: (TRUE)
2018-05-14 10:11:33, Error CSI 00000010@2018/5/14:14:11:33.324 (F) base\wcp\identity\id_authority_helpers.cpp(791): Error STATUS_SXS_IDENTITY_PARSE_ERROR originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::ParseAttributeList expression: CurrentLexeme.m_LexemeType == IdentityParser::CLexeme::Equals
[gle=0x80004005]
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180514114226.log to WER report.
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180514001020.log to WER report.
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180513001750.log to WER report.
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180512001515.log to WER report.
2018-05-14 10:11:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180511121619.log to WER report.
2018-05-14 10:11:33, Info CBS Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-05-14 10:11:33, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-05-14 10:11:33, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-05-14 10:11:33, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-05-14 10:11:34, Error CSI 00000011 (F) STATUS_SXS_IDENTITY_PARSE_ERROR #786605# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:302{151}]"Microsoft-Windows-VAN.Resources, Culture=en-US, Version=6.3.9600.17197, PublicKeyToken=31bf3856ad364e35,6.3.9600.17197, PublicKeyToken=31bf3856ad364e35")
[gle=0xd0150019]
2018-05-14 10:11:34, Error CSI 00000012 (F) STATUS_SXS_IDENTITY_PARSE_ERROR #245# from CCSDirect_IRtlComponentStore::EnumStoreCorruptions(...)[gle=0xd0150019]
2018-05-14 10:11:34, Error CSI 00000013 (F) HRESULT_FROM_WIN32(14093) #244# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 5, cancelEvt = 260 (""), disp = 0)[gle=0x8007370d]
2018-05-14 10:11:34, Error CBS Rept: Failed to call CSI detect. [HRESULT = 0x8007370d - ERROR_SXS_IDENTITY_PARSE_ERROR]
2018-05-14 10:11:34, Info CBS Failed to check CSI store. [HRESULT = 0x8007370d - ERROR_SXS_IDENTITY_PARSE_ERROR]
2018-05-14 10:11:34, Info CBS Ensure CBS corruption flag is clear
2018-05-14 10:11:34, Info CBS Ensure WCP corruption flag is clear
2018-05-14 10:11:34, Info CBS
=================================
Checking System Update Readiness.
Click to expand...

Attached is the CBS log

View attachment CBS.zip
 
Hello and welcome! 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.
 

Attachments

Here is the log and an updated CBS.Log

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-05-14 11:05:41.068
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\administrator.XXXX\Desktop\SFCFixScript.txt [0]











RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-05-14 11:05:41.787
Script hash: RVzyU6AkN/VGtBAMT4GHlmJzcIQU/e4k9eLJcNcKqy0=
----------------------EOF-----------------------
 

Attachments

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.
 

Attachments

View attachment CBS-1121.zip
Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2018-05-14 11:17:11.563
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\administrator.PTIFL\Desktop\SFCFixScript.txt [1]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-05-14 11:17:12.782
Script hash: RVzyU6AkN/VGtBAMT4GHlmJzcIQU/e4k9eLJcNcKqy0=
----------------------EOF-----------------------
 
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.
 
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.
  8. Upload it for me and provide the link.
 
No problem. It appears that you have not done the export correctly. You have exported it in reg format instead of exporting it as a hive. Could you please repeat?
 
No worries!

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. You can use the one you already have downloaded.
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.
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.
6. Try updates and attach CBS.log if any fail.
 

Attachments

View attachment CBS-1234.zip

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 12.05.2018
Ran by Administrator (14-05-2018 12:29:42) Run:1
Running from C:\Users\administrator.XXXX\Desktop
Loaded Profiles: Administrator MSSQL$MICROSOFT##WID & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.3.9600.17484_none_0a635fbf0a5ec59f]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.3.9600.17484_none_0a635fbf0a5ec59f]
"S256H"=hex:50,19,13,7d,21,ea,94,79,d0,e1,4a,01,90,ff,cb,1e,ec,4e,be,4c,d5,2e,\
  4a,58,0b,59,d6,d4,c8,fc,cc,ff
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,54,65,78,\
  74,53,65,72,76,69,63,65,73,46,72,61,6d,65,77,6f,72,6b,2d,6d,73,63,74,66,2c,\
  20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,61,6c,2c,20,56,65,72,73,69,6f,6e,\
  3d,36,2e,33,2e,39,36,30,30,2e,31,37,34,38,34,2c,20,50,75,62,6c,69,63,4b,65,\
  79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,\
  50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,78,38,36,\
  2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"c!8c1e1c1acc2..3fdaa841e37_31bf3856ad364e35_6.3.9600.17484_769d8e35e978f167"=hex:
"f!msctf.dll"=dword:00000003
"DV"=hex:84,49,80,25,03,00,06,00
"CTS"=dword:47f87fa9
"CF"=dword:00000010
EndRegedit:
*****************


Error: (0) Failed to create a restore point.


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


The operation completed successfully.




========= End of CMD: =========


"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.3.9600.17484_none_0a635fbf0a5ec59f" => removed successfully


====> Registry


==== End of Fixlog 12:29:44 ====
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install the update just like you have in the past.
3. Stop Process Monitor as soon as the update 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.



Has RAM been replaced/upgraded/tested recently?
 
I suspect we will have some more fixing to do after this as this seems to be a fairly complex issue.

Has KB4054518 ever been installed or is it currently installed on the system?

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.
  7. Provide a copy in your next reply.


Step #2 - 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. You can use the one you already have downloaded.
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.
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.
6. Try updates and attach CBS.log if any fail.
 

Attachments

View attachment 35511
View attachment CBS-559.zip

I do not see KB4054518 installed on the server. Was able to install .NET updates but not the security rollups


Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 12.05.2018Ran by Administrator (14-05-2018 15:17:10) Run:2
Running from C:\Users\administrator.XXXX\Desktop
Loaded Profiles: Administrator  MSSQL$MICROSOFT##WID & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f301f0b9f6e..ba74cddb9a4_31bf3856ad364e35_6.3.9600.17415_34cb30592c4c1a7d]
"appid"=hex:66,33,30,31,66,30,62,39,66,36,65,36,63,65,37,66,37,62,66,32,61,62,\
  61,37,34,63,64,64,62,39,61,34,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,\
  61,6c,2c,20,56,65,72,73,69,6f,6e,3d,36,2e,33,2e,39,36,30,30,2e,31,37,34,31,\
  35,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,\
  36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,\
  74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,\
  70,65,3d,4e,6f,6e,53,78,53


[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-htmlhelp-infotech_31bf3856ad364e35_6.3.9600.17415_none_e7aee7fae777b01b]
"DV"=hex:aa,49,80,25,03,00,06,00
"CTS"=dword:47a92239
"CF"=dword:00000010
EndRegedit:
*****************


Error: (0) Failed to create a restore point.


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


The operation completed successfully.




========= End of CMD: =========




====> Registry


==== End of Fixlog 15:17:12 ====
 
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