Just for fun, what happens when you set the setup.exe compression level to, say, "Fast". This will generate a different binary contents. Perhaps the file (or a magic combination of bytes in this file) triggers a file-lock (false-positive).

Can you reproduce this on your machine? Are you using the latest SB build? Is the setup.exe (and SS.EXE) code-signed?