Windows 10: DISM /capture-ffu getting error 112

Discus and support DISM /capture-ffu getting error 112 in Windows 10 Gaming to solve the problem; 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... Discussion in 'Windows 10 Gaming' started by Paul Dellisanti, Jul 12, 2022.

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

    :)
     
    Paul Dellisanti, Jul 12, 2022
    #1

  2. FFU image application fails with error 0x80070057

    I'm attempting to apply an FFU image that I captured from an identical computer.

    The platform is an embedded computer based on the Intel Atom Bay Trail processor.

    The BIOS is UEFI.

    The OS is Windows 10 Pro 1909.

    The drive being captured and applied to is a SATA solid state drive.

    There are five partitions being captured: the Windows partition, and empty data partition (both formatted NTFS) and the three additional partitions created by Windows Setup for a UEFI-based system.

    The drive being applied to is clean, unformatted.

    Deployment Image Servicing and Management tools version: 10.0.18362.1.

    Command line used to capture:

    Code:
    dism /capture-ffu /imagefile=<imagefile_pathname> /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"Image File"
    Command line used to apply:dism /apply-ffu /imagefile=<imagefile_pathname> /applydrive:\\.\PhysicalDrive0
    These command lines were based on the samples on the Microsoft page
    Capture and apply Windows Full Flash Update (FFU) images. I have since noticed that the documentation specifies colons in place of the equal signs. I am going to try the procedure now with colons but I want to get this question posted now. I will update
    with any developments.

    The on-screen error referenced error number 87 (0x57) and suggested verifying the command line and checking the log file. Here are the error lines from the log file:

    Code:
    Error    DISM   DISM FFU Provider: CFfuHash::CheckHashes#94 failed with 0x80070057.Error    DISM   DISM FFU Provider: CFilteredTransport::Read#94 failed with 0x80070057.Error    DISM   DISM FFU Provider: CFilteredTransport::SkipPadding#144 failed with 0x80070057.Error    DISM   DISM FFU Provider: CFfuReader::ReadStoreHeader#866 failed with 0x80070057.Error    DISM   DISM FFU Provider: CFfuReader::InitializeFfuHeaders#498 failed with 0x80070057.Error    DISM   DISM FFU Provider: CFfuReader::CreateInstance#50 failed with 0x80070057.Error    DISM   DISM FFU Provider: FfuApplyInternal#605 failed with 0x80070057.Error    DISM   DISM FFU Provider: FfuApplyImage#51 failed with 0x80070057.Error    DISM   DISM FFU Provider: PID=1760 TID=1764 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:514 - CFfuManager::Apply(hr:0x80070057)Error    DISM   DISM FFU Provider: PID=1760 TID=1764 Failed to apply an FFU image to '\\.\PhysicalDrive0'. - CFfuManager::InternalCmdApply(hr:0x80070057)Error    DISM   DISM FFU Provider: PID=1760 TID=1764 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x80070057)Error    DISM   DISM FFU Provider: PID=1760 TID=1764 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:227 - CFfuManager::ExecuteCmdLine(hr:0x80070057)Error    DISM   DISM.EXE: FfuManager processed the command line but failed. HRESULT=80070057
    This block of errors appears twice in the log file with only the times (snipped from the above) and the process and thread IDs differing.

    Thanks for reading. If you need additional info, just ask.
     
    DaveColter, Jul 12, 2022
    #2
  3. 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, Jul 12, 2022
    #3
  4. GavinLT Win User

    DISM /capture-ffu getting error 112

    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 /capture-ffu getting error 112 :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 /capture-ffu getting error 112 :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, Jul 12, 2022
    #4
Thema:

DISM /capture-ffu getting error 112

Loading...
  1. DISM /capture-ffu getting error 112 - Similar Threads - DISM capture ffu

  2. DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...

    in Windows 10 Gaming
    DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...: Doing this wrong somehow. Need help.Using the latest ADK/PE iso, booted into my iso on VM.DISM /capture-ffu /imagefile=F:\TEST_20240610_Win10642021_qC.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0comes back error 112....
  3. DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...

    in Windows 10 Software and Apps
    DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...: Doing this wrong somehow. Need help.Using the latest ADK/PE iso, booted into my iso on VM.DISM /capture-ffu /imagefile=F:\TEST_20240610_Win10642021_qC.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0comes back error 112....
  4. DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...

    in Windows 10 Installation and Upgrade
    DISM /capture-ffu on Hyper-v. Getting error 112 not enough disk space when there is way...: Doing this wrong somehow. Need help.Using the latest ADK/PE iso, booted into my iso on VM.DISM /capture-ffu /imagefile=F:\TEST_20240610_Win10642021_qC.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0comes back error 112....
  5. Hyper-V DISM Error 112 There is not enough space on the Disk

    in Windows 10 Gaming
    Hyper-V DISM Error 112 There is not enough space on the Disk: Hello all,I've tried looking around the forum for resolving this issue but am coming up short. I have a Hyper-V Instance of Windows 11 Pro Unactivated that I've prepared and sysprepped for mass deployment.I load the winPE environment into the CD/DVD slot of the Hyper-V and...
  6. Hyper-V DISM Error 112 There is not enough space on the Disk

    in Windows 10 Software and Apps
    Hyper-V DISM Error 112 There is not enough space on the Disk: Hello all,I've tried looking around the forum for resolving this issue but am coming up short. I have a Hyper-V Instance of Windows 11 Pro Unactivated that I've prepared and sysprepped for mass deployment.I load the winPE environment into the CD/DVD slot of the Hyper-V and...
  7. 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....
  8. 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....
  9. 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...
  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...