Skip to content

VirtualLab Fusion Silent Installation Guide

Purpose

This document describes how to install VirtualLab Fusion silently on Microsoft Windows systems.

The silent installation is intended for administrators who want to deploy VirtualLab Fusion without user interaction, for example by using software deployment systems, scripts, remote administration tools, or endpoint management solutions.

Installer File

The installer is delivered as a single executable file:

Installation_VirtualLab_Fusion_<version>.exe

Important: <version> is a placeholder. Replace it with the actual version/build number of the installer file that was provided to you.

Example:

Installation_VirtualLab_Fusion_2026_2_1_66.exe

The installer contains the required prerequisites and the main VirtualLab Fusion installation package.

Depending on the target system, the following prerequisites may be installed automatically if they are missing:

  • Microsoft .NET 8.0 Desktop Runtime
  • Microsoft Edge WebView2 Runtime
  • Thales Sentinel Driver
  • Microsoft Visual C++ 2022 Redistributable Package

Requirements

The silent installation must be executed with administrative privileges.

Before running the command, make sure that:

  • the installer file is available locally on the target system,
  • the command prompt or deployment process runs elevated,
  • the target system meets the general VirtualLab Fusion system requirements,
  • the log folder used in the command already exists, if logging is enabled.

Basic Silent Installation Command

Run the following command from an elevated command prompt:

"Installation_VirtualLab_Fusion_<version>.exe" /s /clone_wait /v"/qn REBOOT=ReallySuppress"

Important: Replace <version> with the actual version/build number of the installer file.

Example:

"Installation_VirtualLab_Fusion_2026_2_1_66.exe" /s /clone_wait /v"/qn REBOOT=ReallySuppress"

For deployment validation and troubleshooting, it is recommended to create an MSI installation log.

First make sure that the log directory exists, for example:

mkdir C:\Temp

Then run:

"Installation_VirtualLab_Fusion_<version>.exe" /s /clone_wait /v"/qn REBOOT=ReallySuppress /l*v C:\Temp\VirtualLabFusion_Install.log"

Important: Replace <version> with the actual version/build number of the installer file.

Example:

"Installation_VirtualLab_Fusion_2026_2_1_66.exe" /s /clone_wait /v"/qn REBOOT=ReallySuppress /l*v C:\Temp\VirtualLabFusion_Install.log"

Optional Setup Launcher Log

If troubleshooting of the InstallShield setup launcher is required, an additional launcher log can be created:

"Installation_VirtualLab_Fusion_<version>.exe" /s /clone_wait /debuglog"C:\Temp\VirtualLabFusion_SetupLauncher.log" /v"/qn REBOOT=ReallySuppress /l*v C:\Temp\VirtualLabFusion_Install.log"

Important: Replace <version> with the actual version/build number of the installer file.

This creates two log files:

C:\Temp\VirtualLabFusion_SetupLauncher.log
C:\Temp\VirtualLabFusion_Install.log

Parameter Description

Parameter Description
/s Runs the InstallShield setup launcher in silent mode.
/clone_wait Ensures that the setup launcher waits for the actual installation process to finish before returning an exit code. This is important for automated deployments.
/v"..." Passes parameters to the embedded Windows Installer package.
/qn Runs the MSI installation without user interface.
REBOOT=ReallySuppress Prevents the installer from automatically restarting the system.
/l*v <logfile> Creates a detailed MSI installation log.
/debuglog"<logfile>" Creates an InstallShield setup launcher log. This is optional and mainly useful for troubleshooting.

Exit Codes

The following exit codes should be treated as successful results:

Exit Code Meaning
0 Installation completed successfully.
3010 Installation completed successfully, but a restart is required.

If exit code 3010 is returned, restart the system before using VirtualLab Fusion in production.

Deployment systems should treat both 0 and 3010 as successful installation results.

Example Batch File

The following example batch file can be used for automated deployment. Adjust the installer file name before using it.

@echo off
setlocal

set "SETUP=Installation_VirtualLab_Fusion_<version>.exe"
set "LOGDIR=C:\Temp"
set "LOGFILE=%LOGDIR%\VirtualLabFusion_Install.log"

if not exist "%LOGDIR%" mkdir "%LOGDIR%"

"%SETUP%" /s /clone_wait /v"/qn REBOOT=ReallySuppress /l*v %LOGFILE%"

set "RC=%ERRORLEVEL%"

echo Installer ExitCode: %RC%

exit /b %RC%

Important: Replace <version> in the batch file with the actual version/build number of the installer file.

Example:

set "SETUP=Installation_VirtualLab_Fusion_2026_2_1_66.exe"

Validation After Installation

After the silent installation has finished, verify the following items:

  • VirtualLab Fusion is installed.
  • The application can be started.
  • Required prerequisites were installed successfully.
  • The installation returned exit code 0 or 3010.
  • If logging was enabled, the installation log does not contain a blocking error.

Notes

The installer automatically installs required prerequisites if they are missing on the target system. The prerequisite installers are executed silently during silent deployment.

The parameter /clone_wait is recommended for automated installations because InstallShield may start a child process internally. Without this parameter, a deployment script may continue before the actual installation has finished.

📌 In the print dialog, choose "Save as PDF". For a clean PDF without URLs or page numbers, uncheck "Headers and footers" in "More settings".

Tags: Administration Installation Silent VirtualLab Fusion