gringo-82
Goto Top

SFC + DISM versagt bei 2012R2 - 2019

Guten Tag,

ich stelle ganz selten Fragen, nur wenn ich wirklich nicht mehr weiter weis..
Habe mich seit Anfang des Monats ca 30h mit dem Thema beschäftigt und ich bin ratlos.

habt Ihr z.Zt. auch vermehrt Probleme, dass der component store von 2012R2 / 2019 und Windows 10 20H2 plötzlich beschädigt ist?
Tritt bei mir grad eben bei verschiedensten Kunden mit verschiedensten Virenscannern plötzlich auf.
Alle Updates werden mit WSUS zurückgehalten um 2 Wochen (ausser der aktuelle Hafnium natürlich - aber nicht alle betroffenen sind im WSUS).
Das ganze begann vor 2 Monaten ca bei 2 2012R2 Servern.
Dann folgten vor 4 Wochen 2 2019er, dann 1 Windows 10 PC, dann und seit gestern 3 Windows 10 PCs (alles verschiedene Kunden!) dann noch 3 Windows 2016 Server...

Alle Reparaturversuche (Chkdsk, SFC, Dism, Component in reg löschen, Component von gesundem Server kopieren usw) schlugen fehl, half eigenltich immer nur ein In-place-upgrade. Die Fehler äußern sich immer anders:

Fehler bei WU: 80073712
Drucker lassen sich nicht mehr installieren
Startleiste funktionierte nicht mehr (Cortana)

Nervt mich brutal - will eigentlich nur wissen ob ich allein bin 😕
Ereignisprotokolle geben mir auch keine Aufschluss über die Ursache. Ich vermute die Windows Updates, gibt aber aktuell ja keine Beanstandungen (ausser KB5000802 und das ist noch nicht installiert)
Gerne kann ich noch das CBS und DISM Log bereitstellen...

Eben einen Anruf von meinem Geschäftspartner bekommen - selbes Problem bei einem anderen W2012R2.

Danke und viele Grüße zusammen,
Stephan

Content-ID: 665007

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

Ausgedruckt am: 25.11.2024 um 01:11 Uhr

Birkuli
Birkuli 22.03.2021 um 19:56:18 Uhr
Goto Top
beidermachtvongreyscull
beidermachtvongreyscull 22.03.2021 um 20:42:20 Uhr
Goto Top
Zitat von @gringo-82:

Guten Tag,
Moinsen,


ich stelle ganz selten Fragen, nur wenn ich wirklich nicht mehr weiter weis..
Habe mich seit Anfang des Monats ca 30h mit dem Thema beschäftigt und ich bin ratlos.

Das glaube ich gerne. Ist auch ein ###thema.


habt Ihr z.Zt. auch vermehrt Probleme, dass der component store von 2012R2 / 2019 und Windows 10 20H2 plötzlich beschädigt ist?
Tritt bei mir grad eben bei verschiedensten Kunden mit verschiedensten Virenscannern plötzlich auf.
Alle Updates werden mit WSUS zurückgehalten um 2 Wochen (ausser der aktuelle Hafnium natürlich - aber nicht alle betroffenen sind im WSUS).
Das ganze begann vor 2 Monaten ca bei 2 2012R2 Servern.
Dann folgten vor 4 Wochen 2 2019er, dann 1 Windows 10 PC, dann und seit gestern 3 Windows 10 PCs (alles verschiedene Kunden!) dann noch 3 Windows 2016 Server...

Ich hab nur 2016er im Einsatz und kenne das Problem bisher nur bei einem.


Alle Reparaturversuche (Chkdsk, SFC, Dism, Component in reg löschen, Component von gesundem Server kopieren usw) schlugen fehl, half eigenltich immer nur ein In-place-upgrade. Die Fehler äußern sich immer anders:

Fehler bei WU: 80073712
Drucker lassen sich nicht mehr installieren
Startleiste funktionierte nicht mehr (Cortana)

Nervt mich brutal - will eigentlich nur wissen ob ich allein bin 😕

Du bist bestimmt nicht alleine. Ähnliche Fehler treffen viele nur nicht zwingend die gleichen.

Ereignisprotokolle geben mir auch keine Aufschluss über die Ursache. Ich vermute die Windows Updates, gibt aber aktuell ja keine Beanstandungen (ausser KB5000802 und das ist noch nicht installiert)
Gerne kann ich noch das CBS und DISM Log bereitstellen...

Den besten Ansatz findest Du eigentlich im CBS.log. Ist nur verdammt blöde in dem Bereich alles zu durchsuchen.
Den CS bzw. den SXS-Ordner wieder sauber zu bekommen, geht eigentlich nur, wenn Du von einer versions- und build-gleichen Installation gesundes Material überträgst.

Eben einen Anruf von meinem Geschäftspartner bekommen - selbes Problem bei einem anderen W2012R2.

Danke und viele Grüße zusammen,
Stephan

Viele Grüße
bdmvg
gringo-82
gringo-82 22.03.2021 um 21:26:30 Uhr
Goto Top
Danke für Deine Antwort Birkuli!

diese Artikel hatte ich auch schon gefunden und alles systematisch incl der Programme durchprobiert (soweit bis die VM nicht mehr funktionierte...)

Die Fehlermeldungen nach SFC / DISM sind
HRESULT = 0x80004003
HRESULT = 0x80070002
HRESULT=80073712


Anbei doch noch die Logs für Euch ;)

CBS nach SFC /scannow
2021-03-22 21:05:34, Info                  CBS    TI: --- Initializing Trusted Installer ---
2021-03-22 21:05:34, Info                  CBS    TI: Last boot time: 2021-03-20 19:12:31.907
2021-03-22 21:05:34, Info                  CBS    Starting TrustedInstaller initialization.
2021-03-22 21:05:34, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2021-03-22 21:05:34, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:6
2021-03-22 21:05:34, Info                  CBS    Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:7
2021-03-22 21:05:34, Info                  CBS    Ending TrustedInstaller initialization.
2021-03-22 21:05:34, Info                  CBS    Starting the TrustedInstaller main loop.
2021-03-22 21:05:34, Info                  CBS    TrustedInstaller service starts successfully.
2021-03-22 21:05:34, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2021-03-22 21:05:34, Info                  CBS    Startup processing thread terminated normally
2021-03-22 21:05:34, Info                  CBS    TI: Startup Processing completes, release startup processing lock.
2021-03-22 21:05:35, Info                  CBS    Starting TiWorker initialization.
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2021-03-22 21:05:35, Info                  CBS    Ending TiWorker initialization.
2021-03-22 21:05:35, Info                  CBS    Starting the TiWorker main loop.
2021-03-22 21:05:35, Info                  CBS    TiWorker starts successfully.
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CCbsWorker, level: 5, total lock:3
2021-03-22 21:05:35, Info                  CBS    TiWorker: Client requests SFP repair object.
2021-03-22 21:05:35, Info                  CBS    Universal Time is: 2021-03-22 20:05:35.880
2021-03-22 21:05:35, Info                  CBS    Loaded Servicing Stack v10.0.14393.4227 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4227_none_7f12d43621e57eca\cbscore.dll
2021-03-22 21:05:35, Info                  CSI    00000001@2021/3/22:20:05:35.896 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff982726cd9 @0x7ff9859d4fcf @0x7ff9859d3a22 @0x7ff6f6762d9d @0x7ff6f6763927 @0x7ff9b3ff8e23)
2021-03-22 21:05:35, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:14
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:15
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: FlightPackageCacheCriticalSection, level: 128, total lock:16
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CCbsCapabilityManager, level: 11, total lock:17
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CCbsWorkerQueue, level: 60, total lock:18
2021-03-22 21:05:35, Info                  CBS    Lock: New lock added: CCbsWorkerQueue:m_WindowsUpdateExpressDownloadLock, level: 10, total lock:19
2021-03-22 21:05:35, Info                  CBS    NonStart: Set pending store consistency check.
2021-03-22 21:05:35, Info                  CSI    00000002@2021/3/22:20:05:35.896 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff982726cd9 @0x7ff98b784b3f @0x7ff98b784c7e @0x7ff6f676230d @0x7ff6f6763954 @0x7ff9b3ff8e23)
2021-03-22 21:05:35, Error                 CSI    00000003@2021/3/22:20:05:35.927 (F) onecore\base\wcp\componentstore\storelayout.cpp(4273): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307190128.cab to WER report.
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307030756.cab to WER report.
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210306125342.cab to WER report.
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210210113719.cab to WER report.
2021-03-22 21:05:35, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210123160223.cab to WER report.
2021-03-22 21:05:35, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2021-03-22 21:05:35, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:05:35, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:05:35, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:05:36, Info                  CBS    Failed to get CSI system store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:05:36, Info                  CBS    CSI store consistency check fails. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:05:36, Info                  CBS    Failed to load component store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:05:36, Error                 CSI    00000004@2021/3/22:20:05:36.052 (F) onecore\base\wcp\componentstore\storelayout.cpp(4273): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307190128.cab to WER report.
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307030756.cab to WER report.
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210306125342.cab to WER report.
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210210113719.cab to WER report.
2021-03-22 21:05:36, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210123160223.cab to WER report.
2021-03-22 21:05:36, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2021-03-22 21:05:36, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:05:36, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:05:36, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

CBS nach DISM.exe /Online /Cleanup-image /Restorehealth

2021-03-22 21:07:37, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2021-03-22 21:07:37, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2021-03-22 21:07:37, Info                  CBS    Ending the TiWorker main loop.
2021-03-22 21:07:37, Info                  CBS    Starting TiWorker finalization.
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: WcpUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: DrupUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: DpxUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2021-03-22 21:07:37, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2021-03-22 21:07:37, Info                  CBS    Ending TiWorker finalization.
2021-03-22 21:07:37, Info                  CBS    Ending the TrustedInstaller main loop.
2021-03-22 21:07:37, Info                  CBS    Starting TrustedInstaller finalization.
2021-03-22 21:07:37, Info                  CBS    Ending TrustedInstaller finalization.
2021-03-22 21:07:59, Info                  CBS    TI: --- Initializing Trusted Installer ---
2021-03-22 21:07:59, Info                  CBS    TI: Last boot time: 2021-03-20 19:12:31.907
2021-03-22 21:07:59, Info                  CBS    Starting TrustedInstaller initialization.
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:6
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:7
2021-03-22 21:07:59, Info                  CBS    Ending TrustedInstaller initialization.
2021-03-22 21:07:59, Info                  CBS    Starting the TrustedInstaller main loop.
2021-03-22 21:07:59, Info                  CBS    TrustedInstaller service starts successfully.
2021-03-22 21:07:59, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2021-03-22 21:07:59, Info                  CBS    Startup processing thread terminated normally
2021-03-22 21:07:59, Info                  CBS    TI: Startup Processing completes, release startup processing lock.
2021-03-22 21:07:59, Info                  CBS    Starting TiWorker initialization.
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2021-03-22 21:07:59, Info                  CBS    Ending TiWorker initialization.
2021-03-22 21:07:59, Info                  CBS    Starting the TiWorker main loop.
2021-03-22 21:07:59, Info                  CBS    TiWorker starts successfully.
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsWorker, level: 5, total lock:3
2021-03-22 21:07:59, Info                  CBS    Universal Time is: 2021-03-22 20:07:59.415
2021-03-22 21:07:59, Info                  CBS    Loaded Servicing Stack v10.0.14393.4227 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.4227_none_7f12d43621e57eca\cbscore.dll
2021-03-22 21:07:59, Info                  CSI    00000001@2021/3/22:20:07:59.415 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff981046cd9 @0x7ff982854fcf @0x7ff982853a22 @0x7ff6f6762d9d @0x7ff6f67635e0 @0x7ff9b3ff8e23)
2021-03-22 21:07:59, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsSessionManager, level: 11, total lock:14
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:15
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: FlightPackageCacheCriticalSection, level: 128, total lock:16
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsCapabilityManager, level: 11, total lock:17
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsWorkerQueue, level: 60, total lock:18
2021-03-22 21:07:59, Info                  CBS    Lock: New lock added: CCbsWorkerQueue:m_WindowsUpdateExpressDownloadLock, level: 10, total lock:19
2021-03-22 21:07:59, Info                  CBS    NonStart: Set pending store consistency check.
2021-03-22 21:07:59, Info                  CBS    Session: 30875479_240820344 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2021-03-22 21:07:59, Info                  CBS    Client specifies manual store corruption detect or repair.
2021-03-22 21:07:59, Info                  CBS    Exec: Session processing started.  Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30875479_240820344
2021-03-22 21:07:59, Info                  CBS    Reboot mark set
2021-03-22 21:07:59, Info                  CBS    Winlogon: Registering for CreateSession notifications
2021-03-22 21:07:59, Info                  CBS    Winlogon: Loading SysNotify DLL
2021-03-22 21:07:59, Info                  CBS    Winlogon: Starting notify server 
2021-03-22 21:07:59, Info                  CBS    FLOW: Entering stage: CheckCbs 
2021-03-22 21:08:31, Info                  CBS    Repr: CBS Store check completes
2021-03-22 21:08:31, Error                 CSI    00000002@2021/3/22:20:08:31.790 (F) onecore\base\wcp\componentstore\storelayout.cpp(4273): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307190128.cab to WER report.
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210307030756.cab to WER report.
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210306125342.cab to WER report.
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210210113719.cab to WER report.
2021-03-22 21:08:31, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20210123160223.cab to WER report.
2021-03-22 21:08:31, Info                  CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:08:31, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:08:31, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:08:31, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-03-22 21:08:31, Info                  CBS    Failed to get CSI system store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    CSI store consistency check fails. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to load component store [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to get CSI Store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to get CSI session store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Ensure CBS corruption flag is clear
2021-03-22 21:08:31, Info                  CBS    Ensure WCP corruption flag is clear
2021-03-22 21:08:31, Info                  CBS    
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair 
Operation result: 0x80073712
Last Successful Step: CBS store detection completes.
Total Detected Corruption:	0
	CBS Manifest Corruption:	0
	CBS Metadata Corruption:	0
	CSI Manifest Corruption:	0
	CSI Metadata Corruption:	0
	CSI Payload Corruption:	0
Total Repaired Corruption:	0
	CBS Manifest Repaired:	0
	CSI Manifest Repaired:	0
	CSI Payload Repaired:	0
	CSI Store Metadata refreshed:	False

Total Operation Time: 32 seconds.

2021-03-22 21:08:31, Info                  CBS    CheckSur: hrStatus: 0x80073712 [ERROR_SXS_COMPONENT_STORE_CORRUPT], download Result: 0x0 [S_OK]
2021-03-22 21:08:31, Info                  CBS    Count of times corruption detected: 0
2021-03-22 21:08:31, Info                  CBS    Seconds between initial corruption detections: -1
2021-03-22 21:08:31, Info                  CBS    Seconds between corruption and repair: -1
2021-03-22 21:08:31, Info                  CBS    SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2021-03-22 21:08:31, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Reboot mark cleared
2021-03-22 21:08:31, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2021-03-22 21:08:31, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2021-03-22 21:08:31, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30875479_240820344 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Error                 CBS    Session: 30875479_240820344 failed to perform store corruption detect and repair operation. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Session: 30875479_240820344 finalized. Reboot required: no [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2021-03-22 21:08:31, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x80073712]

DISM
2021-03-22 21:11:42, Info                  DISM   PID=3864 TID=6688 Scratch directory set to 'C:\Users\xxxxxxxxx\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir  
2021-03-22 21:11:42, Info                  DISM   PID=3864 TID=6688 DismCore.dll version: 10.0.14393.4169 - CDISMManager::FinalConstruct
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   PID=3864 TID=6688 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession  
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: 
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: 
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.14393, Running architecture=amd64, Number of processors=6
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.14393.4169
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Cleanup-image /Restorehealth
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 physical location path: C:\ - CDISMManager::CreateImageSession
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Event name for current DISM session is Global\{C6E5B078-25AC-4637-A415-F866778FDB39} - CDISMManager::CheckSessionAndLock
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Create session event 0x13c for current DISM session and event name is Global\{C6E5B078-25AC-4637-A415-F866778FDB39}  - CDISMManager::CheckSessionAndLock
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation  
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Successfully loaded the ImageSession at "C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C" - CDISMManager::LoadRemoteImageSession  
2021-03-22 21:11:42, Info                  DISM   DISM Image Session: PID=6112 TID=2196 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:42, Info                  DISM   DISM OS Provider: PID=6112 TID=2196 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM OS Provider: PID=6112 TID=2196 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM OS Provider: PID=6112 TID=2196 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
2021-03-22 21:11:42, Warning               DISM   DISM OS Provider: PID=6112 TID=2196 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Warning               DISM   DISM Provider Store: PID=6112 TID=2196 Failed to Load the provider: C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   Try to initialize Panther logging 1 times, last error: 0x0
2021-03-22 21:11:42, Info                  DISM   DISM Manager: PID=3864 TID=6688 Image session successfully loaded from the temporary location: C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C - CDISMManager::CreateImageSession
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Getting Provider OSServices - CDISMProviderStore::GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.14393.4227, Image architecture=amd64
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:42, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\IBSProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM OS Provider: PID=6112 TID=2196 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2021-03-22 21:11:43, Info                  DISM   DISM Driver Manager: PID=6112 TID=2196 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\EmbeddedProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Warning               DISM   DISM Provider Store: PID=6112 TID=2196 Failed to Load the provider: C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\AppxProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\ProvProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\AssocProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\GenericProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\OfflineSetupProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Loading Provider from location C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Connecting to the provider located at C:\Users\xxxxxxxxx\AppData\Local\Temp\398A6198-86EF-4BE4-88DE-460A7597FA0C\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2021-03-22 21:11:43, Info                  DISM   DISM Transmog Provider: PID=6112 TID=2196 Current image session is [ONLINE] - CTransmogManager::GetMode
2021-03-22 21:11:43, Info                  DISM   DISM Transmog Provider: PID=6112 TID=2196 Audit Mode: [No] - CTransmogManager::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM Transmog Provider: PID=6112 TID=2196 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2021-03-22 21:11:43, Info                  DISM   DISM Transmog Provider: PID=6112 TID=2196 Product Type: [ServerNT] - CTransmogManager::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM Transmog Provider: PID=6112 TID=2196 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IBSManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: ProvManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: ProvManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2021-03-22 21:11:43, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2021-03-22 21:11:43, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2021-03-22 21:12:11, Info                  DISM   DISM Package Manager: PID=6112 TID=7196  Error in operation: (null) (CBS HRESULT=0x80073712) - CCbsConUIHandler::Error
2021-03-22 21:12:11, Error                 DISM   DISM Package Manager: PID=6112 TID=2196 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
2021-03-22 21:12:11, Error                 DISM   DISM Package Manager: PID=6112 TID=2196 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80073712)
2021-03-22 21:12:11, Error                 DISM   DISM Package Manager: PID=6112 TID=2196 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80073712)
2021-03-22 21:12:11, Error                 DISM   DISM Package Manager: PID=6112 TID=2196 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
2021-03-22 21:12:11, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2021-03-22 21:12:11, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Package Manager: PID=6112 TID=2196 Finalizing CBS core. - CDISMPackageManager::Finalize
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=6112 TID=2196 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Manager: PID=3864 TID=6688 Closing session event handle 0x13c - CDISMManager::CloseImageSession
2021-03-22 21:12:11, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2021-03-22 21:12:11, Info                  DISM   DISM.EXE: 
2021-03-22 21:12:11, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2021-03-22 21:12:11, Info                  DISM   DISM.EXE: 
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2021-03-22 21:12:11, Info                  DISM   DISM Provider Store: PID=3864 TID=6688 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
gringo-82
gringo-82 22.03.2021 um 21:34:02 Uhr
Goto Top
Den besten Ansatz findest Du eigentlich im CBS.log. Ist nur verdammt blöde in dem Bereich alles zu durchsuchen.
Den CS bzw. den SXS-Ordner wieder sauber zu bekommen, geht eigentlich nur, wenn Du von einer versions- und build-gleichen Installation gesundes Material überträgst.

Danke für deine Antwort beidermachtvongreyscull,

habe ich probiert:
Components von einem "gesunden" Server auf den defekten kopiert
Sfc bricht nach 60% ab
WinSxS und servicing von einem gesunden Server auf eine freigabe kopiert (mit Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:h:\sources\install.wim:1 /LimitAccess kein Erfolg)
dism /online /cleanup-image /restorehealth /source:"\\xxxxx\comp" /LimitAccess erfolgreich repariert
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
dism.exe /online /Cleanup-Image /StartComponentCleanup
alles ohne Fehler durchgelaufen

SFC / scannow bricht noch immer bei 60% ab....


Ach noch was wichtiges u.U.
Die Components Datei unter %Systemroot%\System32\Config hat immer 8Kb bei den defekten Server - normalerweise ja 60 - 80 Mb groß.


Das glaube ich gerne. Ist auch ein ###thema.
Danke für dein Mitgefühl face-smile


Grüße,

Steph
schicksal
schicksal 23.03.2021 um 09:23:42 Uhr
Goto Top
Zu dem Problem kann ich hier auch nur Theorien liefern.

Könnte es sein weil sich das Problem so nach und nach über alle Rechner verteilt, das da eine "Sicherheitsoftware" mitmischt.
Versuche mal einen Server mit deinstallierten AV (...) zu reparieren, vergleiche hier auch so Tools wie Malwarebyte EMET und ä.
gringo-82
gringo-82 23.03.2021 aktualisiert um 13:52:44 Uhr
Goto Top
Zitat von @schicksal:

Zu dem Problem kann ich hier auch nur Theorien liefern.

Hi Schicksal,

immer her damit mit den Theorien - ich erwarte keine sofortige Lösung :D

Aber das kann man auch ausschließen:
1. Es sind verschiedende AV Lösungen auf den Server (bei verschiedenen Kunden) installiert (Kaspersky 4 Windows Server incl aktuellen CF4, ESET for Fileserver oder auch nur der Windows Defender)
2. habe bereits schon probiert den KS4WS zu deinstallieren und die Reparaturen durchzuführen - ebenfalls ohne Erfolg.

Was meinst Du mit Malwarebyte EMET?
schicksal
schicksal 23.03.2021 um 14:00:32 Uhr
Goto Top
In vielen umgebungen ist zus. zu der AV Lösung noch weitere "Sicherheitssoftware" installiert.
Eben Malwarebytes oder EMET https://de.wikipedia.org/wiki/Enhanced_Mitigation_Experience_Toolkit oder ....

Diese Tools machen oft mehr Probleme als diese Vorteile bringen geschweige denn wenn diese veraltern.
gringo-82
gringo-82 23.03.2021 um 17:13:35 Uhr
Goto Top
Achso mit ODER, danke für die Aufklärung, nein, das ist aber auf keinem Server drauf....

Die beiden 2019er zum Beispiel sind absolut spartanisch - nur Defender, der eine ist der Telefonanlagenserver (Swyx) und am anderen liegt eine Datenbank.
schicksal
schicksal 24.03.2021 um 07:24:54 Uhr
Goto Top
"SFC / scannow bricht noch immer bei 60% ab...."
Lösche mal alle erstellten CBS.log und führe nochmals SFC / Scannow aus. vielleicht geht es so durch.

Oder hierzu habe ich woanders einen Tipp erhalten:
Hallo, probiere mal dieses, mit deiner Win 7 DVD booten>Reparaturmodus dort in die Eingabeaufforderung und folgendes mal starten ! sfc /offbootdir=c:\ /offwindir=c:\windows /scannow
Wenn dein Win einen anderen Laufwerksbuchstaben hat c: ändern !
Ps. oder probiere nur mal sfc /verifyonly
Ps. wenn du auf der Kiste eine System Reserved partition hast kann auch von dort überprüft werden !
sfc /scannow /offbootdir=e:\ /offwindir=c:\windows
e: ist die System Reserved partition und c: dein Win
gringo-82
gringo-82 24.03.2021 aktualisiert um 08:44:56 Uhr
Goto Top
Morgen!

Lösche mal alle erstellten CBS.log und führe nochmals SFC / Scannow aus. vielleicht geht es so durch.
werde ich heute abend probieren

Win 7 DVD booten>Reparaturmodus
bereits probiert, bricht dort sofort ab (dauert ca 1 Minute "die Prüfung wird gestartet", dann kommt nicht mal 0%)

wenn du auf der Kiste eine System Reserved partition hast
Schau ich später nach ob ich die Partition dort hab und teste dann

Ps. oder probiere nur mal sfc /verifyonly
bereits probiert, läuft durch, Meldung war dann soweit ich mich erinnere, Fehler gefunden, Fehler können behoben werden mit /scannow. Direkter start danach von sfc /scannwo scheitert aber dann wieder.


Danke!

Grüße,
Steph
gringo-82
gringo-82 07.04.2021 um 17:10:22 Uhr
Goto Top
Leider blieb alles ohne Erfolg nach wie vor....
Legoland1
Legoland1 05.01.2022 um 20:36:16 Uhr
Goto Top
Hallo Gringo-82,

ich bin auch gerade auf der verzweifelten Suche nach einer Lösung zu exakt dem gleichen Problem.
Hast du an dieser Stelle noch etwas erreichen und das Problem lösen können??

Freue mich über kurze Rückmeldung.

Gruß
Tom
gringo-82
gringo-82 08.01.2022 um 22:40:22 Uhr
Goto Top
Servus Tom,

leider nein.
Die einzige "Lösung" blieb immer ein InPlace Upgrade auf der gleichen Version durchzuführen.
Ich konnte nur aus Zufall das Problem simulieren: Bei WSUS im Alternativen Pfad im GPO ebenfalls den gleichen WSUS Server zu hinterlegen.


Viel Erfolg, bitte lass es mich wissen, falls Du dennoch auf eine Lösung kommst - rein aus Neugierde.


Viele Grüße,
Steph
Legoland1
Legoland1 09.01.2022 um 11:47:55 Uhr
Goto Top
Moin Steph,

das ist wie verhext!
Mein Server ist ein 2019 Essentials als Single Domain Controller in einer 6 Mann Klitsche.
Ein Inplace-Update scheidet somit aus (keine Ahnung ob das überhaupt an einem DC gehen würde, noch nie mit befasst).

Das Simulieren verstehe ich nicht ganz...
Du konntest durch Eintragen des gleichen WSUS als alternativen WSUS Server das Problem auf einer gänzlich anderen Maschine nachstellen??

Mein Kundenserver beginnt mittlerweile mit solchen Scherzen wie:
Rechte MT auf die Eigenschaften eines Ordners (um Freigabe und Berechtigen zu setzen) -> geht nicht mehr, keine Reaktion!

Ich werde jetzt die kommende Woche einen Call bei Microsoft eröffnen, mal schauen was da raus kommt.
Ansonsten komme ich um eine Virtualisierung und Migration auf eine neue Maschine nicht drum rum.
Ich melde mich...!

VG
Tom
gringo-82
gringo-82 10.01.2022 um 17:22:01 Uhr
Goto Top
Servus Tom,

oh ein DC auf Blech - bei mir warens alles VMs und kein DC betroffen.
Ein Kollege von mir hat das Problem auch auf einem Hypervisor... schrecklich.
Ja, ich hatte ein anderes Problem mit den Updates und habe wohl aus versehen in meiner Testumgebung dort den alternativen eingetragen (also 3 mal das gleiche). Zack, nach den nächsten Updates ging der Component Store defekt (bei Windows 10 Enterprise).

Stimmt, das mit dem Kontextmenü kommt mir auch noch bekannt vor :/

Hast Du von Deinem defekten Server evtl noch ein Backup wo alles i.O. war?
Da könntest versuchen die COMPONENTS Datei auszuwechseln und "so lange SFC probieren bis es klappt" - man hört sich das laienhaft an...

Fall Du ein Ticket erstellst wär ich Dir mega verbunden hier nochmal kurz bescheid zu geben was rausgekommen ist.
War damals sehr frustiert über die Probleme - hab bis jetzt immer die Quelle jedes Fehlers gefunden, aber dieses mal nicht..

Viel Erfolg und viele Grüße,

Steph
screenshot 2022-01-10 172335
gringo-82
gringo-82 06.02.2022 um 19:35:25 Uhr
Goto Top
Servus Tom,

gab es Hilfe von MS bei Dir?


Grüße,

Steph
Legoland1
Legoland1 07.02.2022 um 10:56:46 Uhr
Goto Top
Moin Steph,

die sind tatsächlich noch zu Gange.
Die Dame vom Support experimentiert noch mit dem DISM Befehl und dem WinSXS Ordner/Wim-File aus diversen Quellen.
Das geht allerdings jedes mal schief...!
Ein Vorschlag von ihr wäre auch ein Inplace Upgrade (da bekomm ich aber Krämpfe bei dem Gedanken).
Lieber migriere ich auf einen Std-Server und virtualisiere das Ganze.
Also bis dato noch keine Lösung.

Ich halte Dich auf dem Laufenden sobald es was Neues gibt!

Cheers Tom
beidermachtvongreyscull
beidermachtvongreyscull 07.02.2022 um 13:12:54 Uhr
Goto Top
Zitat von @Legoland1:

Moin Steph,

die sind tatsächlich noch zu Gange.
Die Dame vom Support experimentiert noch mit dem DISM Befehl und dem WinSXS Ordner/Wim-File aus diversen Quellen.
Das geht allerdings jedes mal schief...!
Ein Vorschlag von ihr wäre auch ein Inplace Upgrade (da bekomm ich aber Krämpfe bei dem Gedanken).
Lieber migriere ich auf einen Std-Server und virtualisiere das Ganze.
Also bis dato noch keine Lösung.

Ich halte Dich auf dem Laufenden sobald es was Neues gibt!

Cheers Tom

Ich bezweifle, dass Du Dir mit dem Support einen Gefallen getan hast., Alleine schon, dass selbst die "expermientieren müssen" und es nicht hinbekommen.

Zudem dürfte es beim MS-Support noch immer so sein:
Wenn sie Dein Problem fixen, aber dadurch ein anderes entsteht, dann musst Du den neuen Call aufmachen.
gringo-82
gringo-82 07.02.2022 um 13:58:18 Uhr
Goto Top
Zitat von @Legoland1:

Moin Steph,

die sind tatsächlich noch zu Gange.
Die Dame vom Support experimentiert noch mit dem DISM Befehl und dem WinSXS Ordner/Wim-File aus diversen Quellen....

Servus Tom,

danke für Deine Antwort! Also die beim Support kochen also auch nur mit Wasser. Diese o.g. Schritte hab ich auch probiert und naja, dass ist mehr als zeitaufwändig und dann funktionierts doch nicht. Mal noch abwarten.

Hab nur wieder nachgefragt, da ich bei einem neuen Kunden schon wieder das Problem mit übernommen habe.
Bei diesem schlägt aber sogar das InPlace Upgrade von 2019 auf 2019 fehl...
Mich verfolgt das ganze schrecklich - dieser Kunde ist / war ohne WSUS (noch) unterwegs.

Oh mei...

Viel Erfolg weiterhin!

Grüße,
Steph
Legoland1
Legoland1 09.04.2022 um 16:38:35 Uhr
Goto Top
Servus zusammen,

Wollte kurz Meldung machen, dass das Server Problem nun endlich gelöst ist. face-smile
Letztendlich war der einzige von MS empfohlen Lösungsweg ein Inplace Update mit der gleichen Version (Srv Essentials 2019), sprich eine Reparatur Installation.
Wegen massiven Bauchschmerzen meinerseits hatte ich mich lange dagegen gesträubt.
Aber nachdem ich dann auf ner Temp. Maschine nen weiteren Virt. DC erstellt, mich schon auf ne Migration vorbereitet hab und allen Mut zusammen genommen habe, hab ich es gestern Nachmittag durchgezogen. Aktuelle iso aus dem VLSC geladen und installiert.
Tatsächlich war es noch sehr spannend, weil er dann doch über 2 Std. lang bei 91% stehen blieb und ich mit allem gerechnet habe.
Zum guten Ende hat er es dann doch geschafft.
Sogar sämtliche Anwendungen mit Datenbanken, bis auf meinen GData Management Server, den hat es erwischt, waren funktionsfähig.

Updates laufen wieder sauber und sämtliche kleinere Macken, die dem Problem geschuldet waren, sind weg!!

Danke Microsoft, hattest doch Recht.

Viel Erfolg und viele Grüße
Tom
gringo-82
gringo-82 10.05.2022 um 11:58:58 Uhr
Goto Top
Servus Tom,

danke fürs Feedback. Naja MS würde ich jetzt nicht so hochloben, da ein InPlace Upgrade die Dampfhammer Methode ist. Schade, mich hätte die Ursache viel mehr interessiert....

Viele Grüße,

Steph