The bundled files are built into the installer itself when it’s initially built by us. They get extracted to a temp directory and then moved to the installation directory instead of being moved from the repository itself.
As for the ‘All Users’ option failing, an installer log should show us what’s going wrong. So if it’s possible could you get me one that’s failing for you?
Our client installer creates an installation log in the system’s temporary directory. On Linux and Mac OS X, this typically means the
/tmp directory. On Windows, the log will be created in the user’s local temp directory, usually
C:\Documents and Settings\%USERNAME%\Local Settings\Temp. The default name of the generated log file is bitrock_installer.log, but if the file already exists from a previous installation, the installer will try to create an unique filename trying bitrock_installer_[pid].log and bitrock_installer_[pid]_[uid].log where [pid] is the PID of the process and [uid] is an unique identifier. On Linux, if the
/tmp directory is not writable, it will attempt to use