[SOLVED] Error: 0xd0000034 Windows 2019

strokov

Contributor
Joined
May 3, 2023
Posts
68
Hi,
I ran the command and got an error.

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5576

[==========================100.0%==========================]
Error: 0xd0000034

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

It's missing a file, in a previous threat this file was also missing, tried to apply the fix again..Unfortunately it didn't fix the problem.

Code:
ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.5576)
Start time: 2024-03-20T08:04:58
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 218497
Number of values: 646645

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====

== Missing Files ==
C:\Windows\winsxs\Catalogs\c5a8498f43390d1f4216508aac814999ad13c1ea03957cb0e626de9c012511df.cat (CanonicalData\Catalogs\c5a8498f43390d1f4216508aac814999ad13c1ea03957cb0e626de9c012511df exists but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\c7474178bf4de1421802f4cf000eca93710e96618cbdb263af8c67d867c06ad3.cat (CanonicalData\Catalogs\c7474178bf4de1421802f4cf000eca93710e96618cbdb263af8c67d867c06ad3 exists but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\c7504cda5e74cb7056abc71c2131e522431e5e97c97d743ca677da391a48ac53.cat (CanonicalData\Catalogs\c7504cda5e74cb7056abc71c2131e522431e5e97c97d743ca677da391a48ac53 exists but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\ebe5e50af69fcd75cebd364a05b7d31a32407fddd90ad0ed84d6cde05d00f5d0.cat (CanonicalData\Catalogs\ebe5e50af69fcd75cebd364a05b7d31a32407fddd90ad0ed84d6cde05d00f5d0 exists but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\ebe95f82ae8cbd95bc6398bcdf40b8816359b37a520dc297ec8c55c2f74e4987.cat (CanonicalData\Catalogs\ebe95f82ae8cbd95bc6398bcdf40b8816359b37a520dc297ec8c55c2f74e4987 exists but no corresponding file found in WinSxS)

== Corrupt Files ==
C:\Windows\winsxs\Catalogs\78fa7f89c8796596704bd7894d2d5061213ddfee5d790cad077a00e8bcfc3b30.cat (Expected SHA256: 78fa7f89c8796596704bd7894d2d5061213ddfee5d790cad077a00e8bcfc3b30. Actual SHA256: c586f0887c6c70c2cc9df0571dd27159262cf7c4b555028ec4c9e17f2a994da0



Storing 2,21KB in C:\Users\adm\AppData\Local\Sysnative\ComponentsScanner
Archived report directory contains 1 files

Finish Time: 2024-03-20T08:16:01. Corruption scan time: 607,2539514s
===========================EOF===========================

Compoments.zip:
wetransfer: COMPONENTS.zip



Previous:
[SOLVED] - Windows 2019 Error Installation KB5026362
 

Attachments

Hi,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Sorry for the delay (had een dagje vrij)

I'll check it tomorrow

Thanks!
 
I ran the fix:

Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-03-25 08:08:18.403
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\ddrff\Desktop\SFCFix.zip [0]



PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum

Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat to C:\Windows\Servicing\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat.
Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum to C:\Windows\Servicing\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum.
Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat to C:\Windows\Servicing\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat.
Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum to C:\Windows\Servicing\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum.
Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat to C:\Windows\Servicing\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.cat.
Successfully copied file C:\Users\adm\AppData\Local\niemiro\Archive\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum to C:\Windows\Servicing\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages
Successfully restored permissions on C:\Windows\Servicing\Packages
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_3576_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_3577_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored ownership for C:\Windows\Servicing\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\Package_3648_for_KB5034127~31bf3856ad364e35~amd64~~10.0.1.4.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 320 datablocks.
Finish time: 2024-03-25 08:08:25.976
Script hash: GXj/Ku+qiZyvisn7gzNYB0XDbmmfVAbyE67XeXzwlWk=
----------------------EOF-----------------------
Code:
C:\Windows\system32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5576

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5576

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5576

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


I think it is working,

Thanks, Dankjewel!

(y)
 
Hi,

Graag gedaan. Are there any remaining issues, or is everything up and running / up-to-date?
 
Hi,

You're welcome. Glad to hear there are no remaining issues.. (y)
 

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

Back
Top