Forum Discussion
Using FFU Imaging; after Optimize-FFU it no longer works
Sadness.... I found this issue on 2/7/2023 after I optimized an ffu from a Win8 device. I optimized in the event I needed to restore to a smaller (500GB SSD) vs the barely used (1TB hdd). I mounted the ffu and it failed. I navigated to the temp folder and found the temp VHD that is created. It mounted without issue but, the logs complained that it couldn't delete that VHD 😞
My error was : hr:0x8000ffff
2023-02-08 12:21:15, Error DISM DISM FFU Provider: More than 1 recovery partitions found.
2023-02-08 12:21:15, Error DISM DISM FFU Provider: FfuApplyInternal#546 failed with 0x8000ffff.
2023-02-08 12:21:15, Error DISM DISM FFU Provider: FfuMountInternal#242 failed with 0x8000ffff.
2023-02-08 12:21:27, Warning DISM DISM FFU Provider: Failed to delete backing VHD/X file C:\Users\<removed>\AppData\Local\Temp\_ffumount50289394.vhd (0x80070020).
2023-02-08 12:21:27, Error DISM DISM FFU Provider: FfuMountImage#163 failed with 0x8000ffff.
2023-02-08 12:21:27, Error DISM DISM FFU Provider: PID=9932 TID=6036 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffuimageinfo.cpp:347 - CFfuImageInfo::Mount(hr:0x8000ffff)
2023-02-08 12:21:28, Error DISM DISM Imaging Provider: PID=9932 TID=6036 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:832 - CGenericImagingManager::InternalOpMount(hr:0x8000ffff)
2023-02-08 12:21:28, Error DISM DISM Imaging Provider: PID=9932 TID=6036 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:745 - CGenericImagingManager::InternalCmdMount(hr:0x8000ffff)
2023-02-08 12:21:28, Error DISM DISM Imaging Provider: PID=9932 TID=6036 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:537 - CGenericImagingManager::ExecuteCmdLine(hr:0x8000ffff)😞
Luckily, the original machine isn't wiped yet (attempting win10 upgrade)
Hi,
sorry for my poor english, but i confirm your answer.
Dism /optimize use the directory %USERPROFILE%\AppData\Local\Temp and mount a temporary file _ffumountxxxxxxxxx.vhd, so you must have the capacity disk to perform this command correctly !.
Sometime, there is an echec and this ffu file is locked by another process, you can reboot your machine to release the handle and check, you must check registry for an eventual persist variable.
I have another post at this link for more details:
https://learn.microsoft.com/en-us/answers/questions/540448/using-ffu-imaging-after-optimize-ffu-it-no-longer
Thanks and regards
hi,
just for information on dism.log:
DISM DISM FFU Provider: Session Registry Path has already been used.
DISM DISM FFU Provider: FfuMountImage#206 failed with 0x800700b7.
DISM DISM FFU Provider: Successfully written the session info to HKEY\SOFTWARE\Microsoft\DISM\Mounted FFUs\
Thanks and regards.
