Windows - Software - Install CDBurnerXP

What the CDBurnerXP deployer does

This Automox Worklet™ deploys CDBurnerXP to Windows endpoints. CDBurnerXP is a free CD, DVD, HD-DVD, and Blu-ray burning utility published by Canneverbe Limited, and the Worklet handles every step that a manual install would otherwise demand of an admin.

The Worklet checks whether CDBurnerXP is already registered in the Windows uninstall hives. If not, it downloads the matching 32-bit or 64-bit installer from the Automox cache and runs it with /VERYSILENT and /NORESTART switches. There is no end user prompt, no GUI window, and no reboot.

The evaluation phase reads DisplayName values under the standard uninstall keys and exits clean when the application is already present. Endpoints that picked up CDBurnerXP through another mechanism stay untouched, and the policy only runs the installer on hosts where no matching entry exists.

Why deploy CDBurnerXP through Automox

Endpoints without an approved disc burning utility can push users toward unvetted downloads from search-result advertising and shareware sites. Repackaged installers from those sources often bundle unwanted software, browser toolbars, or unsigned binaries that show up later as a malware finding.

Deploying CDBurnerXP through Automox gives the user the legitimate, license-free build, pulled from the Automox cache rather than a third-party download portal. The installer writes the standard uninstall registry entries under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall (or HKLM\SOFTWARE\Wow6432Node on 64-bit hosts), so asset inventory tooling picks the install up like any other managed application.

Schedule this Worklet against the standard Windows workstation group and CDBurnerXP lands on every in-scope endpoint in a single policy run. FixNow handles the one-off request from a user who needs it today, and the next registry evaluation confirms the install stuck.

How the CDBurnerXP deployment works

1. Evaluation phase: The PowerShell evaluation script checks [System.Environment]::Is64BitOperatingSystem to branch its logic. On 64-bit endpoints it enumerates the 64-bit Uninstall hive at SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and the 32-bit view at HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall, matching DisplayName against CDBurnerXP. On 32-bit endpoints it enumerates HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. A match exits 0 (compliant). No match exits 1 and queues remediation.

2. Remediation phase: The remediation script re-runs the same Uninstall key checks, exits early if CDBurnerXP is already present, then picks the installer based on OS architecture. It downloads CDBurnerXP_64.exe or CDBurnerXP_32.exe from https://api.automox.com/api/cache via System.Net.WebClient, saves it to the script's working directory, and launches it with Start-Process using the /VERYSILENT and /NORESTART arguments. After the installer returns, the script re-checks the Uninstall keys and writes a success or failure message to the Automox activity log.

CDBurnerXP deployment requirements

• Windows endpoint, 32-bit or 64-bit, with the Automox agent installed and reporting to the console

• Outbound HTTPS reachability to api.automox.com so the agent can retrieve the cached installer

• SYSTEM context (the default Automox agent context) for write access to the script working directory and execution of the downloaded installer

• Roughly 150 MB of free disk space for the installer download and the installed application

• PowerShell 5.1 or later (shipped by default on supported Windows builds; no additional install required)

• Group Policy and AppLocker rules that permit running unsigned or Inno Setup installers from the agent's working directory

Expected endpoint state after CDBurnerXP deployment

After a successful remediation run, CDBurnerXP appears in Windows Settings under Apps and Features (and in the legacy Control Panel Programs and Features view). On a 64-bit endpoint, the install registers under HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall because the application itself is 32-bit code shipped through the 64-bit installer. On a 32-bit endpoint, the install registers under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. The CDBurnerXP shortcut is added to the Start menu and the application is installed under C:\Program Files (x86)\CDBurnerXP on 64-bit Windows.

Run this PowerShell one-liner to confirm the install: Get-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object DisplayName -like 'CDBurnerXP*' | Select DisplayName, DisplayVersion. Expect a row with DisplayName CDBurnerXP and a current DisplayVersion. On a failed run, the Automox activity log shows "CDBurnerXP 64-bit installation failed" or the 32-bit equivalent.

Subsequent evaluation runs find the registry entry and exit 0 without re-downloading or re-running the installer. The endpoint does not require a reboot at any point during the install. End users can launch CDBurnerXP from the Start menu the moment the policy run completes and begin burning ISO images, data discs, audio CDs, or video DVDs.