DISM - Clone and Deploy using FFU Image  

Page 7 of 7 FirstFirst ... 567

  1. AdamNYC31
    Posts : 6
    Window 10
       New #60

    I restarted the system but no change. In the screenshot below you can see I successfully applied the image called OOBE.ffu. I then ran the dism /optimize command from the Windows 10 machine that has SSD for the shared network folder where the FFU file is saved. (See screenshot) the optimization completes successfully. Then on the target machine, I attempt to apply this 'optimized' image and it outright fails. The only change is this 'optimize' command. I can't see what I'm missing.

    DISM - Clone and Deploy using FFU Image-img_3389.jpg

    DISM - Clone and Deploy using FFU Image-img_3388.jpg
      My Computer
    Quote Quote

  3. Railtech
    Posts : 494
    Win 10 Pro x64 versions
       New #61

    So are you attempting to Optimize the image on the same disk as you captured the ffu image? This will not work if you are. You must copy the ffu image to a technician PC then run the optimize command on the image there.
    Copy the FFU file to a technician PC running Windows 10, version 1903 or later. You can't run /optimize-ffu on the same disk as the captured FFU.
      My Computer
    Quote Quote

  4. AdamNYC31
    Posts : 6
    Window 10
       New #62

    To clarify; I'm capturing the reference computer FFU image to a network share which is a completely separate 'technician' PC that is running Windows Server 2019. That screenshot where I am running the 'optimize' command is from the 'technician' PC with Server 2019 running. I am not using the reference PC to do the 'optimization'.

    My only other thought is that when I do a clean install using the Window 10 USB a recovery partition of 508MB is created as the last partition. Is it ok if the reference image contains this partition like below? Perhaps, that is causing the issue?

    DISM - Clone and Deploy using FFU Image-img_3390.jpg
      My Computer
    Quote Quote

  5. Railtech
    Posts : 494
    Win 10 Pro x64 versions
       New #63

    Is your ADK package you are using 1903 or later? I think the 508MB recovery partition is fine.
      My Computer
    Quote Quote

  7. AdamNYC31
    Posts : 6
    Window 10
       New #64

    Yes. I downloaded these two yesterday:

    Windows ADK for Windows 10, version 2004
    This ADK supports Windows 10, version 2004; Windows 10, version 20H2; and Windows 10, version 21H1.

    and

    Windows PE add-on for the ADK, version 2004
    Windows Preinstallation Environment (PE) for Windows 10, version 2004
      My Computer
    Quote Quote

  8. Railtech
    Posts : 494
    Win 10 Pro x64 versions
       New #65

    Hmm, I must admit I have not used the Optimize option with FFU so just trying to eliminate unknown factors. One last thing, did you check if your image would actually fit on the target:

    Dism /Get-ImageInfo /ImageFile:flash.ffu
      My Computer
    Quote Quote

  9. AdamNYC31
    Posts : 6
    Window 10
       New #66

    Yes; the image size is only about 12GB and the destination is 128GB.

    The non-optimized image works but since it was captured on a 128GB machine all the deployments are partitioned exactly as 128GB, then 508MB recovery, and then the rest of the space is unused. It's annoying as I can even even 'extend' the volume to make one large drive as the 508MB recovery partition is in the middle of them. Either way, for this to work properly it needs to auto-resize to use all the available space which as I understand it is the main purpose of the 'optimize' function. I just can't see what the issue is; I feel like I'm following the MS docs to the letter.
      My Computer
    Quote Quote

  10. Railtech
    Posts : 494
    Win 10 Pro x64 versions
       New #67

    Well, I think I would Use the scripts found on the linked page below and not include the recovery partition as outlined in the script titled:
    CreatePartitions-UEFI-FFU.txt or CreatePartitions-BIOS-FFU.txt     as appropriate.

    Next Apply your optimized image as you did previously. Once you have that done you can shrink the Windows partition and run the script titled:
    CreateRecoveryPartitions-UEFI.txt or CreateRecoveryPartitions-BIOS.txt as appropriate adjust minimum size as necessary.

    After the above you will need to run the script titled:
    ApplyRecovery.bat followed by the scripts:
    HideRecoveryPartitions-UEFI.txt or HideRecoveryPartitions-BIOS.txt as appropriate.

    At the top of the linked page you will find a link to download the scripts which is recommended over using copy and paste.
    https://docs.microsoft.com/en-us/win...xs#apply-image
      My Computer
    Quote Quote

  11. brentonv
    Posts : 1
    Windows 10
       New #68

    DISM/FFU Tests


    I wanted to script a backup/restore option into Windows setup and had trouble finding any information about DISM/FFU limitations, so I used a few scripts to automate collecting the data below which will hopefully make things a little less ambiguous for others. Testing was done using VirtualBox 7.0.2 with an initial test run for each sequence performed to assign drive space on the host system prior to collecting any data, and the host system was kept idle during all test sequences so the results should be fairly consistent. Enjoy!


    Table 1: DISM/FFU WinOS Capture/Apply Tests

    OS/Version/Type:   Win10 1703 ADK\Deployment Tools\DISM Version: 10.0.15063.0   Win10 1709 ADK\Deployment Tools\DISM Version: 10.0.16299.15   Win10 1803 ADK\Deployment Tools\DISM Version: 10.0.17134.1   Win10 1809 ADK\Deployment Tools\DISM Version: 10.0.17763.1   Win10 1903 ADK\Deployment Tools\DISM Version: 10.0.18362.1   Win10 2004 ADK\Deployment Tools\DISM Version: 10.0.19041.1   Server2022 ADK\Deployment Tools\DISM Version: 10.0.20348.1   Win11 ADK\Deployment Tools\DISM Version: 10.0.22000.1   Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1
    Win7 7601 MBR/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported
    Disk Used: 17.88 GB Disk Used: 17.88 GB Disk Used: 17.88 GB
    FFU Capture: 03m:57.71s FFU Capture: 03m:31.94s FFU Capture: 03m:41.66s
    FFU Apply: 10m:34.88s FFU Apply: 10m:35.44s FFU Apply: 10m:34.41s
    FFU Size: 17.89 GB FFU Size: 17.89 GB FFU Size: 17.89 GB
    Win8.1 9600 MBR/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported
    Disk Used: 09.39 GB Disk Used: 09.39 GB Disk Used: 09.39 GB
    FFU Capture: 01m:55.46s FFU Capture: 01m:56.39s FFU Capture: 01m:55.44s
    FFU Apply: 06m:06.42s FFU Apply: 06m:03.86s FFU Apply: 06m:03.11s
    FFU Size: 09.63 GB FFU Size: 09.63 GB FFU Size: 09.63 GB
    Win8.1 9600 GPT/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully
    Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB Disk Used: 09.63 GB
    FFU Capture: 01m:57.54s FFU Capture: 01m:55.17s FFU Capture: 01m:58.46s FFU Capture: 02m:00.61s FFU Capture: 01m:54.97s FFU Capture: 01m:58.07s FFU Capture: 01m:56.41s FFU Capture: 01m:56.78s
    FFU Apply: 06m:03.07s FFU Apply: 06m:01.04s FFU Apply: 06m:00.86s FFU Apply: 06m:04.97s FFU Apply: 06m:00.82s FFU Apply: 06m:03.36s FFU Apply: 06m:00.49s FFU Apply: 06m:01.03s
    FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB FFU Size: 09.83 GB
    Win10 22H2 MBR/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported
    Disk Used: 11.34 GB Disk Used: 11.34 GB Disk Used: 11.34 GB
    FFU Capture: 02m:25.68s FFU Capture: 02m:23.71s FFU Capture: 02m:40.63s
    FFU Apply: 07m:36.38s FFU Apply: 07m:36.86s FFU Apply: 07m:36.11s
    FFU Size: 11.78 GB FFU Size: 11.78 GB FFU Size: 11.78 GB
    *Win10 22H2 GPT/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully
    Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB Disk Used: 11.25 GB
    FFU Capture: 02m:24.45s FFU Capture: 02m:21.55s FFU Capture: 02m:39.80s FFU Capture: 10m:24.51s FFU Capture: 11m:43.28s FFU Capture: 11m:30.19s FFU Capture: 11m:06.26s FFU Capture: 12m:23.72s
    FFU Apply: 07m:33.31s FFU Apply: 07m:42.83s FFU Apply: 07m:52.50s FFU Apply: 15m:33.70s FFU Apply: 17m:00.45s FFU Apply: 17m:16.33s FFU Apply: 17m:34.12s FFU Apply: 18m:35.42s
    FFU Size: 11.76 GB FFU Size: 11.76 GB FFU Size: 11.76 GB FFU Size: 49.93 GB FFU Size: 49.93 GB FFU Size: 49.93 GB FFU Size: 49.93 GB FFU Size: 49.93 GB
    Win11 22H2 MBR/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported
    Disk Used: 10.91 GB Disk Used: 10.91 GB Disk Used: 10.91 GB
    FFU Capture: 02m:37.70s FFU Capture: 02m:44.55s FFU Capture: 02m:45.72s
    FFU Apply: 07m:25.47s FFU Apply: 07m:29.62s FFU Apply: 07m:24.72s
    FFU Size: 11.46 GB FFU Size: 11.46 GB FFU Size: 11.46 GB
    Win11 22H2 GPT/NTFS: Error 87: The capture-ffu option is unknown The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully
    Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB Disk Used: 10.86 GB
    FFU Capture: 02m:35.12s FFU Capture: 02m:15.83s FFU Capture: 02m:12.94s FFU Capture: 02m:29.64s FFU Capture: 02m:21.08s FFU Capture: 02m:17.53s FFU Capture: 02m:16.68s FFU Capture: 02m:15.97s
    FFU Apply: 07m:20.30s FFU Apply: 07m:25.61s FFU Apply: 07m:20.97s FFU Apply: 07m:35.73s FFU Apply: 07m:21.71s FFU Apply: 07m:21.95s FFU Apply: 07m:19.40s FFU Apply: 07m:19.77s
    FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB FFU Size: 11.48 GB
     *Win10 GPT/NTFS Raw Issue: Capture-ffu falls back to raw copy since version 2004? 
     Caution: Raw data, full disk copy 


    Table 2: DISM/FFU OtherOS Capture/Apply Tests

    OS/Version/Type:   Win10 1703 ADK\Deployment Tools\DISM Version: 10.0.15063.0   Win10 1709 ADK\Deployment Tools\DISM Version: 10.0.16299.15   Win10 1803 ADK\Deployment Tools\DISM Version: 10.0.17134.1   Win10 1809 ADK\Deployment Tools\DISM Version: 10.0.17763.1   Win10 1903 ADK\Deployment Tools\DISM Version: 10.0.18362.1   Win10 2004 ADK\Deployment Tools\DISM Version: 10.0.19041.1   Server2022 ADK\Deployment Tools\DISM Version: 10.0.20348.1   Win11 ADK\Deployment Tools\DISM Version: 10.0.22000.1   Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1
    Ubuntu Jammy 22.04.1 MBR/EXT4: Error 87: The capture-ffu option is unknown Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported Error 50: The request is not supported
    Ubuntu Jammy 22.04.1 GPT/EXT4: Error 87: The capture-ffu option is unknown Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully
    Disk Used: 12.28 GB Disk Used: 12.28 GB Disk Used: 12.28 GB Disk Used: 12.28 GB Disk Used: 12.28 GB
    FFU Capture: 14m:52.45s FFU Capture: 14m:19.67s FFU Capture: 13m:52.45s FFU Capture: 15m:01.17s FFU Capture: 14m:41.28s
    FFU Apply: 19m:54.30s FFU Apply: 20m:05.89s FFU Apply: 20m:12.70s FFU Apply: 21m:14.06s FFU Apply: 21m:42.83s
    FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB
    MacOS Monterey 12.6.1 GPT/APFS: Error 87: The capture-ffu option is unknown Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command Error 87: An error occurred while processing the command The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully The operation completed successfully
    Disk Used: 17.09 GB Disk Used: 17.09 GB Disk Used: 17.09 GB Disk Used: 17.09 GB Disk Used: 17.09 GB
    FFU Capture: 16m:36.66s FFU Capture: 19m:41.76s FFU Capture: 18m:43.97s FFU Capture: 18m:13.83s FFU Capture: 19m:06.00s
    FFU Apply: 28m:59.11s FFU Apply: 32m:51.78s FFU Apply: 30m:04.59s FFU Apply: 31m:30.39s FFU Apply: 32m:36.62s
    FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB FFU Size: 50.02 GB
     Caution: Raw data, full disk copy 


    Table 3: DISM/FFU Win10 GPT/NTFS Raw Issue Tests

    OS/Version/Type: Windows\Logs\DISM\dism.log
    Win10 1709 GPT/NTFS: Partition style = 1 (0: MBR, 1: GPT, 2: RAW). File System = NTFS [OK]
    Win10 1803 GPT/NTFS: Partition style = 1 (0: MBR, 1: GPT, 2: RAW). File System = NTFS [OK]
    Win10 1809 GPT/NTFS: Partition style = 1 (0: MBR, 1: GPT, 2: RAW). File System = NTFS [OK]
    Win10 1903 GPT/NTFS: Partition Style = GPT. File System = NTFS [OK]
    Win10 1909 GPT/NTFS: Partition Style = GPT. File System = NTFS [OK]
    *Win10 2004 GPT/NTFS: Partition Style = GPT. File System = NTFS. Partition length is not a multiple of cluster size (4096). Failed to get NTFS allocation bitmap.
    Fall back to do a raw copy
    *Win10 20H2 GPT/NTFS: Partition Style = GPT. File System = NTFS. Partition length is not a multiple of cluster size (4096). Failed to get NTFS allocation bitmap.
    Fall back to do a raw copy
    *Win10 21H1 GPT/NTFS: Partition Style = GPT. File System = NTFS. Partition length is not a multiple of cluster size (4096). Failed to get NTFS allocation bitmap.
    Fall back to do a raw copy
    *Win10 21H2 GPT/NTFS: Partition Style = GPT. File System = NTFS. Partition length is not a multiple of cluster size (4096). Failed to get NTFS allocation bitmap.
    Fall back to do a raw copy
    *Win10 22H2 GPT/NTFS: Partition Style = GPT. File System = NTFS. Partition length is not a multiple of cluster size (4096). Failed to get NTFS allocation bitmap.
    Fall back to do a raw copy
     *Win10 GPT/NTFS Raw Issue: Capture-ffu falls back to raw copy since version 2004? 
     Caution: Raw data, full disk copy 


    Table 4: DISM/FFU Legacy ADK Capture/Apply Tests

    OS/Version/Type: DISM/FFU Capture DISM/FFU Restore Result
    Win11 22H2 MBR/NTFS: Win10 1709 ADK\Deployment Tools\DISM Version: 10.0.16299.15 Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1 The operation completed successfully
    Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1 Error 50: The request is not supported
    Win11 22H2 GPT/NTFS: Win10 1709 ADK\Deployment Tools\DISM Version: 10.0.16299.15 Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1 The operation completed successfully
    Win11 22H2 ADK\Deployment Tools\DISM Version: 10.0.22621.1 Win10 1709 ADK\Deployment Tools\DISM Version: 10.0.16299.15 The operation completed successfully
     MBR/NTFS: Capture-ffu MBR is not supported since DISM version 10.0.18362.1 


    Table 5: DISM/FFU Errors

    Error 13: The data is invalid (See Error: 113)
    Error 50: The request is not supported
    Error(s) 87: The capture-ffu option is unknown
    An error occurred while processing the command
    Error 113: There is not enough space on the disk
     Image File: Caution for raw copy, destination must be larger than capture drive 




    Edit: html version can be found here
    Last edited by brentonv; 29 Dec 2022 at 21:00.
      My Computer
    Quote Quote

  13. ATechPCS
    Posts : 1
    Windows Server 2022
       New #69

    AdamNYC31 said:
    I restarted the system but no change. In the screenshot below you can see I successfully applied the image called OOBE.ffu. I then ran the dism /optimize command from the Windows 10 machine that has SSD for the shared network folder where the FFU file is saved. (See screenshot) the optimization completes successfully. Then on the target machine, I attempt to apply this 'optimized' image and it outright fails. The only change is this 'optimize' command. I can't see what I'm missing.

    DISM - Clone and Deploy using FFU Image-img_3389.jpg

    DISM - Clone and Deploy using FFU Image-img_3388.jpg
    Adam, Did you ever figure out what the issue was? I am experiencing this same problem and you are the only one online that I can find having the same problem.
      My Computer
    Quote Quote

 

Tutorial Categories

DISM - Clone and Deploy using FFU Image Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
USB Image Clone?
in Backup and Restore

This might be a simple question for some, but I am stomped on this one. Is it possible to create an image of a PC and use that to Clone it into other PCs, same brand, same specs. We do a lot of Terminals and take it to clients. But every once...
Would appreciate your help! :confused: Have a Toshiba Satellite L655 laptop (one morning the laptop with Windows 7 upgraded itself to Windows 10). Would like to use Macrium Reflect Free to create an image of its hard drive. Have no clue whether I...
I would like to move my OS from a smaller 240gb SSD (running out of room) to a 512gb NVMe SSD. What is the better option-do I clone or image the OS and all its partitions to the NVMe? Are there any need to know pointers before I attemp it? Many...
Hi All, I've got some new DELL AIO Optiplex 3240s that are now running W10 Pro after successful clean installs. I am needing to set one up as a reference computer and then deploy that image to the rest of them. This is for the small library I...
System Disk Image/Clone
in Backup and Restore

There's been some discussion on this in another thread & having previously not been too successful in the past, I'd like to seek some advice. When a disk is cloned it makes an identical copy to another HD; the idea being that if the one in use...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 12:35.
Find Us




Windows 10 Forums