Thanks for the extra detail. The antivirus and virtual machine questions were a guess, and they do not hold: this particular failure does not come from a security product. The message Hash must be initialized is raised by the third party compression component that the current release uses for one specific case, large files.
The workaround is available today and needs no new build from us. In the File Manager, sort the file list by size and select everything above roughly 800 KB. Open the file properties for that selection and tick "Do not compress the selected file(s) (only stored)". The only consequence is a larger publication, since they are stored rather than compressed. While you are there, check that "Use streaming-compatible compression method" is not ticked on any file, as it forces the same path regardless of size.
One thing not to waste time on: the build log does not name the file that failed. The per file size list is written only after compression succeeds, which is why the log stops right after "File List:" with nothing under it. Sorting by size is the quicker route.
On our side this is already dealt with. That component has been taken out of the build path in HTML Executable 2026, which is coming very soon. It also carries a large set of new features. Until it ships, the stored setting above is the way through, and the only price you pay for it is publication size.
