Windows 10: DISM FFU Error 1009

Discus and support DISM FFU Error 1009 in Windows 10 Installation and Upgrade to solve the problem; i am trying to Create an image to add to SCCM. (first time ever, new to this in SCCM) Built winpe USB 3.0 (16gb) with 1809 ADK and 1809 WINPEADK. i... Discussion in 'Windows 10 Installation and Upgrade' started by GavinLT, Dec 20, 2018.

  1. GAVINLT
    GavinLT Win User

    DISM FFU Error 1009


    i am trying to Create an image to add to SCCM. (first time ever, new to this in SCCM)


    Built winpe USB 3.0 (16gb) with 1809 ADK and 1809 WINPEADK.

    i have a fresh 1809 build.(Dell optiplex 5060. i7 8th gen) never connected to Internet or domain.
    installed the applications i wanted. (offline) no encryption on the disk.
    ran sysprep
    Booted into WINPE try to run this command:
    dism /capture-ffu /imagefile=e:\Win10.ffu /capturedrive=\\.\PhysicalDrive0 /name:Win10 /description:”Win1 1809 ffu”

    and it starts and immediately fails and gives me this error : 1009 ' the configuration registry database is corrupt."di
    *usb im trying to write to is 64GB 3.0



    heres the log. from dism/dism.log

    2018-12-20 10:55:19, Info DISM PID=1560 TID=1564 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager:DISM FFU Error 1009 :put_ScratchDir

    2018-12-20 10:55:19, Info DISM PID=1560 TID=1564 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct

    2018-12-20 10:55:19, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:19, Info DISM PID=1560 TID=1564 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession

    2018-12-20 10:55:19, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2018-12-20 10:55:19, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:19, Info DISM DISM Manager: PID=1560 TID=1564 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

    2018-12-20 10:55:19, Info DISM DISM.EXE:

    2018-12-20 10:55:19, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

    2018-12-20 10:55:19, Info DISM DISM.EXE:

    2018-12-20 10:55:19, Info DISM DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=amd64, Number of processors=12

    2018-12-20 10:55:19, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1

    2018-12-20 10:55:19, Info DISM DISM.EXE: Executing command line: dism /capture-ffu /image=E:\Win10.FFU /capturedrive=\\.\PhysicalDrive0 /name:Win10 /description:"Win1809 FFU"

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Warning DISM DISM Provider Store: PID=1560 TID=1564 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:19, Warning DISM DISM Provider Store: PID=1560 TID=1564 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-12-20 10:55:19, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.

    2018-12-20 10:55:19, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager

    2018-12-20 10:55:19, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.

    2018-12-20 10:55:19, Info DISM DISM.EXE: The /image option cannot be used with a local provider command

    2018-12-20 10:55:19, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    2018-12-20 10:55:19, Info DISM DISM.EXE:

    2018-12-20 10:55:19, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

    2018-12-20 10:55:19, Info DISM DISM.EXE:

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:19, Info DISM DISM Provider Store: PID=1560 TID=1564 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:30, Info DISM PID=1596 TID=1600 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager:DISM FFU Error 1009 :put_ScratchDir

    2018-12-20 10:55:30, Info DISM PID=1596 TID=1600 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct

    2018-12-20 10:55:30, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:30, Info DISM PID=1596 TID=1600 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession

    2018-12-20 10:55:30, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2018-12-20 10:55:30, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log

    2018-12-20 10:55:30, Info DISM DISM Manager: PID=1596 TID=1600 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

    2018-12-20 10:55:30, Info DISM DISM.EXE:

    2018-12-20 10:55:30, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

    2018-12-20 10:55:30, Info DISM DISM.EXE:

    2018-12-20 10:55:30, Info DISM DISM.EXE: Host machine information: OS Version=10.0.17763, Running architecture=amd64, Number of processors=12

    2018-12-20 10:55:30, Info DISM DISM.EXE: Dism.exe version: 10.0.17763.1

    2018-12-20 10:55:30, Info DISM DISM.EXE: Executing command line: dism /capture-ffu /imagefile=E:\Win10.FFU /capturedrive=\\.\PhysicalDrive0 /name:Win10 /description:"Win1809 FFU"

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Warning DISM DISM Provider Store: PID=1596 TID=1600 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Info DISM DISM Provider Store: PID=1596 TID=1600 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2018-12-20 10:55:30, Warning DISM DISM Provider Store: PID=1596 TID=1600 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2018-12-20 10:55:30, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.

    2018-12-20 10:55:30, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager

    2018-12-20 10:55:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.

    2018-12-20 10:55:30, Info DISM DISM FFU Provider: Drive path = \\.\PhysicalDrive0

    2018-12-20 10:55:30, Info DISM DISM FFU Provider: Disk size = 256060514304 Bytes (238.47 Gb)

    2018-12-20 10:55:30, Info DISM DISM FFU Provider: Partition style = 1 (0: MBR, 1: GPT, 2: RAW)

    2018-12-20 10:55:30, Info DISM DISM FFU Provider: Partition count = 4

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: COfflineHiveT<class CEmptyType>::Init#563 failed with 0x0.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: CWindowsOsHelper::GetOsInformation#197 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: CDiskReaderT<class CEmptyType>::GetOsInformation#280 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: CManifest::Initialize#836 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: CManifest::CreateInstance#536 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: FfuCaptureInternal#420 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: FfuCaptureImage#116 failed with 0x800703f1.

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: PID=1596 TID=1600 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:787 - CFfuManager::Capture(hr:0x800703f1)

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: PID=1596 TID=1600 Failed to capture an FFU image from '\\.\PhysicalDrive0'. - CFfuManager::InternalCmdCapture(hr:0x800703f1)

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: PID=1596 TID=1600 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x800703f1)

    2018-12-20 10:55:32, Error DISM DISM FFU Provider: PID=1596 TID=1600 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:227 - CFfuManager::ExecuteCmdLine(hr:0x800703f1)

    2018-12-20 10:55:32, Error DISM DISM.EXE: FfuManager processed the command line but failed. HRESULT=800703F1

    2018-12-20 10:55:32, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    2018-12-20 10:55:32, Info DISM DISM.EXE:

    2018-12-20 10:55:32, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

    2018-12-20 10:55:32, Info DISM DISM.EXE:

    2018-12-20 10:55:32, Info DISM DISM Provider Store: PID=1596 TID=1600 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2018-12-20 10:55:32, Info DISM DISM Provider Store: PID=1596 TID=1600 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2018-12-20 10:55:32, Info DISM DISM Provider Store: PID=1596 TID=1600 Disconnect

    :)
     
    GavinLT, Dec 20, 2018
    #1
  2. HEUSPEC
    heuspec Win User

    DISM Error While Capturing

    Hello ;

    I got an error while capturing an ffu image an tablet pc.

    Error code: 1009

    My batch file looks like this :

    rem == CaptureImage.bat ==

    rem == Set high-performance power scheme to speed deployment ==

    call powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

    DISM.exe /capture-ffu /imagefile=E:\408G1.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"408G1"

    Win_PE version is x86
     
    heuspec, Dec 20, 2018
    #2
  3. STEPHANIE SAL
    Stephanie Sal Win User
    DISM - Parameter "Cleanup-Image" is not known (error 87)

    Hello Eric,

    To troubleshoot your concern, we suggest that you run DISM Restore Health command. Refer to the steps provided below:

    • Open Command Prompt (Administrator).
    • Type the following command:
    DISM /Online /Cleanup-Image /RestoreHealth

    3. Press Enter.

    Let us know how it goes.

    Thank you.
     
    Stephanie Sal, Dec 20, 2018
    #3
  4. DAVIDY
    DavidY Win User

    DISM FFU Error 1009

    Windows ICD Hard Drive Partitioning


    I read somewhere that the option to create Production Media (as opposed to Clean) gives more options to add test scripts so maybe other scripts could be added in that option? I really don't know though.

    This page also suggests you can save your image as a FFU file (I never got that to work but haven't tried since ADK 1511) and then deploy with a DISM command, which presumably gives more control if you change some of the DISM parameters(?) But it's not as user friendly as inserting a bootable USB stick and letting it run.
    Lab 1: Customize and install Windows using the Windows Imaging and Configuration Designer (ICD)
     
    DavidY, Dec 20, 2018
    #4
Thema:

DISM FFU Error 1009

Loading...

  1. DISM FFU Error 1009 - Similar Threads - DISM FFU Error

  2. Error 1009 in the cmd prompt

    in Windows 10 Gaming
    Error 1009 in the cmd prompt: Hi, I'm currently having an issue with fully resetting my computer. Here are all the steps to try and fix it I have done so far:1: First of all, when I try and do a full reset of the computer, it restarts my computer and then starts the reset, stays at 1% completion and then...

  3. Error 1009 in the cmd prompt

    in Windows 10 Software and Apps
    Error 1009 in the cmd prompt: Hi, I'm currently having an issue with fully resetting my computer. Here are all the steps to try and fix it I have done so far:1: First of all, when I try and do a full reset of the computer, it restarts my computer and then starts the reset, stays at 1% completion and then...

  4. DISM /capture-ffu getting error 112

    in Windows 10 Gaming
    DISM /capture-ffu getting error 112: Why am I always getting error 112 in DISM when trying to run capture-ffu? I am sure the drive I am trying to capture is smaller than the drive I am trying to save the file to....

  5. DISM /capture-ffu getting error 112

    in Windows 10 Software and Apps
    DISM /capture-ffu getting error 112: Why am I always getting error 112 in DISM when trying to run capture-ffu? I am sure the drive I am trying to capture is smaller than the drive I am trying to save the file to....

  6. DISM /capture-ffu getting error 112

    in Windows 10 Installation and Upgrade
    DISM /capture-ffu getting error 112: Why am I always getting error 112 in DISM when trying to run capture-ffu? I am sure the drive I am trying to capture is smaller than the drive I am trying to save the file to....

  7. DISM Error 1009 – The configuration registry database is corrupt

    in Windows 10 News
    DISM Error 1009 – The configuration registry database is corrupt: [ATTACH]If when you attempt running the DISM command on your Windows 10 device and […] This article DISM Error 1009 – The configuration registry database is corrupt first appeared on TheWindowsClub.com. read more...

  8. DISM /split-ffu option doesn't work in win10 - 2004

    in Windows 10 Ask Insider
    DISM /split-ffu option doesn't work in win10 - 2004: I am unable to split FFU using dism /split-ffu command. The FFU image was created with /compress:none option as per Microsoft documentation. The command line i am executing : dism /Split-FFU /imagefile:fullimage.ffu /sfufile:image.sfu /filesize:1024 Almost immediately i...

  9. Error - DISM FFU Provider: CDiskReader::GetBlockAllocationBitmap#136 failed with 0x80070032.

    in Windows 10 BSOD Crashes and Debugging
    Error - DISM FFU Provider: CDiskReader::GetBlockAllocationBitmap#136 failed with 0x80070032.: When I am capturing ffu image of a MOXA MC1121(windows10), an error 50 occurred as the photo below. [IMG] and the error logs are [ATTACH] However, I couldn't find any solution regarding Error DISM DISM FFU Provider:...

  10. DISM - Clone and Deploy using FFU Image

    in Windows 10 Tutorials
    DISM - Clone and Deploy using FFU Image: How to: DISM - Clone and Deploy using FFU Image [img] Information Since Windows 10 version 1709, you can use DISM to capture and deploy FFU (Full Flash Update) images. FFU captures a disk sector by sector to a file container that holds an exact image of the disk. This...

Users found this page by searching for:

  1. dism 1009 error

    ,

  2. dism /capture-ffu error 1009

    ,

  3. dism capture エラー 1009

    ,
  4. capture-ffu エラー 1009,
  5. cofflinehivet clas cemptytype,
  6. dism capture ffu error 1009,
  7. capture-ffu tid=9056 failed to load the provider,
  8. FFU Provider,
  9. dism capture-ffu error 1009,
  10. dism error 1009,
  11. error 1009 windows 10,
  12. capture ffu configuration database is corrupt,
  13. CDiskReaderT<class CEmptyType>::GetOsInformation,
  14. getosinformation#280 capture-ffu,
  15. Windows PE error 1009