Page 2 of 2 First 12
  1. #21
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,195
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    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.
    Attached Files Attached Files
    If I haven't replied to your thread within 48 hours, please send me a Personal Message.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

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

    Hi, here is the output:

    Code:
    Entfernungsergebnis von Farbar Recovery Scan Tool (x64) Version: 16-12-2017
    durchgeführt von Administrator (16-12-2017 12:15:44) Run:1
    Gestartet von C:\Users\Administrator\Desktop
    Geladene Profile: Administrator (Verfügbare Profile: praxisadmin & KL-AK-D8FE17D60BF6BE & Administrator & MSSQL$MICROSOFT##WID)
    Start-Modus: Normal
    ==============================================
    
    fixlist Inhalt:
    *****************
    cmd: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923"
    cmd: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f"
    *****************
    
    
    ========= reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923" =========
    
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-customizer_31bf3856ad364e35_0.0.0.0_none_e2e1b08357882923
        Package_1535_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-4339_neutral_GDR    REG_SZ    6.3.9600.17415@4
        Package_513_for_KB3205401~31bf3856ad364e35~amd64~~6.3.1.4.3205401-744_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_761_for_KB4012219~31bf3856ad364e35~amd64~~6.3.1.4.4012219-1089_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_763_for_KB4015550~31bf3856ad364e35~amd64~~6.3.1.4.4015550-1101_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_816_for_KB4019215~31bf3856ad364e35~amd64~~6.3.1.3.4019215-1159_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_816_for_KB4019217~31bf3856ad364e35~amd64~~6.3.1.4.4019217-1162_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_817_for_KB4022726~31bf3856ad364e35~amd64~~6.3.1.4.4022726-1168_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_831_for_KB4025336~31bf3856ad364e35~amd64~~6.3.1.4.4025336-1212_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_836_for_KB4034681~31bf3856ad364e35~amd64~~6.3.1.3.4034681-1235_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_841_for_KB4034663~31bf3856ad364e35~amd64~~6.3.1.4.4034663-1243_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_970_for_KB4038792~31bf3856ad364e35~amd64~~6.3.1.3.4038792-1393_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_972_for_KB4041693~31bf3856ad364e35~amd64~~6.3.1.2.4041693-1402_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_974_for_KB4048958~31bf3856ad364e35~amd64~~6.3.1.2.4048958-1413_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_562_for_KB4012216~31bf3856ad364e35~amd64~~6.3.1.2    REG_SZ    6.3.9600.18515@4
        Package_562_for_KB4012216~31bf3856ad364e35~amd64~~6.3.1.2.4012216-798_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_1004_for_KB4054519~31bf3856ad364e35~amd64~~6.3.1.4.4054519-1448_neutral_GDR    REG_SZ    6.3.9600.18515@4
    
    
    ========= Ende von CMD: =========
    
    
    ========= reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f" =========
    
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-d..japanese-prediction_31bf3856ad364e35_0.0.0.0_none_ff5b0a3a46c0829f
        Package_2793_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14.2919355-5989_neutral_GDR    REG_SZ    6.3.9600.17031@4
        Package_1535_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-4335_neutral_GDR    REG_SZ    6.3.9600.17415@4
        Package_513_for_KB3205401~31bf3856ad364e35~amd64~~6.3.1.4.3205401-741_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_761_for_KB4012219~31bf3856ad364e35~amd64~~6.3.1.4.4012219-1086_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_763_for_KB4015550~31bf3856ad364e35~amd64~~6.3.1.4.4015550-1098_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_816_for_KB4019215~31bf3856ad364e35~amd64~~6.3.1.3.4019215-1156_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_816_for_KB4019217~31bf3856ad364e35~amd64~~6.3.1.4.4019217-1159_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_817_for_KB4022726~31bf3856ad364e35~amd64~~6.3.1.4.4022726-1165_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_831_for_KB4025336~31bf3856ad364e35~amd64~~6.3.1.4.4025336-1209_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_836_for_KB4034681~31bf3856ad364e35~amd64~~6.3.1.3.4034681-1232_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_841_for_KB4034663~31bf3856ad364e35~amd64~~6.3.1.4.4034663-1240_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_970_for_KB4038792~31bf3856ad364e35~amd64~~6.3.1.3.4038792-1390_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_972_for_KB4041693~31bf3856ad364e35~amd64~~6.3.1.2.4041693-1399_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_974_for_KB4048958~31bf3856ad364e35~amd64~~6.3.1.2.4048958-1410_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_562_for_KB4012216~31bf3856ad364e35~amd64~~6.3.1.2    REG_SZ    6.3.9600.18515@4
        Package_562_for_KB4012216~31bf3856ad364e35~amd64~~6.3.1.2.4012216-795_neutral_GDR    REG_SZ    6.3.9600.18515@4
        Package_1004_for_KB4054519~31bf3856ad364e35~amd64~~6.3.1.4.4054519-1445_neutral_GDR    REG_SZ    6.3.9600.18515@4
    
    
    ========= Ende von CMD: =========
    
    
    ==== Ende von Fixlog 12:15:44 ====

  3. #23
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,195
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

    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.


    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.
    Attached Files Attached Files
    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  4. #24

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

    Hi,

    the error is gone. Super!

    But Dism is not clean yet. See logs.
    Attached Files Attached Files

  5. #25
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,195
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    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.
    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

Page 2 of 2 First 12

Similar Threads

  1. [SOLVED] [Win10ProV1703Build15063 x64] DISM /RestoreHealth gives error 0x800f081f
    By deleted102517 in forum Windows Update
    Replies: 31
    Last Post: 05-07-2017, 12:26 PM
  2. Windows Update, DISM failing with 14093
    By Scorpwanna in forum Windows Update
    Replies: 2
    Last Post: 05-18-2016, 09:54 PM
  3. Replies: 7
    Last Post: 05-11-2015, 12:13 AM
  4. Replies: 4
    Last Post: 04-14-2015, 09:12 PM
  5. Replies: 7
    Last Post: 07-17-2014, 02:42 AM

Log in

Log in