[SOLVED] Error Code 0x80073712

[bluezeus]

Results:

STEP1:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-04 11:32:27.104
Microsoft Windows Server 2012 - amd64
Using .zip script file at D:\Profilo\Administrator\Desktop\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.22802_none_5ba1a50ae5ca97eb\gdiplus.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.9200.22802_none_6c5036264cc4be44\gdiplus.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_6.2.9200.22802_none_4082338898b06f67\gdiplus.dll
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.22802_none_5ba1a50ae5ca97eb\gdiplus.dll to C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.22802_none_5ba1a50ae5ca97eb\gdiplus.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.9200.22802_none_6c5036264cc4be44\gdiplus.dll to C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.9200.22802_none_6c5036264cc4be44\gdiplus.dll.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_6.2.9200.22802_none_4082338898b06f67\gdiplus.dll to C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_6.2.9200.22802_none_4082338898b06f67\gdiplus.dll.
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.22802_none_5ba1a50ae5ca97eb\gdiplus.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.22802_none_5ba1a50ae5ca97eb\gdiplus.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.9200.22802_none_6c5036264cc4be44\gdiplus.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.9200.22802_none_6c5036264cc4be44\gdiplus.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_6.2.9200.22802_none_4082338898b06f67\gdiplus.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus.systemcopy_31bf3856ad364e35_6.2.9200.22802_none_4082338898b06f67\gdiplus.dll
PowerCopy:: directive completed successfully.


FileScan::
[0: 1] C:\Windows\WinSxS\x86_microsoft-windows-store-runtime_31bf3856ad364e35_6.2.9200.16811_none_edd84a4c108df7ee\WSShared.dll
Expected: rlQshEmdw4Qy1oO4CguLaWXU01GfL/p9mVVOyOc+wYM=
Expected: 6.2.9200.16811
Successfully traced component x86_microsoft-windows-store-runtime_31bf3856ad364e35_6.2.9200.16811_none_edd84a4c108df7ee.
Package_121_for_KB2928678~31bf3856ad364e35~amd64~~6.2.1.1.2928678-278_neutral_LDR3
FileScan:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 22 datablocks.
Finish time: 2019-08-04 11:32:47.366
Script hash: nAWFn5V3dLL6gvpO08XRjGN5Ex5Wk1SLmr4s1a9pgyM=
----------------------EOF-----------------------

STEP2:
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 14005
The manifest file contains one or more syntax errors.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

CBS.zip

 

[writhziden]

Let's see if ProcMon can help us track down a few more issues:

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as the it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[bluezeus]

This is log Logfile.zip

 

[writhziden]

I would like to offer my apologies that there is a delay in the next repair to your system. There were some unexpected complexities found in your logs, and we will need some additional time to develop a plan of action. Thank you for your patience.

 

[writhziden]

Step 1
Memory Concerns

Have you recently replaced the memory (RAM) in your system? There were bit shifts detected in a couple registry keys, which can be indicative of faulty RAM. If you have not recently replaced your RAM, I highly advise that you proceed with memory diagnostics before proceeding to Steps 2-3. If you do not already have memory diagnostic tools for testing your server hardware, we recommend using Test RAM with PassMark MemTest86

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.
   Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt 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 to install updates again, and if any fail, attach the CBS.log.

Step 3
DISM /RestoreHealth Scan

1. Right-click on the Start button and select Command Prompt (Admin)
2. 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
3. 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"
4. 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 Dropbox or OneDrive or SendSpace and just provide the link.

 

[bluezeus]

Thank you for supporting writhziden, don't worry if you need more time.
The important thing is that we can get to the end of this problem.

Results:

STEP1
(I not have recently replaced RAM)
The Windows Memory Diagnostic tested the computer's memory and detected no errors

STEP2
See log attached

STEP3
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 14005
The manifest file contains one or more syntax errors.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

CBS.zip

 

[writhziden]

Please do the following:

1. Point to: Bottom right corner
2. Click on: Search (The magnifying glass icon)
3. Under: Search (Apps)
4. Type: Regedit
5. Select and open Registry Editor
6. Collapse any open hives (directory icons)
7. Take a screenshot with Print Screen and crop it with Paint or use the snipping tool to capture an image of your Registry Editor
   It should look similar to below:
   
8. Upload the image in your next post

 

[bluezeus]

 

[writhziden]

Your main registry hives look good. Thanks for verifying. Can you please provide the most recent version of your COMPONENTS hive?

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 to SendSpace and just provide the link here.

If you are unable to follow those instructions due to the hive being in use by the server, follow the below procedure instead:

Read More:

1. Please download the Freeware RegBak from here: Acelogix Software - Download products
   You will find it at the bottom of the page that the link brings you to.
2. Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
3. Click the New Backup button. Accept the defaults and simply click Start.
4. When it says Finished successfully, click the Close button.
5. This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
6. This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
7. Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
8. Now right click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
9. Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
10. You can close any open windows you have as well as the RegBak program now.

 

[bluezeus]

Ok, this is Components.zip

 

[writhziden]

It looks like you have an extra, bad key floating around that I missed removing earlier. Follow the below steps to remove it and allow us to verify it was removed.

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 the attached fixlist.txt 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 to install updates again, and if any fail, attach the CBS.log.

Step 2
DISM /RestoreHealth Scan

1. Right-click on the Start button and select Command Prompt (Admin)
2. 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
3. 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"
4. 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 Dropbox or OneDrive or SendSpace and just provide the link.

 

[bluezeus]

Step 1
Fix result of Farbar Recovery Scan Tool (x64) Version: 10-08-2019
Ran by Administrator (14-08-2019 09:50:50) Run:6
Running from D:\Profilo\Administrator\Desktop
Loaded Profiles: UpdatusUser & Administrator & MSSQL$MICROSOFT##WID & SQLTELEMETRY & SQLSERVERAGENT & MSSQLSERVER (Available Profiles: UpdatusUser & Administrator & MSSQL$MICROSOFT##WID & SQLTELEMETRY & SQLSERVERAGENT & MSSQLSERVER & .NET v4.5 & .NET v4.5 Classic)
Boot Mode: Normal
==============================================
fixlist content:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
CloseProcesses:
CreateRestorePoint:
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea0defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932
ExportKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea0defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932
ExportKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea1defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932
*****************

========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========
The operation completed successfully.

========= End of CMD: =========
Processes closed successfully.
Error: (0) Failed to create a restore point.
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea0defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932 => removed successfully
================== ExportKey: ===================
"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea0defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932" => not found
=== End of ExportKey ===
================== ExportKey: ===================
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5d18801b471eebde819ea1defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_none_23e4bcb26106e932]
"S256H"="e1f43994360521bdf67754d61526a76b46ef9a30b948d9664383b16ad3084f10"
"identity"="35643138383031623437316565626465383139656131646566633365316533622c2043756c747572653d6e65757472616c2c2056657273696f6e3d362e322e393230302e32303532312c205075626c69634b6579546f6b656e3d33316266333835366164 (the data entry has 112 more characters)."
"CF"="12"
"c!5d18801b471..1defc3e1e3b_31bf3856ad364e35_6.2.9200.20521_23e4bcb26106e932"=""
=== End of ExportKey ===

The system needed a reboot.
==== End of Fixlog 09:51:17 ====





Step 2

CBS.zip

 

[writhziden]

Let's see if ProcMon can help us track down your DISM issues:

Capture Process Monitor Trace

1. Once again, we will need you to run Process Monitor.
2. This time, try to start Process Monitor as close as you can to when the failure occurs when running DISM /Online /Cleanup-Image /RestoreHealth (within 1-5 minutes of failure).
   
   Read More:

   
   DISM /RestoreHealth Scan
   

   1. Right-click on the Start button and select Command Prompt (Admin)
   2. 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

   [*][*][*]
3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
   
   
   
   
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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[bluezeus]

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.
Error: 0x800f081f
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

This is log Logfile.zip

 

[writhziden]

Thank you. Can we also please see your CBS folder?

1. Press the Windows key, type This PC, and press Enter.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Right-click on the CBS folder, and select Copy.
5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
8. Provide a link to the CBS.zip archive you upload. Examples of services to upload to are Dropbox or OneDrive or SendSpace
   
   

 

[bluezeus]

Ok, CBS.zip

 

[writhziden]

I'm afraid that set of logs came too long after DISM ran. We will need to get the logs immediately after the DISM repair attempt. Please follow the steps to do so below:

Step 1
DISM /RestoreHealth Scan

1. Right-click on the Start button and select Command Prompt (Admin)
2. 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
3. Report back to us with the full error message (take a screenshot if you can).

Step 2
Provide the Full CBS Directory

1. Press the Windows key, type This PC, and press Enter.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Right-click on the CBS folder, and select Copy.
5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
8. Provide a link to the CBS.zip archive you upload. Examples of services to upload to are Dropbox or OneDrive or SendSpace

 

[bluezeus]

excuse me for the delay in the response, these are the results:

Step 1



Step 2
CBS.zip

 

[Sysnative Windows Update]

Hello!

As writhziden is currently busy, I am going to shortly step in and provide the next steps for you to follow:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past, but this time, I want you to select only a single update.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

If you receive something else instead of an error code, please stop and let me know.

Your next reply should contain:

1. A description of what happened
2. KB number of the update you have attempted to install
3. A link to the Process Monitor Logfile and the CBS.log.

Thank you for your patience whilst we are troubleshooting this.

 

[bluezeus]

Hello

KB4486081



CBS & Log