[Server2012R2UPD3 x64] WU fails, DISM RestoreHealth failed with error 14093.

itlange · Nov 12, 2017

Hi,

I have a Windows 2012 R2 Server. This Server had have a corrupted memory. We have fixed this and replace the memory chip.

But now Windows Update is not working and DISM, too.

C:\Windows\System32>dism /online /cleanup-image /restorehealth /source:d:\sources /limitaccess

Tool zur Imageverwaltung für die Bereitstellung
Version: 6.3.9600.17031

Abbildversion: 6.3.9600.17031

[==========================100.0%==========================]

Fehler: 14093

Die Identitätszeichenfolge ist ungültig. Die Ursache kann ein vorangestelltes Ko
mma, die Angabe von mehr als zwei unbenannten Attributen, ein fehlender Attribut
name oder ein fehlender Attributwert sein.

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

C:\Windows\System32>

SFC /scannow shows no errors.
SFCFix says all OK.

Sysnative Windows Update · Nov 24, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hello, I'm sorry about the delay! Do you still need assistance?

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.

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

itlange · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

softwaremaniac said:
Hello, I'm sorry about the delay! Do you still need assistance?

Yes, we need your help. Thank you for your reply. This is the log output from the sfcfix tool, after dragging the zip onto it.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-11-25 17:32:30.648
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\pdhui.dll
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.exe
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.msc
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\resmon.exe
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\sysmon.ocx
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wdc.dll
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wvc.dll

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\pdhui.dll to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\pdhui.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.exe to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.msc to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.msc.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\resmon.exe to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\resmon.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\sysmon.ocx to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\sysmon.ocx.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wdc.dll to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wdc.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wvc.dll to C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wvc.dll.

Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\pdhui.dll
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\pdhui.dll
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.exe
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.exe
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.msc
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\perfmon.msc
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\resmon.exe
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\resmon.exe
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\sysmon.ocx
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\sysmon.ocx
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wdc.dll
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wdc.dll
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wvc.dll
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.17415_none_97696364a9122507\wvc.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2017-11-25 17:32:32.210
Script hash: pZ34pk7S1odh5ngJNniEXxXS3ygdeZTA8/bOC+T7Y9A=
----------------------EOF-----------------------

Sysnative Windows Update · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Thank you.

Step#1 - DISM /RestoreHealth Scan
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.

Right-click on the Start button and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as One Drive or SendSpace and just provide the link.

itlange · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Same Error 14093
Indentity Error

See CBS.log
View attachment CBS.zip

Sysnative Windows Update · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Thank you. We fixed a part of the corruption actually!

First make a backup before we make any changes:

RegBak

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.

RegBak.zip

Right-click on regbak.zip then select Extract all... and extract the files to your Desktop

For 32-bit (x86) editions of Windows, double-click on regbak.exe
For 64-bit (x64) editions of Windows, double-click on regbak64.exe

If you are unsure whether you have x86 or x64 Windows, see here
Without changing any options, click Next. RegBak will now backup all of your registry hives.

Let me know when complete.

itlange · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Done

Sysnative Windows Update · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Export Component Based Servicing

Click on the Start button and in the search box, type regedit
When you see regedit on the list, right-click on it and select Run as administrator
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\
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (*.*)
Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
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 etc. and include the link with your reply.

itlange · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hi. Here is the export:

Download ComponentBasedServicing.zip from Sendspace.com - send big files the easy way

thank you for your help.

Sysnative Windows Update · Nov 25, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Has RAM been tested on this machine?
I mean after the replacement to verify.

itlange · Nov 26, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hi,

yes we have made a quick test and it was ok.

You must know, the defective RAM was over 1 year in this server. 4 memory chips and 1 was defective. It couses 1-2 BSODs per month. But no one has noticed, because of the auto-restart.

Sysnative Windows Update · Nov 26, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

Afterwards, run DISM and attach the resulting CBS.log

itlange · Nov 28, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hi,

we have made a deep memtest86 scan of the new RAM. No failure found. All memory ok.

Here is the SFCFix output log:

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-11-28 09:58:39.084
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\Administrator\Downloads\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\PackageDetect\Microsoft-Windows-IdentityServer-Proxy-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923.
Successfully took ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f.

WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\PackageDetect\Microsoft-Windows-IdentityServer-Proxy-Package~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\PackageDetect\Microsoft-Windows-IdentityServer-Proxy-Package~31bf3856ad364e35~amd64~~0.0.0.0.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923.

Successfully imported registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923.
WARNING: Failed to create backup for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f.

Successfully imported registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f.

Successfully restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\PackageDetect\Microsoft-Windows-IdentityServer-Proxy-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923.
Successfully restored ownership and permissions for registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 11 datablocks.
Finish time: 2017-11-28 09:58:39.320
Script hash: JKZeiUE61iGDbZcq0f028cH1xVI1v0p831s+t/FOzFE=
----------------------EOF-----------------------

itlange · Nov 28, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hi,

dism failed with same error.

Sysnative Windows Update · Nov 29, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

Afterwards, run DISM and attach the resulting CBS.log

itlange · Dec 4, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Hi,

2 error messages less.
2 errors left.

Sysnative Windows Update · Dec 4, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

Afterwards, try DISM and attach the resulting CBS.log

itlange · Dec 5, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Here is the cbs.log and scfix.txt

Seems to me thats the same error as before?

Sysnative Windows Update · Dec 5, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

itlange · Dec 15, 2017

Re: [Server2012R2] WU fails, DISM RestoreHealth failed with error 14093.

Sorry for the Delay. Here the Log output.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-12-15 16:49:25.444
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




RegistryExport::
Failed  to export registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923.

Failed  to export registry key  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component  Based  Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f.
RegistryExport:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 11 datablocks.
Finish time: 2017-12-15 16:49:25.612
Script hash: xWeaqfamvwB4CS1Pt82w9BdWkLOfGEfYybGZjbWq6B4=
----------------------EOF-----------------------

[Server2012R2UPD3 x64] WU fails, DISM RestoreHealth failed with error 14093.

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Attachments

Member

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Attachments

Member