Windows 10: Error in DISM (Error 605)

Discus and support Error in DISM (Error 605) in Windows 10 BSOD Crashes and Debugging to solve the problem; I had got BSODs twice a few days ago, having the stopcode MEMORY_MANAGEMENT. after that I ran CHKDSK and it scanned the drive. Then i started DISM.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by GokulV, May 21, 2019.

  1. GokulV Win User

    Error in DISM (Error 605)


    I had got BSODs twice a few days ago, having the stopcode MEMORY_MANAGEMENT.


    after that I ran CHKDSK and it scanned the drive.


    Then i started DISM. Usually all would go well but for some reason this time it stopped at 8.3% with this message-


    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1

    Image Version: 10.0.17763.503

    [==== 8.3% ]
    Error: 605

    The specified buffer contains ill-formed data.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log



    These are the logs after the DISM -





    2019-05-21 19:27:37, Info DISM PID=8796 TID=7640 Scratch directory set to 'C:\Users\dt\AppData\Local\Temp\'. - CDISMManager:Error in DISM (Error 605) :put_ScratchDir
    2019-05-21 19:27:37, Info DISM PID=8796 TID=7640 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
    2019-05-21 19:27:37, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:37, Info DISM PID=8796 TID=7640 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession
    2019-05-21 19:27:37, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:37, Info DISM DISM Provider Store: PID=8796 TID=7640 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-05-21 19:27:37, Info DISM DISM Provider Store: PID=8796 TID=7640 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:37, Info DISM DISM Provider Store: PID=8796 TID=7640 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:37, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:37, Info DISM DISM Manager: PID=8796 TID=7640 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2019-05-21 19:27:37, Info DISM DISM.EXE:
    2019-05-21 19:27:37, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2019-05-21 19:27:37, Info DISM DISM.EXE:
    2019-05-21 19:27:37, Info DISM DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=amd64, Number of processors=4
    2019-05-21 19:27:37, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1
    2019-05-21 19:27:37, Info DISM DISM.EXE: Executing command line: DISM /online /cleanup-image /restorehealth
    2019-05-21 19:27:37, Info DISM DISM Provider Store: PID=8796 TID=7640 Connecting to the provider located at C:\WINDOWS\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:37, Info DISM DISM Manager: PID=8796 TID=7640 physical location path: C:\ - CDISMManager::CreateImageSession
    2019-05-21 19:27:37, Info DISM DISM Manager: PID=8796 TID=7640 Event name for current DISM session is Global\{B63F5F8B-1B24-499C-8E04-0738A5728A5E} - CDISMManager::CheckSessionAndLock
    2019-05-21 19:27:37, Info DISM DISM Manager: PID=8796 TID=7640 Create session event 0x1fc for current DISM session and event name is Global\{B63F5F8B-1B24-499C-8E04-0738A5728A5E} - CDISMManager::CheckSessionAndLock
    2019-05-21 19:27:37, Info DISM DISM Manager: PID=8796 TID=7640 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2019-05-21 19:27:38, Info DISM DISM Manager: PID=8796 TID=7640 Successfully loaded the ImageSession at "C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A" - CDISMManager::LoadRemoteImageSession
    2019-05-21 19:27:38, Info DISM DISM Image Session: PID=10484 TID=10524 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:38, Info DISM DISM OS Provider: PID=10484 TID=10524 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2019-05-21 19:27:38, Info DISM DISM OS Provider: PID=10484 TID=10524 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:38, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-05-21 19:27:38, Warning DISM DISM Provider Store: PID=10484 TID=10524 Failed to load the provider: C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-05-21 19:27:38, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:38, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
    2019-05-21 19:27:38, Info DISM DISM Manager: PID=8796 TID=7640 Image session successfully loaded from the temporary location: C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A - CDISMManager::CreateImageSession
    2019-05-21 19:27:38, Info DISM DISM.EXE: Target image information: OS Version=10.0.17763.503, Image architecture=amd64
    2019-05-21 19:27:38, Info DISM DISM.EXE: Image session version: 10.0.17763.1
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:38, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:38, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-05-21 19:27:38, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_SUCCESS
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2019-05-21 19:27:40, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-05-21 19:27:40, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_SUCCESS
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2019-05-21 19:27:40, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.503_none_7e5131134cd5bd73\wcp.dll' : got STATUS_SUCCESS
    2019-05-21 19:27:40, Info DISM DISM Driver Manager: PID=10484 TID=10524 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Warning DISM DISM Provider Store: PID=10484 TID=10524 Failed to load the provider: C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Transmog Provider: PID=10484 TID=10524 Current image session is [ONLINE] - CTransmogManager::GetMode
    2019-05-21 19:27:40, Info DISM DISM Transmog Provider: PID=10484 TID=10524 Audit Mode: [No] - CTransmogManager::Initialize
    2019-05-21 19:27:40, Info DISM DISM Transmog Provider: PID=10484 TID=10524 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
    2019-05-21 19:27:40, Info DISM DISM Transmog Provider: PID=10484 TID=10524 Product Type: [WinNT] - CTransmogManager::Initialize
    2019-05-21 19:27:40, Info DISM DISM Transmog Provider: PID=10484 TID=10524 Product Type ServerNT : [No] - CTransmogManager::Initialize
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Connecting to the provider located at C:\Users\dt\AppData\Local\Temp\8B91BF58-5A3E-4AA5-A494-0C8C0DD3307A\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM Provider Store: PID=10484 TID=10524 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2019-05-21 19:27:40, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2019-05-21 19:27:40, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager
    2019-05-21 19:27:40, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler:Error in DISM (Error 605) :private_ValidateCmdLine
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-05-21 19:27:40, Info DISM DISM Package Manager: PID=10484 TID=10524 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
    2019-05-21 19:28:07, Info DISM DISM Package Manager: PID=10484 TID=10540 Error in operation: (null) (CBS HRESULT=0x8007025d) - CCbsConUIHandler::Error
    2019-05-21 19:28:07, Error DISM DISM Package Manager: PID=10484 TID=10524 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x8007025d)
    2019-05-21 19:28:07, Error DISM DISM Package Manager: PID=10484 TID=10524 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x8007025d)
    2019-05-21 19:28:07, Error DISM DISM Package Manager: PID=10484 TID=10524 Failed to restore the image health. - CPackageManagerCLIHandler:Error in DISM (Error 605) :processCmdLine_CleanupImage(hr:0x8007025d)
    2019-05-21 19:28:07, Error DISM DISM Package Manager: PID=10484 TID=10524 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x8007025d)
    2019-05-21 19:28:07, Info DISM DISM Package Manager: PID=10484 TID=10524 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-05-21 19:28:07, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=8007025D
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Package Manager: PID=10484 TID=10524 Finalizing CBS core. - CDISMPackageManager::Finalize
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=10484 TID=10524 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Manager: PID=8796 TID=7640 Closing session event handle 0x1fc - CDISMManager::CleanupImageSessionEntry
    2019-05-21 19:28:07, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2019-05-21 19:28:07, Info DISM DISM.EXE:
    2019-05-21 19:28:07, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2019-05-21 19:28:07, Info DISM DISM.EXE:
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=8796 TID=7640 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=8796 TID=7640 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-05-21 19:28:07, Info DISM DISM Provider Store: PID=8796 TID=7640 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider





    PC specs-


    Intel Core i3-4130

    8 GB DDR3

    Running Windows 10 version 1809






    Also after the BSODs, I hear a click from the HDD occasionally.


    Can I get any help on what to do?


    Thanks

    :)
     
    GokulV, May 21, 2019
    #1
  2. KieX Win User

    Error: No work available to process

    Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

    On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

    If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

    At least those steps will rule out problems from the WCG end.
     
  3. Rey Bel1 Win User
    DISM restore health fail error 605 - 0x8007025d in the log file

    Hi,

    Error 0x8007025D may arise from a bad or corrupt RAM. To better assist you we'd like to ask the following questions:

    • What is the make and model of your device?
    • Have you made any recent changes on your device prior to the issue?
    • What have you done so far to resolve the issue?

    Meanwhile, we suggest that check Andre Da Costa's
    How to Troubleshoot Common Setup and Stop Errors During Windows 10 Installation
    for more information about error and how to resolve it. You can locate the error code and the corresponding steps to resolve it by pressing
    Ctrl+F then type 0x8007025D in the search bar, and then press Enter.

    We look forward to your response.
     
    Rey Bel1, May 21, 2019
    #3
  4. x01r Win User

    Error in DISM (Error 605)

    atioglxx.dll OpenGL Error ! Error in DISM (Error 605) :(

    *** errors in the installer !!!

    * manuel make *

    _____________________
    1.step :

    http://support.amd.com/us/kbarticles/Pages/CatalystAGPHotfix.aspx

    Catalyst 9.9 Hotfix for Windows XP Professional and Home Edition

    ati.com/drivers/hotfix/9-9_agp-hotfix_xp32_dd_ccc.exe

    _____________________
    2.step :

    ( install *Smile Error in DISM (Error 605) :) )

    C:\ATI\Support\9-9_agp-hotfix_xp32_dd_ccc

    _____________________
    3.step :

    C:\ATI\Support\9-9_agp-hotfix_xp32_dd_ccc\Driver\XP_INF\B_86849\atioglxx.dl_

    ( X:\....\9-9_agp-hotfix_xp32_dd_ccc\Driver\XP_INF\B_ ,,,, \atioglxx.dl_ )

    _____________________
    4.step :

    ( ReName *Smile Error in DISM (Error 605) :) )

    atioglxx.dl_ -> atioglxx.dll

    _____________________
    5.step :

    ( Move *Smile Error in DISM (Error 605) :) )

    atioglxx.dll -> C:\WINDOWS\system32

    _____________________
    6.step :

    restart PC ! OK *Smile Error in DISM (Error 605) :)

    ATi OpenGL (atioglxx.dll) No-Errors ! *Big Grin Error in DISM (Error 605) :D
     
Thema:

Error in DISM (Error 605)

Loading...
  1. Error in DISM (Error 605) - Similar Threads - Error DISM Error

  2. Troubleshootihng DISM error 605

    in Windows 10 BSOD Crashes and Debugging
    Troubleshootihng DISM error 605: Windows 10 version 2004 I've forgotten the issue I was researching on the web, but one of the solutions for repair was to run the DISM command scan health and restore health. When I ran the commands, at about 50% completion, Error 605 was reported. Web searching...
  3. DISM Error/CkhDsk Errors

    in Windows 10 Installation and Upgrade
    DISM Error/CkhDsk Errors: Error: 0x800f081f The source files could not be found. File record segment 43E10 is corrupt. File record segment 43ED8 is corrupt. File record segment 43EDA is corrupt. File record segment 43EDB is corrupt. Tried using DISM Tried using CHKDSK Tried using SFC...
  4. DISM ERROR

    in Windows 10 BSOD Crashes and Debugging
    DISM ERROR: Hi, i did an sfc /scannow and got an error saying some components cant be fixed. So i did a Dism check health and scan health, both said there are no errors. Then i did a dism restorehealth but the operation is completed at 84.9%. Please help i am experiencing a lot of issues...
  5. Can't recover the Windows 10 with DISM - Error 605 and I do not want to rest windows!

    in Windows 10 Ask Insider
    Can't recover the Windows 10 with DISM - Error 605 and I do not want to rest windows!: Can't recover the Windows 10 with DISM - Error 605 and I do not want to rest windows! DISM.exe /Online /Cleanup-image /Restorehealth Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.535...
  6. dism error

    in Windows 10 Drivers and Hardware
    dism error: so i had upgraded my ram lately which was giving me Bsod error.when i gave to technician he tested the ram and my laptop and he said my windows software was affected .so i decided to do dism check and using 'DISM /Online /Cleanup-Image /CheckHealth' in cmd it showed messange...
  7. DISM error

    in Windows 10 BSOD Crashes and Debugging
    DISM error: My laptop had a lot of corrupted files after I accidentally switched off the wrong switch. I ran DISM restore health, the following was returned. C:\WINDOWS\system32>dism /Online /Cleanup-image /RestoreHealth Deployment Image Servicing and Management tool Version:...
  8. DISM Error

    in Windows 10 Performance & Maintenance
    DISM Error: Win 10 Pro x64 1709 Error After using Dism /Online /Cleanup-Image /RestoreHealth Any tips? Stops at 85% And i Have Windows Update Service Enabled. I attached DISM Log, ty. 132539
  9. DISM COMException Error

    in Windows 10 Performance & Maintenance
    DISM COMException Error: I've discovered a weird issue on Windows 10x64 10525 PS C:\WINDOWS\system32> dism.exe /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.10525.0 Image Version: 10.0.10525.0...
  10. 10130 - DISM error

    in Windows 10 Support
    10130 - DISM error: Getting this error when running DISM after a clean install: >Dism /Online /Cleanup-Image /StartComponentCleanup Deployment Image Servicing and Management tool Version: 10.0.10130.0 Image Version: 10.0.10130.0...

Users found this page by searching for:

  1. dism error 605

    ,
  2. error 605 dism

    ,
  3. dism error 605 ill-formed data

    ,
  4. DISM Error: 605,
  5. dism error 605 ill formed data,
  6. Dism fails with error code 605,
  7. windows error 605,
  8. dism error 605 the specified buffer contains ill-formed data,
  9. windows 10 dism tool error 605 the specified buffer contains ill-formed data,
  10. error 605 windows 10,
  11. dism initialized panther logging at c:\windows\logs\dism\dism.log,
  12. dism error 605 ill-formed,
  13. error: 605 the specified buffer contains ill-formed data.,
  14. dism.exe error 605,
  15. dism the specified buffer contains ill-formed