none
dism suddently stop working the configuration registry database is corrupt 1009 RRS feed

  • Question

  • I've used dism several times to capture image to clone pc's.

    I use an external USB disk where I've created 2 partition, one that boot winpe prepared with

    MakeWinPEMedia /UFD C:\WinPE_amd64 F:

    and a second partition where WIM file are placed

    Few days ago I've started to use this

    DISM.exe /capture-ffu /imagefile=e:\WinOEM.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"Windows 10 FFU"

    and DISM.exe /apply-ffu..

    After a couple of test then capture command has stoped woking with error 1009 configuration registry database is corrupt

    I've rebuilt the boot partition on the usb disk, changed the usb disk with a new one, Tryed on different pc, Always with same resutl

    search on google without any solution

    next the dism.log content

     Any idea befor I leave DISM?

    2018-09-28 16:44:24, Info                  DISM   PID=1396 TID=1400 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2018-09-28 16:44:24, Info                  DISM   PID=1396 TID=1400 DismCore.dll version: 10.0.16299.15 - CDISMManager::FinalConstruct
    2018-09-28 16:44:24, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-09-28 16:44:24, Info                  DISM   PID=1396 TID=1400 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession
    2018-09-28 16:44:24, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2018-09-28 16:44:24, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-09-28 16:44:24, Info                  DISM   DISM Manager: PID=1396 TID=1400 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE:
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE:
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=4
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.16299.15
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /capture-ffu /imagefile=e:\WinOEM.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"Windows 10 FFU"
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Warning               DISM   DISM Provider Store: PID=1396 TID=1400 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-09-28 16:44:24, Warning               DISM   DISM Provider Store: PID=1396 TID=1400 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2018-09-28 16:44:24, Info                  DISM   DISM FFU Provider: Drive path = \\.\PhysicalDrive0
    2018-09-28 16:44:24, Info                  DISM   DISM FFU Provider:   Disk size = 128035676160 Bytes (119.24 Gb)
    2018-09-28 16:44:24, Info                  DISM   DISM FFU Provider: Partition style = 1 (0: MBR, 1: GPT, 2: RAW)
    2018-09-28 16:44:24, Info                  DISM   DISM FFU Provider: Partition count = 4
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: COfflineHiveT<class CEmptyType>::Init#572 failed with 0x0.
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: CWindowsOsHelper::GetOsInformation#194 failed with 0x800703f1.
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: CDiskReaderT<class CEmptyType>::PopulateCatalogs#305 failed with 0x800703f1.
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: FfuCaptureInternal#494 failed with 0x800703f1.
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: FfuCaptureImage#114 failed with 0x800703f1.
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: PID=1396 TID=1400 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:787 - CFfuManager::Capture(hr:0x800703f1)
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: PID=1396 TID=1400 Failed to capture an FFU image from '\\.\PhysicalDrive0'. - CFfuManager::InternalCmdCapture(hr:0x800703f1)
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: PID=1396 TID=1400 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x800703f1)
    2018-09-28 16:44:26, Error                 DISM   DISM FFU Provider: PID=1396 TID=1400 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:227 - CFfuManager::ExecuteCmdLine(hr:0x800703f1)
    2018-09-28 16:44:26, Error                 DISM   DISM.EXE: FfuManager processed the command line but failed. HRESULT=800703F1
    2018-09-28 16:44:26, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2018-09-28 16:44:26, Info                  DISM   DISM.EXE:
    2018-09-28 16:44:26, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2018-09-28 16:44:26, Info                  DISM   DISM.EXE:
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2018-09-28 16:44:26, Info                  DISM   DISM Provider Store: PID=1396 TID=1400 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    alex

    Friday, September 28, 2018 3:02 PM

All replies

  • Sunday, September 30, 2018 7:33 AM
  • The computer is still using Windows 10 1709.

    These were the error codes:

    0x8007007e The specified module could not be found.

    0x800703f1 The configuration registry database is corrupt.

    You can attempt an in place upgrade repair with the identical iso or with a Windows 1803 iso.

    https://www.microsoft.com/en-us/software-download/windows10

    https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

    .

    .

    .

    Please remember to vote and to mark the replies as answers if they help.

    .

    .

    .

    Sunday, September 30, 2018 8:37 AM
  • Not so clear to me.

    Which computer is running win 1709?

    The error is generated inside the winpe environment ( I boot from a usb disk,  disk x) and its' happens with any pc I try to get the image from, I've tryed even with a new w10 1 fresh installed.

    So I belive run System File Checker tool on the pc has no effect

    I' dont' understand where I shoud do the in place upgrade, all pc has

    I suppose the problem is inside the winpe environment and not the pc I try to get the image from.

    Or do you mean the "Windows assessment deplymnet kit" must be reinstalled or upgraded  and the bebuilt the winpe?


    alex

    Monday, October 1, 2018 8:32 AM
  • On one of my computers there was a corrupt operating system by scannow, a corrupt component store by restorehealth and numerous other operating system problems.  Failure to boot without additional steps  This also included failure of the in place upgrade repair and failure to upgrade.  There were numerous problems with this PC.

    At this moment I was able to fix multiple problems fixing free space requirements, changing settings in the bios, etc.  An in place upgrade repair was able to fix the scannow and restorehealth corruption.  The start menu had not worked and is working.  There were problems with the boot and now the computer boots.

    Currently I just freed up needed space in the EFI partition.  A second in place upgrade repair is now being performed.  The first in place upgrade repair was 1703 to 1703 with the identical iso.  The second in place upgrade repair is with a Windows 1803 iso.  It found sufficient space and now displays ready to install.  It will keep personal files.  It displayed installing windows 10.  Your PC will restart several times.  This might take a while.  There is a % counter.

    The second in place upgrade failed displaying a new error code.  There was a problem with the computer reading the iso on the flash drive.  The computer was rebooted.  The flash drive was inserted after the reboot.  File explorer was opened and setup was launched.  It now displays installing Windows at 5%.

    Troubleshooting can be tedious or easy.  You may not know what is ahead if there is operating system or registry corruption.  It may take time.  Worst case scenario is to clean install after backing up all files.

    Form the txt that was posted:  2018-09-28 16:44:24, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.16299.15

    16299 is Windows 1709.

    Consider an in place upgrade repair using an identical windows build iso or a windows 10 1803 iso.

    For any failed iso repair the logs can be troubleshooted.
    Monday, October 1, 2018 9:27 AM
  • Hi Alex,

    Please not that starting with Windows 10, version 1709, DISM has the ability to capture, deploy, and service FFUs, with the following limitations:

    • The drive that an FFU is applied to has to be the same or larger than the drive it is captured from
    • FFU captures of encrypted disks are not supported
    • Captures of disks that have Volume Shadow Copy Service (VSS) enabled are not supported
    • Splitting compressed FFUs is not supported

    Then follow this guide to check your operation:

    Windows FFU image – Faster capture & deployment

    https://win10.guru/windows-ffu-image-faster-capture-deployment/

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 1, 2018 10:19 AM
    Moderator
  • The Os I am running DISM IS NOT Windows 10 BUT WINPE so, as this OS in mounted during boot from the usb disk, I suppose I cannot run any fix on it. Also all other PC I am using are fine, the last I've tryed to get the image from, was installed few hours before , and was still not working.

    alex

    Monday, October 1, 2018 12:07 PM
  • FFU capture has worked fine a couple of time befort it stopped to word, withouth any changes

    disk as not encrypetd, I did not split FFU, just capture


    alex

    Monday, October 1, 2018 12:12 PM
  • I've reinstalled the last ADK on a new pc, create new win pe partition on a new usb disk and run FFU carture.

    SAme results even if the os version is newer (Dism.exe version: 10.0.17134.1)

    2018-10-02 15:18:47, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2018-10-02 15:18:47, Info                  DISM   DISM.EXE:
    2018-10-02 15:18:47, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2018-10-02 15:18:47, Info                  DISM   DISM.EXE:
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:18:47, Info                  DISM   DISM Provider Store: PID=1484 TID=1488 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:21, Info                  DISM   PID=1476 TID=700 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2018-10-02 15:19:21, Info                  DISM   PID=1476 TID=700 DismCore.dll version: 10.0.17134.1 - CDISMManager::FinalConstruct
    2018-10-02 15:19:21, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-10-02 15:19:21, Info                  DISM   PID=1476 TID=700 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession
    2018-10-02 15:19:21, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2018-10-02 15:19:21, Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
    2018-10-02 15:19:21, Info                  DISM   DISM Manager: PID=1476 TID=700 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE:
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE:
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.17134, Running architecture=amd64, Number of processors=4
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17134.1
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /capture-ffu /imagefile=e:\WinOEM.ffu /capturedrive=\\.\PhysicalDrive0 /name:disk0 /description:"Windows 10 FFU"
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Warning               DISM   DISM Provider Store: PID=1476 TID=700 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2018-10-02 15:19:21, Warning               DISM   DISM Provider Store: PID=1476 TID=700 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: FfuManager.
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2018-10-02 15:19:21, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2018-10-02 15:19:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2018-10-02 15:19:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2018-10-02 15:19:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2018-10-02 15:19:22, Info                  DISM   DISM FFU Provider: Drive path = \\.\PhysicalDrive0
    2018-10-02 15:19:22, Info                  DISM   DISM FFU Provider:   Disk size = 128035676160 Bytes (119.24 Gb)
    2018-10-02 15:19:22, Info                  DISM   DISM FFU Provider: Partition style = 1 (0: MBR, 1: GPT, 2: RAW)
    2018-10-02 15:19:22, Info                  DISM   DISM FFU Provider: Partition count = 4
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: COfflineHiveT<class CEmptyType>::Init#572 failed with 0x0.
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: CWindowsOsHelper::GetOsInformation#194 failed with 0x800703f1.
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: CDiskReaderT<class CEmptyType>::PopulateCatalogs#305 failed with 0x800703f1.
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: FfuCaptureInternal#494 failed with 0x800703f1.
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: FfuCaptureImage#114 failed with 0x800703f1.
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: PID=1476 TID=700 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:787 - CFfuManager::Capture(hr:0x800703f1)
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: PID=1476 TID=700 Failed to capture an FFU image from '\\.\PhysicalDrive0'. - CFfuManager::InternalCmdCapture(hr:0x800703f1)
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: PID=1476 TID=700 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x800703f1)
    2018-10-02 15:19:23, Error                 DISM   DISM FFU Provider: PID=1476 TID=700 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:227 - CFfuManager::ExecuteCmdLine(hr:0x800703f1)
    2018-10-02 15:19:23, Error                 DISM   DISM.EXE: FfuManager processed the command line but failed. HRESULT=800703F1
    2018-10-02 15:19:23, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2018-10-02 15:19:23, Info                  DISM   DISM.EXE:
    2018-10-02 15:19:23, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2018-10-02 15:19:23, Info                  DISM   DISM.EXE:
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2018-10-02 15:19:23, Info                  DISM   DISM Provider Store: PID=1476 TID=700 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    alex

    Tuesday, October 2, 2018 1:28 PM
  • Same exact issue.  

    I created an Image fine.  I then went to change couple of things and now I can not capture an image 

    The configuration registry database is corrupt

    Did you find a solution Alex?

    Wednesday, October 31, 2018 5:13 PM
  • No, any solution. I've tryed many things without solution.

    Installed a fresh new pc (to get the image from)

    installed the last ADK on a new pc

    prepared a new usb disk (even the disk was new) with ADK and winpe

    Always not working. I don't understand what corrupted registry database the error refer to.

    At the end I switched to Acronis to clone

    Lost a lot of time.. very bad result


    alex

    Friday, November 2, 2018 6:05 PM
  • This seems not to be problem with PE, it looks it is a problem with machines I'm capturing. I have been capturing Windows 10 Pro and IoT, I have managed to capture both but some computers will generate the same error 1009. Weird thing is that with one specific computer I was getting Error 1009, but I kept trying and finally I was able to capture FFU image. I really don't know what happened. 

    Tuesday, March 5, 2019 9:07 AM
  • This error is caused by two things:

    1. There is corruption in the source machine.

    2. There is corruption in the captured image.

    Typically the first thing I would run is to change SATA cables or capture the image from a different system. Verify no issues with the disk itself with chkdsk or the vendor specific disk tools. If the source is sound, then determine what could be the cause of corruption when making the image.

    I have only seen this message on sources with bad hard disks, or when trying to use DISM to capture a live system due to a scenario where appropriate imaging software (such as Ghost or Acronis) cannot be used for whatever reason. Aside from bad disk/sata cable issues, it is usually in relation to the image size and the amount of RAM on the client machine, or I only see it when the WIM is very large (over 10 GB).

    Remember that while DISM can do full partition images, even with the FFU ability, it still was created and designed for image deployment and servicing. Not for creating full system backups or for cloning partitions of live OSes.


    • Edited by Tripredacus Wednesday, March 6, 2019 9:49 PM
    Wednesday, March 6, 2019 9:49 PM
  • I've tryed with a new pc and a fresh installation of w10, refresh the sdk on my pc and redo a new winpe installation on a new usb disk. Always same issue.

    So I dismiss to use DISM and switch to acronis


    alex

    Thursday, March 7, 2019 1:40 PM
  • I had the same issue, and the comments on the linked guide page gave me the solution: A commenter noted that only a sysprepped and generalized Windows can be captured as FFU. I had the same error message as the OP, and the error was gone after calling "c:\windows\system32\sysprep\Sysprep /generalize /oobe /shutdown" on the system for which I want to create the image.

    Tuesday, September 17, 2019 8:05 AM