Windows 10: DISM /split-ffu option doesn't work in win10 - 2004

Discus and support DISM /split-ffu option doesn't work in win10 - 2004 in Windows 10 Ask Insider to solve the problem; 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... Discussion in 'Windows 10 Ask Insider' started by /u/dmonk36, Jun 7, 2020.

  1. /U/DMONK36
    /u/dmonk36 Win User

    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 am getting response:


    Deployment Image Servicing and Management tool

    Version: 10.0.19041.1

    The operation completed successfully.
    ​

    However, nothing is created. Could anyone tell what's going on? or has anyone ever used "split-ffu" option with DISM successfully?

    submitted by /u/dmonk36
    [link] [comments]

    :)
     
    /u/dmonk36, Jun 7, 2020
    #1
  2. CEREBERUS
    cereberus Win User

    DISM - Clone and Deploy using FFU Image  

    @Kari


    /Apply-Image

    For WIM, this command applies a Windows image file (.wim) or a split Windows image (.swm) files to a specified partition. Beginning with Windows 10, version 1607, DISM can apply and capture extended attributes (EA).
    For FFU, this command applies a full flash update (.ffu) image to a specified drive. It doesn’t support applying an image from a virtual hard disk (.vhdx) file, though you can use this command to apply a full image to a VHD. FFU applies to Windows 10 only.
    This option doesn’t support applying an image from a virtual hard disk (VHD), though you can use this command to apply images to a .vhdx file that's been attached, partitioned, and formatted.
     
    cereberus, Jun 7, 2020
    #2
  3. BETOLP
    BetoLP Win User
    Windows doesn`t start. Authomatic repair doesn`t work.

    Thanks again!!

    I`m sorry I had not noticed that the text on the picture was in spanish. It says that windows has replaced some damaged clusters in "name" file and "directory". Then, at the end "an unspecified error occurred (75736e6a726e6c2e 4f6)".

    I`ll do it and I`ll be updating this thread when I have the report.

    - - - Updated - - -

    I ran SeaTools. These are the results:

    DISM /split-ffu option doesn't work in win10 - 2004 [​IMG]


    Does it mean my HDD is useless?
     
    BetoLP, Jun 7, 2020
    #3
  4. GAVINLT
    GavinLT Win User

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

    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 /split-ffu option doesn't work in win10 - 2004 :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 /split-ffu option doesn't work in win10 - 2004 :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, Jun 7, 2020
    #4
Thema:

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

Loading...

  1. DISM /split-ffu option doesn't work in win10 - 2004 - Similar Threads - DISM split ffu

  2. 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....

  3. 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....

  4. 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....

  5. Split tunneling doesn't work.

    in Windows 10 Network and Sharing
    Split tunneling doesn't work.: I installed fully but it seems split tunneling still does not work. when I open an app that has been added as Trigger Application VPN automatically turns on but the connection from that app still does not go through the VPN connection. I test with a game, web browser, and 1...

  6. Win10 2004 Microphone doesnt work.

    in Windows 10 Drivers and Hardware
    Win10 2004 Microphone doesnt work.: Hello, i tried updating to the 2004 build today but when i do my mic stops working the pegel always shows 100% but it wont make any sound on recording or on Teamspeak and when i revert to the old build it works fine again. The headset is a Lx50 by Lioncast so not the...

  7. (Build 2004) Color profile doesn't work for a split second when opening display settings.

    in Windows 10 Ask Insider
    (Build 2004) Color profile doesn't work for a split second when opening display settings.: This ONLY happens when opening the Display settings (or Settings -> System, which the first tab will be Display), this does not happen if you don't have a custom color profile, also didn't happen in builds 1809 and 1909. PC Info: Windows 10 build 2004 (19041.329) GPU:...

  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. 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...

  10. DISM - Split install.wim file

    in Windows 10 Tutorials
    DISM - Split install.wim file: How to: DISM - Split install.wim file [img] Information Overall, Windows image size (the size of install.wim file) is growing version by version. In fact, it is slowly approaching the magical 4 GB file size limit for a FAT32 formatted USB flash drive. Especially if you...