[SOLVED] Windows Server 2019 DISM Fails

stevenTPG

Member
Joined
Feb 13, 2024
Posts
21
Hello again!

When running DISM it fails with this error: 0xd0000034
sfc /scannow comes back clean

Attached is the components scanner txt and CBS zip.

All the best,
Steven
 

Attachments

Looking over your logs, back as soon as I've finished analysing them.
 
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.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also 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.
1p8eDnI.gif

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

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Hey Gary,

Thanks for your help!

SFCFix.exe ran successfully, but dism still failed. Attached are the SFCFix.txt and CBS.log files.

All the best,
Steven
 

Attachments

  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
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.
1p8eDnI.gif

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

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Hey Gary,

Thanks for all your help. DISM ran successfully now.

Attached are the SFCFix.txt and CBS.log files.

All the best,
Steven
 

Attachments

Nothing being flagged in your latest CBS.log so please try updating your computer.

If successful please let me know.

If not, please post the CBS.log created after your update attempt.
 
Hey Gary,

I was able to update the system. After running sfc /scannow, it found corrupt files but was unable to repair them.

Please find the CBS.log attached.

All the best,
Steven
 

Attachments

If you were able to successfully update, why did you run SFC, it's a fairly limited tool, and not the best indicator of faults on your system.

Latest CBS.log is free from errors as far as I can see, so unless your computer has any actual problems, I'd say you're good to go.

If you do have any actual problems, please let me know what they are, and we'll see what we can do to resolve them.
 
You're welcome.

I'll mark this topic as solved then.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top