What's new

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

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
Please re-upload your Component Based Servicing.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
I'm afraid you have provided an incorrect file.

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 etc. and include the link with your reply.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
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.
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

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
Hi,

please do the following:

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.



  • 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.

Afterwards,

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.
  9. Reboot and try installing updates.
 

Attachments

itlange

Active member
Joined
Nov 12, 2017
Posts
30
Hi, i have done this. Here the log:
Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-03-12 08:22:19.162
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\Jan\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{18f4a5fd-fd3b-40a5-8fc2-e5d261c5d02e}.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\1.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\2.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{18f4a5fd-fd3b-40a5-8fc2-e5d261c5d02e}.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Shsvcs\Diagnostic.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-UxTheme\Diagnostic.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{6d8a3a60-40af-445a-98ca-99359e500146}\ChannelReferences\2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{18f4a5fd-fd3b-40a5-8fc2-e5d261c5d02e}.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Shsvcs\Diagnostic.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Shsvcs.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-UxTheme\Diagnostic.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-UxTheme.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.
RegistryScript:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 11 datablocks.
Finish time: 2018-03-12 08:30:10.057
Script hash: NhCAIaJEYoVCbMTSL6m+2zJw9p4zFxEAt8UsqLPOD8U=
----------------------EOF-----------------------
After work or tomorrow after work, we will try to restart the server.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
OK, let me know the results.

I'm sorry this is taking so long.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
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. 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

itlange

Active member
Joined
Nov 12, 2017
Posts
30
Code:
Entfernungsergebnis von Farbar Recovery Scan Tool (x64) Version: 25.04.2018
durchgeführt von Jan (03-05-2018 18:11:38) Run:5
Gestartet von C:\Users\Jan\Desktop
Geladene Profile: Jan & Administrator (Verfügbare Profile: praxisadmin & KL-AK-D8FE17D60BF6BE & Jan & Administrator & MSSQL$MICROSOFT##WID)
Start-Modus: Normal
==============================================

fixlist Inhalt:
*****************
CreateRestorePoint:
DeleteValue:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-iis-adsicompatibility_31bf3856ad364e35_0.0.0.0_none_6793c23ae1e32b2b|Package_581_for_KB3172614~31bf3856ad364e35~amd64~~6.3.1.4.3172614-700_neutral_GDR
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-iis-adsicompatibility_31bf3856ad364e35_0.0.0.0_none_6793c23ae1e32b2b]
"Package_581_for_KB3172614~31bf3856ad364e35~amd64~~6.3.1.4.3172614-700_neutral_GDR"="6.3.9600.18323@4"
EndRegedit:

*****************

Fehler: (0) Erstellen eines Wiederherstellungspunktes gescheitert.
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-iis-adsicompatibility_31bf3856ad364e35_0.0.0.0_none_6793c23ae1e32b2b\\Package_581_for_KB3172614~31bf3856ad364e35~amd64~~6.3.1.4.3172614-700_neutral_GDR" => erfolgreich entfernt

====> Registry

==== Ende von Fixlog 18:11:39 ====
I will now try the next update.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Posts
18,477
Location
Croatia
Try KB3172614 and attach CBS.log if it fails.
 
Top