Windows 10 DISM not working correclty

[sebasmac]

Hi Medetweakers,

Ik heb er inmiddels bijna hoofdpijn van gekregen, windows DISM. Als ik de command promt als admin opstart en voer dan het DISM commando uit krijg ik de volgende foutmelding:

"The Logger could not initialize"

Als ik vervolgens het commando sfc /scannow uitvoer en hem gelijk afbreek en dan nogmaals DISM uitover werkt het wel perfect, ook op een schone installatie heb ik dit issue. Zie het screenshot



Ik vermoed dat die een stukje temp files weggooit als je sfc /scannow gebruikt, weet iemand wat die precies inhoud? Op internet is hier ook niks over te vinden helaas.

Thanks!

[wagenveld]

Staat er iets in de logfile? > %windir%\Logs\DISM
Heb je SFC al eens helemaal laten draaien?

[sebasmac]

wagenveld schreef op dinsdag 17 mei 2016 @ 14:33:
Staat er iets in de logfile? > %windir%\Logs\DISM
Heb je SFC al eens helemaal laten draaien?

2016-05-17 14:08:56, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2016-05-17 14:08:56, Info DISM DISM.EXE:
2016-05-17 14:08:56, Info DISM DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=4
2016-05-17 14:08:56, Info DISM DISM.EXE: Dism.exe version: 10.0.10586.0
2016-05-17 14:08:56, Info DISM DISM.EXE: Executing command line: dism
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Loading Provider from location C:\Windows\System32\Dism\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-05-17 14:08:56, Info DISM DISM Provider Store: PID=15808 TID=15632 Connecting to the provider located at C:\Windows\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-05-17 14:08:56, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
2016-05-17 14:08:56, Info DISM DISM.EXE: Getting the help information collection for the provider: WimManager.
2016-05-17 14:08:56, Info DISM DISM.EXE: Registering information from the help collection from provider: WimManager.
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(wimcommands) and category(localtoplevelhelp) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(cleanup-wim) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(remount-wim) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(mount-wim) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(unmount-wim) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(commit-wim) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(get-wiminfo) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(get-mountedwiminfo) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(capture-image) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(append-image) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(export-image) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(delete-image) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(list-image) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(update-wimbootentry) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(get-wimbootentry) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(capture-customimage) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(apply-customdataimage) and category(wimcommands) for the provider(WimManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-05-17 14:08:56, Info DISM DISM.EXE: Getting the help information collection for the provider: GenericImagingManager.
2016-05-17 14:08:56, Info DISM DISM.EXE: Registering information from the help collection from provider: GenericImagingManager.
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(imagingcommands) and category(localtoplevelhelp) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(cleanup-mountpoints) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(remount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(mount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(unmount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(commit-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(get-imageinfo) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(get-mountedimageinfo) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(apply-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Succesfully registered the Help Item with topic(split-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-05-17 14:08:56, Info DISM DISM.EXE: Getting the help information collection for the provider: Compatibility Manager.
2016-05-17 14:08:56, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-05-17 14:08:56, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2016-05-17 14:08:56, Info DISM DISM.EXE:
2016-05-17 14:08:56, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

Verder heb ik SFC zeker al een paar keer helemaal laten draaien, dit maakt niks uit vandaar dat ik hem nu afbreek omdat het dan ook werkt en het anders heel lang duurt.

[wagenveld]

Vreemde log, weet je zeker dat dit de juiste is (als je dus die foutmelding krijgt)? Ik zou minimaal die foutmelding verwachten.

[sebasmac]

Yep, Log gecleaned Dism gestart en dan komt er dit uit. Ik vind het ook een vreemd verhaal

[wagenveld]

Check mijn (werkende) log, zelfde resultaat

code:

2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(imagingcommands) and category(localtoplevelhelp) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(cleanup-mountpoints) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(remount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(mount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(unmount-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(commit-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(get-imageinfo) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(get-mountedimageinfo) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(apply-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Succesfully registered the Help Item with topic(split-image) and category(imagingcommands) for the provider(GenericImagingManager).
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Getting the help information collection for the provider: Compatibility Manager.
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: 
2016-05-17 14:39:08, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

edit: Doe eens een alternatieve logfile specificeren?
dism /LogPath:<path to log file.log>

En voor de volledigheid ook de temp dir maar even:
/ScratchDir:<path_to_scratchdirectory>

https://technet.microsoft.com/en-us/library/hh825079.aspx

[ Voor 3% gewijzigd door wagenveld op 17-05-2016 14:56 ]

[Killah_Priest]

Zo te zien een combinatie van problemen :
0x80004005 is schijnbaar een access denied melding.
"The logger could not initialize" is een melding mbt het niet kunnen wegschrijven van de foutmelding naar de DISM log.

Hoewel ze mogelijk dezelfde oorzaak hebben moet je beide los van elkaar zien om het probleem goed te kunnen troubleshooten.
In de DISM log zul je hoogstwaarschijnlijk dus niet de oorzaak vinden van het probleem aangezien er een foutmelding komt mbt het wegschrijven van de error naar de log.
(Het kan uiteraard ook zo zijn dat de vermeende access denied ontstaat doordat de logfile gelocked is tot je sfc doet. Probeer de DISM log anders eens weg te gooien)

[JFTE]

Misschien Process Monitor mee laten draaien? Je kunt dan zien welke bestanden, register en poorten e.d. worden benaderd en of dit wel of niet gelukt is.

[mrtnptrs]

En wat gebeurd er als je Dism /Online /Cleanup-Image /RestoreHealth uitvoerd in commandprompt dat uitgevoerd is als adiministrator? Krijg je dan dezelfde error? Laat het commando wel volledig zijn werk doen als je geen error krijgt.