Seth,

unfortunately, reviewing the source code in your .sbi does not help in this case. But the "sbevents" log is interesting.

Error #99 comes up if the next install file (decompression) action can't be executed because the decompression library was unable to find the "magic sign" of the next file. The magic sign is the archive header of the next file to be decompressed and includes the name of the file, original file size, date/time stamp, CRC-32 code). If Error #99 is returned from the LSPack decompression then the magic sign was not there.

This might happen if:

1. An installation action is executed multiple times (99%)

2. The archive is tampered (e.g. transmission error or false-positive from a protection software)

3. The file is > 2GB

In your "sbevents" log I see multiple installation actions for your "deltaCompression.log" file:

|08/26/2021|13:17:41.032|Install file: C:\Users\edtadmin\AppData\Local\Temp\b60e1f40-0670-11ec-4823-001ce5d30029\deltapackage\\deltaCompression.log

|08/26/2021|13:18:53.596|Err01: 99 - File: C:\Users\edtadmin\AppData\Local\Temp\b60e1f40-0670-11ec-4823-001ce5d30029\PlugInFiles\\deltaCompression.log

If you did not include this file TWICE in your project then it comes from the SAME "Install File(s)..." action and the 2nd call returns Error #99 (IMO).

Or did you add "deltaCompression.log" twice? If yes, you should see this file multiple times in your compiler HTML.

Friedrich