Overwrite read-only files
Clears the “Read-Only” attribute of an existing file before attempting to overwrite it.
This page controls how the package unpacks files on the destination machine: what happens when a file already exists, how locked files are handled, and which decompression engine is used.

Displays a prompt asking the user whether to overwrite, skip, or apply the choice to all remaining files.
This is the recommended setting for standard packages.
Replaces existing files automatically without prompting.
Compares modification dates and only replaces the destination file if the packaged version is newer.
Never overwrites existing files, regardless of version or date.
Overwrite read-only files
Clears the “Read-Only” attribute of an existing file before attempting to overwrite it.
Replace locked files at startup
If a file cannot be replaced because it is in use, the package queues the replacement for the next Windows reboot. The %NEEDREBOOT% variable is set to 1 if a reboot is required. Requires Administrative Privileges.
Paquet Builder includes two high-performance engines based on 7-Zip technology:
| Engine | Characteristics |
|---|---|
| Small Engine | Optimized for size. Supports LZMA/LZMA2 and BCJ2. No encryption. Requires enough RAM to hold the largest single file (avoid for files > 256 MB). |
| Full Engine | Supports AES-256 encryption and multi-threaded decompression. Writes directly to disk — ideal for very large files. |
| Automatic | (Recommended) Paquet Builder selects the best engine based on your project settings. The choice is logged in the compilation log. |