Recent Excel releases offer two versions: 32-bit or 64-bit. Learn more about Office 32-bit and 64-bit versions

If your end users have Office 64-bit, you must provide them with a 64-bit executable file. XLS Padlock can generate 64-bit .exe files.

This option is for standalone executable files only.

Choose what type of EXE XLS Padlock will generate when creating your secure application:

32-bit only: XLS Padlock generates an EXE file for Excel 32-bit versions.

64-bit only: XLS Padlock generates an EXE file for Excel 64-bit versions.

Universal: XLS Padlock creates a single EXE file for both Excel 32-bit and 64-bit versions. Thus, you do not have to manage and deliver two separate EXE files to your customers. The other side of the coin is a clear increase of the EXE file size: the EXE will double in size because we merge 32-bit and 64-bit code into one EXE.

32-bit and 64-bit: XLS Padlock generates two separate EXE files. When you hit “Build Secure Application”, XLS Padlock first makes an EXE for Excel 32-bit versions and then an EXE for 64-bit versions at once. To prevent EXE files from overwriting themselves, XLS Padlock automatically adds “32” and “64” suffixes to the Output path. For instance, “My App.exe” will result in “My App32.exe” and “My App64.exe”.



If end users run a 64-bit .EXE file with a 32-bit Office installation (and vice-versa), an error message will be displayed, asking end users to contact you for a correct EXE version.



We strongly recommend you to code sign your application EXE file if you use the Universal mode, because a temporary EXE file will be created at runtime and some antivirus dislike this behavior. Code signing will definitively help to lower false positives.



By default, applications distributed in the bundle format are already Universal.

Configure Advanced Options