D
DaveColter
Guest
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:
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:
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.
Continue reading...
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:
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:
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.
Continue reading...