Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

Diskutiere Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update im Windows 10 News Forum im Bereich Windows 10 Foren; Hallo runit, leider funktioniert das nicht! Hier das DISM-Log (sorry wegen der Länge): Die Fehlermeldung wird ausgegeben: … konnte wegen eines E/A-Fehlers nicht ausgeführt werden. ...

+ Antworten + Neues Thema erstellen
Seite 6 von 7 ErsteErste ... 4567 LetzteLetzte
Ergebnis 51 bis 60 von 61
  1. #51
    Standardavatar
    Version
    1511
    System
    ASROCK, AMD A8-5600K APU Radeon HD Graphics AMD Radeon HD7560D, 8 GB RAM, 3 TB HDs, Win10/Linux Dual

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Hallo runit,
    leider funktioniert das nicht!
    Hier das DISM-Log (sorry wegen der Länge):

    Die Fehlermeldung wird ausgegeben:
    … konnte wegen eines E/A-Fehlers nicht ausgeführt werden. Was soll das für ein E/A-Fehler sein? Das DVD-Laufwerk lief und läuft noch immer 1a.

    LG, Boy


    2016-10-21 22:10:47, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2016-10-21 22:10:47, Info DISM DISM.EXE:
    2016-10-21 22:10:47, Info DISM DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=4
    2016-10-21 22:10:47, Info DISM DISM.EXE: Dism.exe version: 10.0.10586.0
    2016-10-21 22:10:47, Info DISM DISM.EXE: Executing command line: DISM /Online /Cleanup-Image /RestoreHealth /source:wim:X:\install.wim:1 /limitaccess
    2016-10-21 22:10:47, Info DISM DISM Provider Store: PID=8964 TID=8560 Getting Provider FolderManager - CDISMProviderStore::GetProvider
    2016-10-21 22:10:47, Info DISM DISM Provider Store: PID=8964 TID=8560 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:10:47, Info DISM DISM Provider Store: PID=8964 TID=8560 Loading Provider from location C:\WINDOWS\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:10:47, Info DISM DISM Provider Store: PID=8964 TID=8560 Connecting to the provider located at C:\WINDOWS\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:10:47, Info DISM DISM Manager: PID=8964 TID=8560 physical location path: C:\ - CDISMManager::CreateImageSession
    2016-10-21 22:10:47, Info DISM DISM Manager: PID=8964 TID=8560 Event name for current DISM session is Global\{F8849D0D-54C2-43E1-8067-3E2AEE34908D} - CDISMManager::CheckSessionAndLock
    2016-10-21 22:10:47, Info DISM DISM Manager: PID=8964 TID=8560 Create session event 0x16c for current DISM session and event name is Global\{F8849D0D-54C2-43E1-8067-3E2AEE34908D} - CDISMManager::CheckSessionAndLock
    2016-10-21 22:10:47, Info DISM DISM Manager: PID=8964 TID=8560 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2016-10-21 22:11:15, Info DISM DISM Manager: PID=8964 TID=8560 Successfully loaded the ImageSession at "C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C" - CDISMManager::LoadRemoteImageSession
    2016-10-21 22:11:15, Info DISM DISM Image Session: PID=4912 TID=5032 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2016-10-21 22:11:15, Info DISM DISM Provider Store: PID=4912 TID=5032 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2016-10-21 22:11:15, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:15, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:20, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:11:20, Info DISM DISM OS Provider: PID=4912 TID=5032 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2016-10-21 22:11:20, Info DISM DISM OS Provider: PID=4912 TID=5032 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2016-10-21 22:11:20, Info DISM DISM OS Provider: PID=4912 TID=5032 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath
    2016-10-21 22:11:20, Warning DISM DISM OS Provider: PID=4912 TID=5032 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
    2016-10-21 22:11:20, Info DISM DISM Provider Store: PID=4912 TID=5032 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2016-10-21 22:11:20, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:20, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Warning DISM DISM Provider Store: PID=4912 TID=5032 Failed to Load the provider: C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007 007e)
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Info DISM DISM Manager: PID=8964 TID=8560 Image session successfully loaded from the temporary location: C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C - CDISMManager::CreateImageSession
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Info DISM DISM.EXE: Target image information: OS Version=10.0.10586.570, Image architecture=amd64
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:23, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:11:25, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:11:25, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Package Manager: PID=4912 TID=5032 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2016-10-21 22:14:19, Info DISM DISM Package Manager: PID=4912 TID=5032 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
    2016-10-21 22:14:19, Info DISM DISM Package Manager: PID=4912 TID=5032 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\IBSProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM OS Provider: PID=4912 TID=5032 Successfully loaded the hive. - CDISMOSServiceManager:etermineBootDrive
    2016-10-21 22:14:19, Info DISM DISM Driver Manager: PID=4912 TID=5032 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\Wow64provider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Warning DISM DISM Provider Store: PID=4912 TID=5032 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x800 04002)
    2016-10-21 22:14:19, Warning DISM DISM Provider Store: PID=4912 TID=5032 Failed to Load the provider: C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8000 4002)
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:19, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\EmbeddedProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Warning DISM DISM Provider Store: PID=4912 TID=5032 Failed to Load the provider: C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007 007e)
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\AppxProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\ProvProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\AssocProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\GenericProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\OfflineSetupProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Loading Provider from location C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Connecting to the provider located at C:\Users\BOYHER~1\AppData\Local\Temp\170CB539-A305-42B8-836B-554BAD28FE1C\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2016-10-21 22:14:21, Info DISM DISM Transmog Provider: PID=4912 TID=5032 Current image session is [ONLINE] - CTransmogManager::GetMode
    2016-10-21 22:14:21, Info DISM DISM Transmog Provider: PID=4912 TID=5032 Audit Mode: [No] - CTransmogManager::Initialize
    2016-10-21 22:14:21, Info DISM DISM Transmog Provider: PID=4912 TID=5032 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
    2016-10-21 22:14:21, Info DISM DISM Transmog Provider: PID=4912 TID=5032 Product Type: [WinNT] - CTransmogManager::Initialize
    2016-10-21 22:14:21, Info DISM DISM Transmog Provider: PID=4912 TID=5032 Product Type ServerNT : [No] - CTransmogManager::Initialize
    2016-10-21 22:14:21, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2016-10-21 22:14:21, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2016-10-21 22:14:21, Info DISM DISM Provider Store: PID=4912 TID=5032 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2016-10-21 22:14:21, Info DISM DISM Package Manager: PID=4912 TID=5032 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2016-10-21 22:14:21, Info DISM DISM Package Manager: PID=4912 TID=5032 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2016-10-21 22:14:21, Info DISM DISM Package Manager: PID=4912 TID=5032 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2016-10-21 22:15:08, Warning DISM DISM Package Manager: PID=4912 TID=5032 CBS AddSource failed with HRESULT=0x80070002! - CDISMPackageManager::Internal_Finalize
    2016-10-21 22:15:08, Info DISM DISM Package Manager: PID=4912 TID=5032 CBS session options=0x28100! - CDISMPackageManager::Internal_Finalize
    2016-10-21 23:45:59, Info DISM DISM Package Manager: PID=4912 TID=4432 Error in operation: (null) (CBS HRESULT=0x8007045d) - CCbsConUIHandler::Error
    2016-10-21 23:45:59, Error DISM DISM Package Manager: PID=4912 TID=5032 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800704 5d)
    2016-10-21 23:45:59, Error DISM DISM Package Manager: PID=4912 TID=5032 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x8007045d)
    2016-10-21 23:45:59, Error DISM DISM Package Manager: PID=4912 TID=5032 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupI mage(hr:0x8007045d)
    2016-10-21 23:45:59, Error DISM DISM Package Manager: PID=4912 TID=5032 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800 7045d)
    2016-10-21 23:45:59, Info DISM DISM Package Manager: PID=4912 TID=5032 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2016-10-21 23:45:59, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=8007045D
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Package Manager: PID=4912 TID=5032 Finalizing CBS core. - CDISMPackageManager::Finalize
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=4912 TID=5032 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Manager: PID=8964 TID=8560 Closing session event handle 0x16c - CDISMManager::CloseImageSession
    2016-10-21 23:45:59, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2016-10-21 23:45:59, Info DISM DISM.EXE:
    2016-10-21 23:45:59, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2016-10-21 23:45:59, Info DISM DISM.EXE:
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=8964 TID=8560 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=8964 TID=8560 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2016-10-21 23:45:59, Info DISM DISM Provider Store: PID=8964 TID=8560 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    LG, Boy

  2. #52
    Standardavatar
    Version
    Win10 Home 64 bit, 1607 Build 14393.447

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Aus dem Log geht hervor, dass DISM-Prozess auf Deinen persönlichen AppData-Ordner nicht zugreifen konnte, wenn ich das richtig sehe. Das Antivir wurde zuvor mit dem Herstellertool vollständig entfernt?
    Antivir entfernen - alle Removal-Tools

    Naja, ich würde das Inplace-Upgrade auch nicht über DISM, sondern über Media Creation Tool/Stick machen. Beim Media Creation Tool musst Du das richtige wählen, das 1511 oder das 1607, je nachdem, welche Version Du hast. Aus dem Log ersehe ich, dass Du das 1511er haben müsstest. Den Link zum Download füge ich an. Für Inplace öffnest Du nach Erstellung des Sticks den Stick und führst setup.exe aus.

    Datenträger für Update oder Neuinstallation von Stick und DVD

    https://techjourney.net/how-to-downl...bile-emulator/

  3. #53
    Standardavatar
    Version
    noch keine
    System
    später

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Hallo Areiland,
    wo plaziere ich mein Anliegen am besten?

    Nach dem Funktionsupdate für Windows 10 Version 1607 (Anniversary Update) am 22.10.2016 startet mein Corel Graphis Suite X5, Version 15.2.0.686 nicht mehr. Angeblich liegt jetzt eine Inkompatibilität vor, aber vor dieser letzten Aktualisierung klappte es reibungslos.
    Was kann ich tun?


    Besten Dank im Voraus!
    Gruß Heinzi

  4. #54
    Avatar von areiland
    Version
    Windows 10 Pro x64 Build 1607 14393.222
    System
    970M Pro3,FX6350,ATI 7730,16GB DDR3 1600,SSD256 GB,MK7559GSXP,SH224BB

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Im Unterforum "Software" vielleicht? Sollte es dort fehl platziert sein, kann ich es immer noch problemlos woanders hin verschieben.

  5. #55
    Standardavatar
    Version
    1511
    System
    ASROCK, AMD A8-5600K APU Radeon HD Graphics AMD Radeon HD7560D, 8 GB RAM, 3 TB HDs, Win10/Linux Dual

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Hallo runit (& @ alex),
    danke für Eure schier unendliche Geduld!
    Ich habe heute abend die Reißleine gezogen und einen Clean-Install von der 1607er-ISO-DVD gemacht. Der ist schnell und sauber durchgelaufen und funktioniert 1a und sauschnell; und bietet mir jetzt die Gelegenheit, nur noch die nötigsten Apps & Programme zu installieren (sprich: auszumisten).
    Ich denke, damit kann ich mich aus diesem Thread erst mal verabschieden. Ich fühle mich erleichtert.
    Zudem habe ich unter Linux-Mint in der VirtualBox ein WIN7SP1 eingerichtet, für alle Fälle, das auch superschnell läuft. Bis zum nächsten Event werde ich also erst mal Ruhe geben.
    Noch mal ganz herzlichen Dank an alle Beteiligten, die sich solche Mühe mit mir gegeben haben!
    LG, Boy

  6. #56
    Avatar von raptor49
    System
    Win 10/ 64 u 32, Suse Leap 42.2/64, Lubuntu 14.04 / 32

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Zitat Zitat von boyherre Beitrag anzeigen
    Ich habe heute abend die Reißleine gezogen und einen Clean-Install von der 1607er-ISO-DVD gemacht. Der ist schnell und sauber durchgelaufen und funktioniert 1a und sauschnell;

    Das Tragische daran ist, das selbst MS nicht in der Lage ist, solche Tips zu geben. Das müssen die user dann erst in Foren wie diesem lesen.

  7. #57
    Standardavatar
    Version
    Windows 10 Home
    System
    Intel Xeon E3-1230 v3, 8 GB Ram, ASUS Geforce GTX 770

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Zitat Zitat von raptor49 Beitrag anzeigen
    Das Tragische daran ist, das selbst MS nicht in der Lage ist, solche Tips zu geben. Das müssen die user dann erst in Foren wie diesem lesen.
    Der Grund warum sie das nicht machen, ist sicher der, dass der durchschnittliche PC-User mit solchen vermeintlich tollen Tipps hoffnungslos überfordert wäre. Insofern ist es schon verständlich, dass man sowas lieber erfahreneren Nutzern überlässt. Und, ehrlich gesagt, ist das auch gut so, denn wenn man sowas Leuten überlässt, die keine Ahnung haben, dann kann das böse enden. Ich jedenfalls würde nicht zu Tantchen Trude aus Buxtehude gehen, und von der verlangen, dass sie mal eben Windows aufspielt.

    Abgesehen davon kann MS sich auch nicht um alles kümmern. Zumindest dürfte es in fortgeschritteneren Kreisen schon mittlerweile bekannt sein, dass man das Media Creation Tool verwenden kann, um Windows, oder Updates einzuspielen.

  8. #58
    Avatar von EynSirMarc
    Version
    Windows 10 Enterprise 1607 14393.479 x64/Windows pro 14971 x64/Windows Server 2016 14393
    System
    M5a99FX, amd fx8350,16GB, HD7770

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    schön wäre noch wenn sich Media Creation Tool updaten würde, oder immer nach der neusten windows version schaut.

  9. Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Hi
    Schau dir mal diesen Windows-Ratgeber an!

    MfG
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  10. #59
    Standardavatar
    Version
    Windows 10 Home
    System
    Intel Xeon E3-1230 v3, 8 GB Ram, ASUS Geforce GTX 770
    Warum sollte sich das updaten, wenn eh immer die neueste Windows-Version für das Beschreiben des Sticks, oder der DVD gezogen wird, wenn man das Tool verwendet?

  11. #60
    Standardavatar
    Version
    Win10 Home 64 bit, 1607 Build 14393.447

    Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

    Das MCT bei MS zum Download enthält immer die aktuelle Version xxxxx.0. Nach der Installation oder noch während erfolgen unmittelbar alle darauf folgenden Updates, sodass man nach der Installation auch die aktuelle Build haben sollte. Wenn ich das MCT nutze, ist dies bei mir so.


Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update

Windows 10: etwa ein Drittel aller Win-10-User nutzen das Anniversary Update - Ähnliche Themen


  1. Umfrage: ist das Windows 10 Anniversary Update schon angekommen?: Microsoft verteilt seit dem 2. August das auch als Redstone bekannte Anniversary Update, doch etliche Nutzer warten bisher vergeblich auf diese...



  2. WIN 10 Anniversary Update - unbekannte App verhindert das Update: 7986 Beim Anniversary Update bleibt das Update hängen: "Deinstallieren Sie diese App, da sie nicht mit Windows 10 kompatibel ist. Manuell...



  3. Windows 10 (Mobile): wie man das Anniversary Update eventuell schneller bekommt: Microsoft verteilt ab heute das erste umfassende Update für Windows 10 und Windows 10 Mobile. Damit die Server geschont werden, wird die auch unter...



  4. Windows 10 - fast die Hälfte aller Steam-User nutzen Windows 10: Nach nunmehr fast einem Jahr Marktpräsenz kann sich Windows 10 bezugnehmend der Statistiken der Marktforscher von Netmarketshare immerhin den zweiten...



  5. Windows 10: schon ein Viertel der Steam-User nutzen das neue Betriebssystem: Laut den neuesten Hochrechnungen auf Steam hat es Microsofts Windows 10 mit einen Zuwachs von 2,64 Prozentpunkten auf eine Marktpräsenz von fast 27...


Sucheingaben