[SOLVED] Microsoft Windows Server 2016 Standard dism failure

[Bert Merayo]

Attached is zipped cbs.log and dism.log files. Please help! Thank you,

 

[Windows Update Bot]

Hi @Bert Merayo,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[PeterJ]

Hello,

FRST Scan:

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
2. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
4. Press the Scan button.
5. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
6. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[Bert Merayo]

See attached files. Thx,

 

[PeterJ]

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. 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.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Open this web page to download the latest Java version. Click 1 of the 3 download links.
Start the downloaded installer and run it.
Warning: You may get a choice to install additional software and/or allow to change your browser settings. Uncheck all that!
If you get a pop-up saying "Out-of-date Java versions detected.", click Uninstall>. This will remove the outdated Java versions.

Step 3:
Did you install the program Npcap OEM intentionally ?

 

[Bert Merayo]

See attached. Yes, Npcap OEM was intentional. Thx,

 

[Bert Merayo]

Latest CBS.log file with CSI corrupt payload info. Thx,

 

[Bert Merayo]

I'm missing the 4 in bold that i cannot find... thx


(p) CSI Payload Corrupt msil_microsoft-windows-n..ontroller-framework_31bf3856ad364e35_10.0.14393.4046_none_9b7ca454713a9f4b\edb00000001.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_tsportalwebpart_31bf3856ad364e35_10.0.14393.4169_none_aa5808974a2aac6c\allusers_tswa.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-c..termanagementsnapin_31bf3856ad364e35_10.0.14393.4169_none_c0d8369cd0e67b48\Computer Management.lnk
(p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9\MSDTC.LOG
(p) CSI Payload Corrupt amd64_tsportalwebpart_31bf3856ad364e35_10.0.14393.0_none_620a5da1064dcfc0\allusers_tswa.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-failovercluster-snapin_31bf3856ad364e35_10.0.14393.0_none_aab1e8cd313249d9\Failover Cluster Manager.lnk
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-d..c-usersandcomputers_31bf3856ad364e35_10.0.14393.0_none_685eeff41f6af95f\Active Directory Users and Computers.lnk
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
(p) CSI Payload Corrupt (Fixed) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml

Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 16
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 16
Total Repaired Corruption: 12
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 12
CSI Store Metadata refreshed: True

 

[PeterJ]

The following fix will repair the last one of the remaining 4 items.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Provide the 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. Note: If you find that you need to reboot and are unable to because this is a server then try Option#2 below.
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 Gofile or WeTransfer and just provide the link here.

---

Option#2 (only if you are unable to follow the previous instructions)

• 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.
• Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
• Click the New Backup button. Accept the defaults and simply click Start.
• When it says Finished successfully, click the Close button.
• 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...
• 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.
• Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
• Now right-click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
• 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 Gofile or WeTransfer and then just provide the link in your reply.
• You can close any open windows you have as well as the RegBak program now.

 

[Bert Merayo]

(p) CSI Payload Corrupt msil_microsoft-windows-n..ontroller-framework_31bf3856ad364e35_10.0.14393.4046_none_9b7ca454713a9f4b\edb00000001.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_tsportalwebpart_31bf3856ad364e35_10.0.14393.4169_none_aa5808974a2aac6c\allusers_tswa.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_tsportalwebpart_31bf3856ad364e35_10.0.14393.0_none_620a5da1064dcfc0\allusers_tswa.log
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt (Fixed) amd64_microsoft-windows-failovercluster-snapin_31bf3856ad364e35_10.0.14393.0_none_aab1e8cd313249d9\Failover Cluster Manager.lnk

Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 4
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 4
Total Repaired Corruption: 1
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 1
CSI Store Metadata refreshed: True

 

[PeterJ]

Did you perform Step 1 in my previous post ?
Please perform Step 2.

 

[Bert Merayo]

Did you perform Step 1 in my previous post ? Yes
Please perform Step 2. See attached components.zip file --> Gofile - Cloud Storage Made Simple

 

[PeterJ]

Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Bert Merayo]

log uploaded after "sfc /scannow" failed:

 

[PeterJ]

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Bert Merayo]

sfc /scannow failed, see attached CBS log file.Thank you,

 

[PeterJ]

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Bert Merayo]

All better now. thank you so very much!

 

[PeterJ]

Your welcome.