QlikView Desktop engine
QV2QS uses QlikView Desktop to extract PRJ folders from QVW files. A portable copy of QlikView Desktop (version 12.100.20100, September 2025 SR1) is bundled inside the QV2QS executable. No separate installation of QlikView Desktop is required.
Engine selection
When PRJ generation is enabled (--generatePrj or Auto-generate PRJ in the wizard), QV2QS determines which QlikView Desktop engine to use:
- If QlikView Desktop is not installed on the system, QV2QS launches the bundled portable engine. The bundled engine runs in the background, generates the PRJ folder, and exits automatically. No user interaction is required.
- If QlikView Desktop is installed and registered on the system, QV2QS uses the installed version instead of the bundled engine. The installed version's own license and configuration are used.
Supported configurations
The bundled engine is the only officially supported configuration. QV2QS has been tested and validated exclusively against the bundled QlikView Desktop version.
System installations of QlikView Desktop have not been validated across all versions and are not officially supported for use with QV2QS. If a system installation is present, QV2QS may function correctly, but results have not been verified. QlikView 12.40 (April 2019) or later is recommended when a system installation is used. Versions earlier than 12.40 are not recommended.
For guaranteed compatibility, run QV2QS on a machine without QlikView Desktop installed.
Only the bundled QlikView Desktop engine is officially supported. Compatibility with system installations of QlikView Desktop is an area identified for future testing and validation. Product compatibility statements are subject to change and should not be relied upon as a commitment to support specific QlikView Desktop versions.
Verifying which engine is active
QV2QS logs which engine is selected at the start of every PRJ generation. To check which engine was used, open the system log at %LOCALAPPDATA%\QV2QS\qv2qs.log and look for the QlikView version reported after the engine connects. Run with --logLevel DEBUG to capture the full engine discovery sequence.
For details on log event names and field-level diagnostics, see Logging and diagnostics.