Step-by-Step: Building an nLite Addon for Revo Uninstaller

Step-by-Step: Building an nLite Addon for Revo Uninstaller

Overview

This guide shows how to create an nLite addon that integrates Revo Uninstaller into a Windows installation so the uninstaller is present after setup. Assumes Revo Uninstaller Portable or an installer that supports silent installation. Targets nLite-compatible Windows versions (XP/2003-era); adjust for your target OS.

What you’ll need

  • nLite installed on a Windows machine
  • Revo Uninstaller installer (preferably portable or with silent install switches)
  • A working Windows installation source (folder or ISO)
  • 7-Zip or similar for extracting installers (optional)
  • A text editor (Notepad++)
  • Basic familiarity with batch scripting and INF format

Steps

  1. Prepare files
  • Create a folder for the addon, e.g., Addon_Revo.
  • Place the Revo Uninstaller installer or portable files into the folder.
  • If using an installer, verify available silent switches (commonly /S, /silent, or /VERYSILENT for NSIS/ Inno setups). Test on a VM.
  1. Create addon structure
  • Inside Addon_Revo, create: i386 (or AMD64 if targeting x64) and Layout file placement matching nLite expectations.
  • Typical layout:
    • AddonRevo
      • i386
        • RevoSetup.exe (or extracted files)
      • Unattend.txt (optional)
      • setup.ini (nLite addon descriptor)
      • addon.inf (instructions for file placement and commands)
  1. Create addon descriptor (addon.inf or setup.ini)
  • Include metadata: Name, Author, Version, Description.
  • Specify which files to copy to the target system (usually to %windir%\Program Files\Revo or %windir%\RevoPortable).
  • Example entries:
    • [Version] Name=Revo Uninstaller Description=Installs Revo Uninstaller after setup
    • [Files] i386\RevoSetup.exe=%ProgramFiles%\Revo\RevoSetup.exe
  1. Add post-install commands
  • Use RunOnce or setupcomplete.cmd to run the installer silently at first boot.
  • Place a small batch file in i386 that will be copied to %windir%\Setup\Scripts\SetupComplete.cmd (or instructed via addon.inf).
  • Example SetupComplete.cmd content (adjust silent switch):

    Code

    start /wait “” “%ProgramFiles%\Revo\RevoSetup.exe” /S exit 0
  • For portable builds, copy the portable folder to Program Files and optionally create shortcuts.
  1. Handle registry and shortcuts
  • If the installer requires registry entries, run the installer to create them, then export needed .reg entries and include a reg import in SetupComplete.cmd:

    Code

    reg import “%ProgramFiles%\Revo\revo.reg”
  • Create Start Menu shortcuts by dropping .lnk files into the Default User profile or creating them via a small PowerShell script in SetupComplete.cmd.
  1. Test the addon
  • Use nLite to add your addon to the Windows source and build an ISO or burn to media.
  • Install on a VM and confirm:
    • Revo files are present in the intended folder
    • Silent install runs or portable files are available
    • Shortcuts and registry entries are correct
    • No prompts appear during first boot
  1. Troubleshoot common issues
  • Silent switches not working: extract the installer and look for installer type; try alternate switches or use AutoIt/InnoExtractor to create a portable set.
  • SetupComplete.cmd blocked: ensure file encoding is ANSI and no extra extension (.txt).
  • File paths wrong: use explicit %ProgramFiles% or %windir% and test paths in a running VM.
  1. Package and distribute
  • Zip the Addon_Revo folder or create an nLite-compatible addon .zip.
  • Include a README with install/test notes and the Revo license terms.

Minimal example files to include

  • addon.inf / setup.ini with metadata and file mappings
  • i386\RevoSetup.exe (or portable files)
  • SetupComplete.cmd to run installer silently or copy portable files
  • Optional revo.reg and shortcut scripts

Safety and licensing

  • Ensure you have the right to redistribute Revo files; include licensing info and avoid bundling trial/paid files without permission.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *