A USB deployment of a WIM image captured in version 4.0 fails during deployment
Here's an example of a failure from the deployment log:
2017-02-08 13:47:32-0800 [error] wimImage->DeployImage(Default, Default) [image=H:\KACE\hashstore\94DB983A837FB46A38AB1C4CDD2D0.10378]
2017-02-08 13:47:32-0800 [info] Deploy Image - Start
2017-02-08 13:47:32-0800 [info] ...Creating temp dir: [H:\K2_2017-02-08_13-47-32]
2017-02-08 13:47:32-0800 [info] ...Deploy Directory: H:\KACE\hashstore\
2017-02-08 13:47:32-0800 [info] ...Image File: 94DB983A837FB46A38AB1C4CDD2D0.10378
2017-02-08 13:47:32-0800 [info] ...Image Dir: H:\KACE\hashstore\
2017-02-08 13:47:32-0800 [info] ...Temp Directory: H:\K2_2017-02-08_13-47-32
2017-02-08 13:47:32-0800 [error] ...Cannot open .wim file: The system cannot find the file specified.
The wim manifest file is listing the manifest file itself.
This causes a USB deployment to fail as it is trying to deploy s.wim.manifest as a wim
Resolved in 5.0 and higher.
For 4.x please see workaround below:
This is an example of what has to be removed from the manifest:
This is an example of what file would have to be deleted in the
Note that the file isn't named md5