Windows 10: DISM /optimize-ffu has anyone got it to work?

Discus and support DISM /optimize-ffu has anyone got it to work? in Windows 10 Software and Apps to solve the problem; Honestly after spending 2 days trying to make this switch work I really do not know what to do next and about to punch this computers lights out.So i... Discussion in 'Windows 10 Software and Apps' started by AlexBurke5, Apr 17, 2025.

  1. DISM /optimize-ffu has anyone got it to work?


    Honestly after spending 2 days trying to make this switch work I really do not know what to do next and about to punch this computers lights out.So i have a windows 11 24h2 build done. Sysprepped and ready for imaging.I Boot into WinPE generated from the latest deployment toolkit.I use dism /capture-ffu... etc. to create an FFU fileThis file restores perfectly fine on machines with the correct HDD size using dism /apply-ffu. But with FFU files if the drive is smaller or larger it wont do the partitions right, smaller disk just fails, larger disks doesn't use all space So you apparently have

    :)
     
    AlexBurke5, Apr 17, 2025
    #1
  2. 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 /optimize-ffu has anyone got it to work? :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 /optimize-ffu has anyone got it to work? :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, Apr 17, 2025
    #2
  3. Jeannine Shiu, Apr 17, 2025
    #3
  4. RejZoR Win User

    DISM /optimize-ffu has anyone got it to work?

    How to get damn DISM to work?

    Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

    After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.
     
    RejZoR, Apr 17, 2025
    #4
Thema:

DISM /optimize-ffu has anyone got it to work?

Loading...
  1. DISM /optimize-ffu has anyone got it to work? - Similar Threads - DISM optimize ffu

  2. DISM /optimize-ffu has anyone got it to work?

    in Windows 10 Gaming
    DISM /optimize-ffu has anyone got it to work?: Honestly after spending 2 days trying to make this switch work I really do not know what to do next and about to punch this computers lights out.So i have a windows 11 24h2 build done. Sysprepped and ready for imaging.I Boot into WinPE generated from the latest deployment...
  3. 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....
  4. 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....
  5. 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....
  6. 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...
  7. Has anyone used DISM++ ?

    in Windows 10 Software and Apps
    Has anyone used DISM++ ?: Hi - I found this and wanted to know if anyone has used it or not. Looks like eye candy to me, so I wanted to inquire. DISM++ is a Windows OS Image Customizer and Size Reducer Thanks. *Smile 139408
  8. DISM FFU Error 1009

    in Windows 10 Installation and Upgrade
    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...
  9. Has Anyone Got Experience of Using Flowcode?

    in Windows 10 Software and Apps
    Has Anyone Got Experience of Using Flowcode?: Greetings Earthlings. Newbie to this forum, go easy on me. I'm thinking about purchasing a site license for a program called FLOWCODE? It's a programming app that allows the use of (for example) flow charts. I'm currently using SUBLIME TEXT however I'm investigating...
  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...