Nullsoft Scriptable Install System (NSIS) 3.13 – Windows Installer Creation Tool

The Winning Edge

Quick Start: Create Your First Professional Installer

1. Open NSIS and select File → New Script Wizard to generate a basic template.nsi file 2. Edit the Name, OutFile, and InstallDir directives to match your application 3. Add File /r commands to include your application files recursively 4. Insert !include MUI2.nsh and define MUI_PAGE_* macros for a modern wizard UI 5. Run Tools → Compile Script to build your installer.exe 6. Test the installer on a clean VM or separate machine before distribution

Reason To Do This: The wizard gets you 80% there in minutes. Using MUI2 gives you a polished, Windows 10/11-native look instantly. Testing on a clean environment catches missing dependencies and registry issues before your users do.

Optimize Installer Size with Smart Compression

1. Set SetCompressor lzma at the top of your.nsi for best overall ratio 2. Use SetCompressor /SOLID lzma for groups of similar files (DLLs, assets) to improve compression 3. Exclude already-compressed media (MP4, JPG, ZIP) with SetCompressor /FINAL zlib — they won’t shrink further 4. Enable CRC checks only where needed: CRCCheck off for speed, on for critical system files 5. Strip debug symbols from your binaries before packaging — they add bulk without user value

Reason To Do This: LZMA solid compression can reduce installer size by 30-50% over default settings. Skipping compression on pre-compressed assets saves build time. Smaller installers mean faster downloads, lower bandwidth costs, and higher conversion rates.

Silent Deployment for Enterprise Rollouts

1. Add RequestExecutionLevel admin to require elevation once 2. Implement a silent mode: check for /S flag and skip all UI pages with MUI_PAGE_CUSTOMFUNCTION_PRE 3. Write installation choices (components, paths) to the registry on first interactive install 4. On silent runs, read those saved values and apply them automatically 4. Test with: installer.exe /S /D=C:/CustomPath 5. Log results to a file for audit trails: /S /L=install.log

Reason To Do This: Enterprises deploy via SCCM, Intune, or Group Policy — they need zero-interaction installs with predictable paths and logging. Building this in once saves weeks of repackaging requests later. The /D= flag support is a NSIS superpower most installers lack.