USB Deployment fails with error there are too many files in the Hashstore (226991)

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:

1. Go into the USB drive and navigate to KACE > hashstore > images and open the ID.manifest file
2. Search the manifest for entries that refer to a path with 'wim.manifest':
   e.g. path: C:\K2_2017-02-08_21-01-42\C.wim.manifest
3. Make a note of the size: and md5: lines for that entry, since the file referenced in the entry is renamed to reflect the md5 checksum and size
4. Remove the entry from the file starting with the fields: line and ending with the size: line
5. Repeat for any other wim.manifest entries
6. Save the file
7. Delete the files on the USB drive located in KACE > hashstore that correspond to the entries that were removed from the manifest.

This is an example of what has to be removed from the manifest:

fields: 10
acl: O:WDG:WDD:NO_ACCESS_CONTROL
atime: 131311872000000000
ctime: 131312438155100000
kind: file
md5: B1B48A8901B32565F8E5699BC0E34402
mtime: 131312438160000000
path: S:\K2_2017-02-10_15-43-35\S.wim.manifest
security: A
short_name: SWIM~1.MAN
size: 290

This is an example of what file would have to be deleted in the usb:\KACE\hashstore directory, based on the above manifest entry:

48A8901B32565F8E5699BC0E34402.290

Note that the file isn't named md5.size, the first 3 characters of the md5 are trimmed off