19.11.2018

6964

Windows Server 2012 R2 Komponentenspeicher wurde beschädigt. Inplace Upgrade?

Hallo liebes Forum,

Wir besitzen einen Domänencontroller der auf einem Windows Server 2012 R2 läuft.
Dadurch, dass alle Windows Updates fehlschlagen und wir mit Perfomance Problemen zu kämpfen haben, wurde der Befehl DISM.exe /Cleanup-Image /RestoreHealth /Online ausprobiert.

Leider kommt es immer zu dem Fehler: 14098 "Der Komponentenspeicher wurde beschädigt".

Habt ihr eine Idee was man ausprobieren könnte?

Ist es möglich eine Inplace Upgrade Reparaturinstallation durchzuführen ohne Probleme bzgl. DC zu bekommen ?

Gruss

DeRo93

Bitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben

Content-ID: 393205

Url: https://administrator.de/contentid/393205

Ausgedruckt am: 22.11.2024 um 14:11 Uhr

11 Kommentare

Neuester Kommentar

Moin,

ist das euer einziger DC?
Hast Du ein funktionierenes Backup?
Was steht in den CBS Logs?

Du könntest versuchen den Komponentenspeicher neu zu erstellen/aufzubauen:
net stop bits
net stop wuauserv
rd /q /s c:\windows\softwaredistribution\
net start wuauserv
wuauclt /resetauthorization /detectnow

Ob das auf einem DC sinnvoll ist, musst Du selbst entscheiden.

Gruss

Hallo,

das wäre nochmal eine Variante: dism /Online /Cleanup-Image /AnalyzeComponentStore

Hängt der Server an einem WSUS?

wenn ja, könntest Du vor den Reparaturvorgängen mit dism sicherstellen, dass der Server nur auf microsoft-update zugreift:
Computerkonfiguration/Administrative Vorlagen/System/

Einstellungen für die Installation optionaler Komponenten und die Reparatur von Komponenten angeben Deaktiviert
Windows-Installationsdateipfad angeben Deaktiviert

Computerkonfiguration/Administrative Vorlagen/Windows-Komponenten/Windows Update

Internen Pfad für den Microsoft Updatedienst angeben Deaktiviert

Ob das auf einem DC sinnvoll ist, musst Du selbst entscheiden.

Grüße

lcer

Zitat von @sabines:

Moin,

ist das euer einziger DC?
Hast Du ein funktionierenes Backup?
Was steht in den CBS Logs?

Du könntest versuchen den Komponentenspeicher neu zu erstellen/aufzubauen:
net stop bits
net stop wuauserv
rd /q /s c:\windows\softwaredistribution\
net start wuauserv
wuauclt /resetauthorization /detectnow

Ja das ist unser einziger DC.
Backups sind vorhanden von VEEAM leider schon MIT dem Fehler.
Welchen Teil der CBS.log braucht ihr ? Soll ich die ganze Datei mal hochladen?
Nach den Befehlen kriege ich leider trotzdem die gleiche Meldung mit dem Komponentenspeicher.

Hallo,

das wäre nochmal eine Variante: dism /Online /Cleanup-Image /AnalyzeComponentStore

Hängt der Server an einem WSUS?

wenn ja, könntest Du vor den Reparaturvorgängen mit dism sicherstellen, dass der Server nur auf microsoft-update zugreift:
Computerkonfiguration/Administrative Vorlagen/System/
Einstellungen für die Installation optionaler Komponenten und die Reparatur von Komponenten angeben Deaktiviert
Windows-Installationsdateipfad angeben Deaktiviert

Computerkonfiguration/Administrative Vorlagen/Windows-Komponenten/Windows Update
Internen Pfad für den Microsoft Updatedienst angeben Deaktiviert

Diese Einstellungen finde ich in den Gruppenrichtlinien nicht.

Bisher habe ich eine Reparaturinstallation mit einem Inplace Upgrade nur auf Windows 7-10 Rechnern gemacht. Wie verhält sich das ganze auf einem Domänencontroller? Muss hier etwas besonderes beachtet werden?

Gruss
DeRo93

Moin,

willst Du das Risiko eingehen und Dir Deinen einzigen DC völlig zerhauen?
Installiere einen neuen DC übertrage die Rollen etc und dann kümmere Dich um den "alten".

Gruss

Zitat von @sabines:

Moin,

willst Du das Risiko eingehen und Dir Deinen einzigen DC völlig zerhauen?
Installiere einen neuen DC übertrage die Rollen etc und dann kümmere Dich um den "alten".

Gruss

Natürlich denke ich auch, dass das die Beste Option wäre.

Aber wäre es nicht theoretisch möglich ein Inplace Upgrade zu versuchen und wenn etwas schief gehen sollte, den Server anhand meiner VEEAM Sicherung wiederherzustellen ?

Gruss DeRo93

Moin,
versuche doch erst nochmal den Komponentenstore mit der Server CD zu fixen.

Dism /online /cleanup-image /restoreHealth /source:WIM:G:\Sources\install.wim:2 /LimitAccess

Wobei Du nochmals kontrollieren solltest welche Image in der Install.wim an erster Stelle liegt, ich glaube aber der Core Server, somit wäre die 2 hinter WIM richtig.
und davor am besten noch

Sfc /scannow

Zitat von @Tektronix:

Moin,
versuche doch erst nochmal den Komponentenstore mit der Server CD zu fixen.

Dism /online /cleanup-image /restoreHealth /source:WIM:G:\Sources\install.wim:2 /LimitAccess

Wobei Du nochmals kontrollieren solltest welche Image in der Install.wim an erster Stelle liegt, ich glaube aber der Core Server, somit wäre die 2 hinter WIM richtig.
und davor am besten noch

Sfc /scannow

Moin,

auch das habe ich probiert und bekomme den selben Fehler: 14098 "Der Komponentenspeicher wurde beschädigt."
SFC /Scannow gibt mir den Fehler "Der Windows-Ressourcenschutz konnte den angeforderten Vorgang nicht ausführen."

Hier nochmal die DISM.Log von der DISM Session:

  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-11-20 09:14:39, Info                  DISM   DISM.EXE: 
2018-11-20 09:14:39, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=amd64, Number of processors=2
2018-11-20 09:14:39, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.17031
2018-11-20 09:14:39, Info                  DISM   DISM.EXE: Executing command line: dism  /online /cleanup-image /restorehealth /source:WIM:D:\sources\install.wim:2 /LimitAccess
2018-11-20 09:14:39, Info                  DISM   DISM Provider Store: PID=4648 TID=5540 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-11-20 09:14:39, Info                  DISM   DISM Provider Store: PID=4648 TID=5540 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:39, Info                  DISM   DISM Provider Store: PID=4648 TID=5540 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:39, Info                  DISM   DISM Provider Store: PID=4648 TID=5540 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:39, Info                  DISM   DISM Manager: PID=4648 TID=5540 physical location path: C:\ - CDISMManager::CreateImageSession
2018-11-20 09:14:39, Info                  DISM   DISM Manager: PID=4648 TID=5540 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation  
2018-11-20 09:14:41, Info                  DISM   DISM Manager: PID=4648 TID=5540 Successfully loaded the ImageSession at "C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74" - CDISMManager::LoadRemoteImageSession  
2018-11-20 09:14:41, Info                  DISM   DISM Image Session: PID=4668 TID=2564 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM OS Provider: PID=4668 TID=2564 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM OS Provider: PID=4668 TID=2564 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM OS Provider: PID=4668 TID=2564 Host OS verion is 6.3 - CDISMOSServiceManager::SetDllSearchPath
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Warning               DISM   DISM Provider Store: PID=4668 TID=2564 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Manager: PID=4648 TID=5540 Image session successfully loaded from the temporary location: C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74 - CDISMManager::CreateImageSession
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Target image information: OS Version=6.3.9600.18384, Image architecture=amd64
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\IBSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Warning               DISM   DISM Provider Store: PID=4668 TID=2564 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\IBSProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM OS Provider: PID=4668 TID=2564 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-11-20 09:14:41, Info                  DISM   DISM Driver Manager: PID=4668 TID=2564 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\Wow64provider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Warning               DISM   DISM Provider Store: PID=4668 TID=2564 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
2018-11-20 09:14:41, Warning               DISM   DISM Provider Store: PID=4668 TID=2564 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\EmbeddedProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Warning               DISM   DISM Provider Store: PID=4668 TID=2564 Failed to Load the provider: C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\AppxProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\AssocProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\GenericProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Loading Provider from location C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Connecting to the provider located at C:\Users\ADMINI~1\AppData\Local\Temp\7F8ED8D7-2ED3-40BB-81CB-C92B2FF57C74\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Audit Mode: [No] - CTransmogManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 GetProductType: ProductType = [LanmanNT] - CTransmogManager::GetProductType
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Product Type: [LanmanNT] - CTransmogManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Determined WinDir path = [C:\Windows] - CTransmogManager::GetWinDirPath
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Treating Domain Controller as Server. - CTransmogManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM Transmog Provider: PID=4668 TID=2564 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-11-20 09:14:41, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Provider Store: PID=4668 TID=2564 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-11-20 09:14:41, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-11-20 09:16:01, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 CBS session options=0x28100! - CDISMPackageManager::Internal_Finalize
2018-11-20 09:20:39, Error                 DISM   DISM Package Manager: PID=4668 TID=2564 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
2018-11-20 09:20:39, Info                  DISM   DISM Package Manager: PID=4668 TID=5204  Error in operation: (null) (CBS HRESULT=0x80073712) - CCbsConUIHandler::Error
2018-11-20 09:20:39, Error                 DISM   DISM Package Manager: PID=4668 TID=2564 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80073712)
2018-11-20 09:20:39, Error                 DISM   DISM Package Manager: PID=4668 TID=2564 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80073712)
2018-11-20 09:20:39, Error                 DISM   DISM Package Manager: PID=4668 TID=2564 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
2018-11-20 09:20:39, Info                  DISM   DISM Package Manager: PID=4668 TID=2564 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-11-20 09:20:39, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Package Manager: PID=4668 TID=5204 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:39, Info                  DISM   DISM Provider Store: PID=4668 TID=5204 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-11-20 09:20:40, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.

Evtl. noch jemand eine Meinung zum Inplace Upgrade?

Zitat von @DeRo93:

Natürlich denke ich auch, dass das die Beste Option wäre.

Definitiv solltest du dies tun.

Aber wäre es nicht theoretisch möglich ein Inplace Upgrade zu versuchen und wenn etwas schief gehen sollte, den Server anhand meiner VEEAM Sicherung wiederherzustellen ?

Mit der Veam Sicherung kommst du natürlich immer wieder zurück aber ein Inplace Upgrade eines DCs ist absolut nicht empfehlenswert gerade bei einem Single DC, damit wirst du später noch andere Probleme bekommen. Also mach es besser gleich nach best Practice.

Also neuen DC in die Domain hängen, synchronisieren lassen und die FSMOs und die anderen Sachen die noch darauf fleuchen. übertragen, alten DC demoten und abschalten.
Und für die Zukunft immer mind. 2 DCs vorhalten.

Gruß A.

Moin,
probier mal noch

Dism /Online /Cleanup-Image /StartComponentCleanup

und danach nochmals

Dism /online /cleanup-image /restoreHealth /source:WIM:G:\Sources\install.wim:2 /LimitAccess

Hallo,

nochmal deutlicher:

Die Reparaturvorgänge mit DISM schlagen unter Umständen fehl, wenn das Reparatur-Image (parameter /source) einen anderen Versionsstand hat als das des zu reparierenden Systems. Das ist beispielsweise der Fall, wenn "ein paar Updates Zuviel" installiert wurden. Deswegen sollte man die Reparaturimages nach Möglichkeit auf dem aktuellen Versionsstand halten.

Ist das nicht der Fall, kann man das Image manuell auf den aktuellen Updatestand bringen (siehe hier das ist extrem zeitraubend) oder man sorgt dafür, dass Microsoft-Update verwendet wird - Dann können fehlende oder fehlerhafte Dateien von dort nachgeladen werden.
Falls Du die nicht findest - hier nochmal die Einstellungen:

Grüße

lcer

PS:

Dism /Online /Get-CurrentEdition
Dism /Image:C:\test\offline /Get-CurrentEdition

Frage Microsoft Windows Server

Mehr von DeRo93

Einziger Domänencontroller ersetzen - Windows Server 2012R2 - HostnameDeRo93 - 31 Kommentare

Office365 OWA - Kontakteintrag stimmt nicht mit Outlook übereinDeRo93

Windows Server 2016 - Freigegebene Drucker - Druckerwarteschlange muss immer neugestartet werdenDeRo93 - 10 Kommentare

ESXI 6.0 - QNAP Datastore für Snapshots hinzufügenDeRo93 - 9 Kommentare

Heiß diskutiert

Sophos SFOS 20 DNAT funktioniert nichtsuperfun2k24 - 26 Kommentare

Kaufberatung Hardware - Hyper-V Cluster 3 Nodesuser217 - 25 Kommentare

Intel-E810 QSFP28 to Mikrotik QSPF+ mit 40Gbit VerbindungPharaun - 24 Kommentare

Testumgebung bauen (Grundlegend)prplemk2 - 19 Kommentare

HP Z620 USB hat kein Strom beim Startenaufdemmars - 17 Kommentare

Dom.Admin-Passwort ändern - Auswirkungen auf EX, HCW, AADCTJ.Hooker74 - 15 Kommentare

Zertifikate in die Exchange Online GAL hochladenJudgelg - 13 Kommentare

Switch ohne STP ins Netzwerkmaisenkaiser - 13 Kommentare

Creo 4.0 Lizenz Server (LMTOOLS)UnluckyProccess1999 - 13 Kommentare

Entwicklertagebuch: Release 6.4 - Filteradmtech - 13 Kommentare

FB7590 ISDN Fax-Funktionleberkaese - 12 Kommentare

Bildqualität der Windows Remotedesktop-Sitzung verbessernDarkened1645 - 11 Kommentare