How to Integrate ImgBurn as an nLite Addon Integrating ImgBurn directly into your custom Windows installation media using nLite allows you to deploy a fully functional, lightweight optical burning solution automatically. By converting ImgBurn into an nLite-compatible addon, the software installs silently during the operating system setup phase without requiring manual user intervention. Prerequisites and Tools Required
To successfully create and integrate the addon, you need a specific set of tools and source files:
nLite Deployment Tool: The core utility used to customize and rebuild your Windows installation source.
ImgBurn Installer: The official executable setup file downloaded from the developer’s website.
7-Zip or WinRAR: An archiving utility to package the finalized addon structure.
Silent Switch Parameters: The specific command-line arguments that force the ImgBurn installer to run without displaying a user interface. Step 1: Determine the Silent Installation Switch
Standard installers require user interaction, which halts the automated Windows setup process. ImgBurn utilizes an Inno Setup installer, which supports specific command-line parameters for unattended deployment. The Switch: /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
/VERYSILENT: Instructs the installer to execute the installation entirely in the background without displaying progress windows.
/SUPPRESSMSGBOXES: Automatically answers “Yes” or “OK” to any unexpected prompt or dialog box.
/NORESTART: Prevents the computer from restarting if the installer requests a reboot during the Windows text-mode setup phase.
/SP-: Disables the initial prompt asking “This will install… Do you wish to continue?”. Step 2: Create the Addon Directory Structure
nLite addons require a specific folder architecture and an initialization file (entries.ini) to tell nLite how to process the application.
Create a temporary folder on your local drive named ImgBurn_Addon. Inside that folder, create a subfolder named SVCPACK.
Copy your official ImgBurn installer executable into the SVCPACK folder. Rename it to a simple, short name without spaces, such as imgburn.exe. Step 3: Write the entries.ini File
The entries.ini file serves as the instruction manual for nLite. It specifies where to place the file and what commands to execute during the setup sequence. Open a text editor like Notepad. Paste the following configuration block into the document:
[Entries] imgburn.exe [SetupHotfixesToRun] imgburn.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- Use code with caution.
Save the file exactly as entries.ini inside the root of your ImgBurn_Addon folder (not inside the SVCPACK folder). Step 4: Package the Addon Archive
nLite processes addons natively when they are compressed into a high-ratio archive format, typically 7z or Cabinet (CAB).
Select both the SVCPACK folder and the entries.ini file inside your workspace.
Right-click the selected items, navigate to your compression utility (e.g., 7-Zip), and select Add to archive. Set the archive format to 7z.
Set the compression level to Ultra to minimize the footprint on your installation media. Name the resulting file ImgBurn_nLite_Addon.7z. Step 5: Integrate via the nLite Interface
With the compressed addon package ready, you can now import it directly into your customized Windows distribution project.
Launch nLite and locate your target Windows installation source files.
Advance through the menus until you reach the Task Selection screen.
Select the Hotfixes, Addons and Update Packs option, then click Next.
Click the Insert button on the integration interface and select Add.
Browse to and select your newly created ImgBurn_nLite_Addon.7z file.
Click Next to allow nLite to process the compilation and build your customized ISO image.
When you install Windows using this modified ISO, ImgBurn will install silently in the background, leaving a fully operational shortcut on your desktop upon your first login.
If you want to customize this addon further, tell me if you need to:
Pre-configure settings (e.g., file associations, default burn speeds). Include language packs for localized installations. Troubleshoot errors during the nLite compilation process.
Leave a Reply