Executive Summary 

A stored cross-site scripting security issue in the Qlik Talend Administration Center has been identified. This issue was resolved in a patch, which is already available.

This issue was discovered by Ahsan.

Affected Software 

All versions of Qlik Talend Administration Center before Patch_20260123_QTAC-1883 (cumulative patch)_R2026-01_v1-8.0.1 are affected.

Severity Rating 

Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), this issue is rated medium.

Vulnerability Details

CVE-2026-pending 

Severity: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N: (5.4 Medium)

A stored cross-site scripting vulnerability has been found in Qlik Talend Administration Center. An attacker with permission to manage servers can store an XSS payload that can be triggered by a different user.

Resolution 

Upgrade at the earliest. The following table lists the patch versions addressing the vulnerability (CVE-2026-pending).

Always update to the latest version. Before you upgrade, check if a more recent release is available.

Executive Summary 

A broken access control issue has been identified in Qlik Talend Administration Center, which allows a user with View permission to modify the Qlik Talend Studio update URL. This issue was resolved in a patch, which is already available.

This issue was discovered by Kaushik Roy.

Affected Software 

All versions of Qlik Talend Administration Center before Patch_20251121_QTAC-1471_R2025-11_v1-8.0.1.

Severity Rating 

Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), this issue is rated high.

Vulnerability Details

CVE-2026-pending 

Severity: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N: (8.2 High)

A broken access control issue has been identified in the Qlik Talend Administration Center, which allows a user with View permission to modify the Qlik Talend Studio update URL. This could be exploited to download malicious software to a Qlik Talend Studio instance.

Resolution 

Upgrade at the earliest. The following table lists the patch versions addressing the vulnerability (CVE-2026-pending).

Always update to the latest version. Before you upgrade, check if a more recent release is available.

After updating the SQL Server JDBC driver in the Talend Administration Center (TAC), executing metaservlet calls to associate task results in a deployment failure. The system specifically fails because it is still searching for the old driver version, resulting in a NoSuchFileException.

Resolution

To resolve the dependency conflict and refresh the application cache, follow these steps:

1. Verify JAR Location and ensure the new JDBC JAR file exists only in the following directory:
   
   /talend/tac/apache-tomcat/webapps/tac/WEB-INF/lib/

   Do not keep multiple versions or duplicates in other library folders to avoid classpath conflicts.

2. Stop the Qlik Talend Administration Center service and Tomcat instance
   
   
3. Clear Tomcat Cache
   
   Since Tomcat caches compiled JSP files and session data, manually clear the work and temp directories by renaming the current folders:
   
   
   • tomcat/work > tomcat/work_bak
   • tomcat/temp > tomcat/temp_bak
4. Create new, empty work and temp folders
   
   
5. Start the Qlik Talend Administration Center service
   
   Tomcat will rebuild the cache using the current libraries present in the WEB-INF/lib folder.

Cause

The error indicates that although the old driver was removed from the file system, Qlik Talend Administration Center (or the underlying Tomcat container) still holds a reference to the deleted JAR file. This suggests a caching issue within the Tomcat application server.

Environment

• Qlik Talend Administration Center

Is Qlik Sense Enterprise on Windows affected by the security vulnerability CVE-2023-26136 (nvd.nist.gov)?

CVE-2023-26136 is a vulnerability detected in Node.js, a third-party component used by Qlik Sense Enterprise on Windows. Security scans may flag the vulnerability in a Qlik Sense Enterprise on Windows environment. 

While Qlik was not directly impacted, the affected third-party component has been updated across supported versions.

Affected versions: 

• Qlik Sense Enterprise on Windows May 2024 patch 23
• Qlik Sense Enterprise on Windows November 2024 patch 17
• Qlik Sense Enterprise on Windows May 2025 patch 5 

Resolution

Upgrade to any of the following (or later) versions:

• Qlik Sense Enterprise on Windows May 2024 patch 24
• Qlik Sense Enterprise on Windows November 2024 patch 18
• Qlik Sense Enterprise on Windows May 2025 patch 6 
• Qlik Sense Enterprise on Windows May 2026 IR 

In some instances, the Qlik Sense patch installer updates service binaries but does not remove leftover node_modules folders from previous installations. The old request/node_modules/tough-cookie directories may still exist on disk even though the running service no longer uses them.

If you notice stale folders post-upgrade:

1. Run the following PowerShell script as Administrator to clean up stale folders:
   
   

   # Qlik Sense - tough-cookie stale folder cleanup
   # Run as Administrator after upgrading to v14.231.26 or later
   # Take a backup or snapshot before running
   Write-Host "Starting tough-cookie cleanup..." -ForegroundColor Cyan
   # Step 1 - Stop Service Dispatcher (this will stop all dependent Qlik Sense
   services)
   Stop-Service -Name "QlikSenseServiceDispatcher" -Force -ErrorAction
   SilentlyContinue
   Write-Host "Stopped: QlikSenseServiceDispatcher" -ForegroundColor Yellow
   Start-Sleep -Seconds 5
   # Step 2 - Remove tough-cookie directories
   $paths = @(
   "C:\Program Files\Qlik\Sense\ConverterService\node_modules\tough-cookie",
   "C:\Program
   Files\Qlik\Sense\DownloadPrepService\node_modules\request\node_modules\tough
   cookie",
   "C:\Program
   Files\Qlik\Sense\MobilityRegistrarService\node_modules\request\node_modules\tough
   cookie",
   "C:\Program
   Files\Qlik\Sense\NotifierService\node_modules\request\node_modules\tough-cookie"
   )
   foreach ($path in $paths) {
   if (Test-Path $path) {
   Remove-Item -Path $path -Recurse -Force
   Write-Host "Removed: $path" -ForegroundColor Green
   } else {
   Write-Host "Not found (already clean): $path" -ForegroundColor Gray
   }
   }
   Write-Host "`nCleanup complete. Restart Service Dispatcher manually to bring all
   services back online." -ForegroundColor Cyan​

   This script may need to be re-run after any future Qlik Sense Enterprise on Windows patch or reinstallation, as the installer may restore these directories.

   The script is provided as is and to be used at your own risk.

2. Restart the Qlik Sense Service Dispatcher service

Internal Investigation ID(s)

• SUPPORT-2237

Qlik NPrinting tasks stop progressing at random, even if the Qlik NPrinting services otherwise run without issue. Task executions are blocked, with no specific error messages logged. 

The Rabbit logs read the following error:

missed heartbeats from client, timeout: 15s

The problem is similar to the one described in Qlik NPrinting task run but do not progress: stuck on same percentage, with some notable differences:

1. It can occur on any Windows Server operating system, while the previous issue is restricted to 2019.
2. The error message {{badmatch,{error,eacces}} is not present in the Rabbit logs.
3. A missed heartbeats from client error is logged instead.

The problem can start after an upgrade to Qlik NPrinting 2025 or any later releases.

Resolution

1. Verify that Qlik NPrinting has been installed on a dedicated server as required; see Unsupported configurations: Installation for details. 
2. Verify that all Qlik NPrinting Server Engine and Designer Anti Virus Folder Exclusions have been applied correctly
3. If the problem persists, increase the timeout window to reduce heartbeat frequency.

   This step requires changes to service configuration files. Back up all files before you proceed.

   1. Locate the configuration files in C:\Program Files\NPrintingServer\NPrinting\[ServiceName] folders
   2. Stop the Qlik NPrinting Services
   3. Set the following in the scheduler.config, engine.config, webengine.config, and audit.config (if active):
      
      

      <add key="rabbitmq-timeout" value="60" />
      <add key="rabbitmq-requested-heartbeat-sec" value="30" />

      
      
   4. In the scheduler.config, set:
      
      

      <add key="engine-heartbeat" value="15" /> 
      <add key="engine-heartbeat-offline-threshold" value="30" />

   5. Restart the services

Cause

Qlik NPrinting services send heartbeats to verify that communication between them is open.

Recent versions of Qlik NPrinting are more sensitive to missed heartbeats, meaning a missed communication check can lead to the services being unable to process tasks as expected. 

This may be caused by a busy Qlik NPrinting server (such as when the software is run on a shared server, resulting in unsustainably high CPU usage) or by the heartbeats being delayed by security scans.

Related Content

• Troubleshooting 
• Unsupported configurations

Internal Investigation ID(s)

• SUPPORT-8903

Environment

• Qlik NPrinting

Installing Qlik Replicate 2025.5 and 2025.11 GA versions on Linux 9.7, an error may occur during installation or when attempting to start the services.

This issue is typically observed when the installation is performed using a different account than the one intended to run the services.

For example, installing Qlik Replicate with the account apsup while specifying qlik as the service account:

sudo user=qlik group=qlik verbose=true rpm -ivh --prefix /opt areplicate-2025.11.0-164.x86_64.rpm

A typical error message is:

arep.sh: created /opt/attunity/replicate/bin/areplicate
arep.sh: created /etc/systemd/system/areplicate.service
systemctl daemon-reload failed
failed to install areplicate as a service, areplicate will not be run
warning: %posttrans(areplicate-2025.11.0-164.x86_64) scriptlet failed, exit status 9  

Resolution

Upgrade your Qlik Replicate installation. This issue has been resolved in Qlik Replicate 2025.11 SP3 (2025.11.0.437 and later).

Internal Investigation ID(s)

00443949

Environment

• Qlik Replicate 2025.5
• Qliklik Replicate 2025.11 GA/SP1/SP2
• Linux 9.7

The Data Load Editor in Qlik Sense Enterprise on Windows 2025 experiences noticeable performance issues.

Resolution

Fix Version

Qlik Sense May 2025 SR 6 and higher releases.

Workaround

A workaround is available. It is viable as long as the Qlik SAP Connector is not in use.

1. In a Windows file browser, navigate to C:\Program Files\Common Files\Qlik\Custom Data\
2. Move the QvSapConnectorPackage directory to a different location

No service restart is required.

Internal Investigation ID(s) 

SUPPORT-6006

Environment

• Qlik Sense Enterprise on Windows

Beginning from Qlik Replicate version 2024.05, a new checkbox was added to Log Stream Staging tasks: Retrieve all source columns on UPDATE

The option is available in Task Settings (A) > Change Processing > Change Processing Tuning (B)

It is enabled (C) by default.  

When Retrieve all source columns on UPDATE is enabled, it will cause any table added to the task to issue an ALTER on the table to enable supplemental logging on all columns if the source database is Oracle.

Resolution

For high-transaction tables, enable Supplemental Logging on all columns during off-peak hours manually before adding them to the Qlik Replicate task.

Cause

In previous Qlik Replicate versions, supplemental logging was not required on all columns and was enabled only on Primary Key Columns. But with that new checkbox, it is required to be added to all columns.

When any new table is added to the Log Stream Staging task, Qlik Replicate issues an ALTER TABLE command to enable Supplemental Logging on all columns. This command can fail on high-transaction or busy tables in the source Oracle DB.

Environment

• Qlik Replicate

Installing Qlik Data Gateway v1.7.13.0 on Windows may fail. The installation remains stuck in a loop.

The system first requires a restart of Windows, but will not complete the installation afterwards. Instead, a Microsoft Visual C++ Redistributable Modify Setup prompt will be displayed:

Whatever option is chosen, a new pop-up appears stating, 'Please restart your system before running the Qlik Data Gateway - Direct access installation'. This will restart the loop. 

Resolution

Install v1.7.14.0 when available.

If it's necessary to perform a new installation in the meantime, use v1.7.11.0.

Cause

This is a known defect (SUPPORT-8964) affecting v1.7.13.0.

Internal Investigation ID(s)

SUPPORT-8964

Environment

• Qlik Direct Access Gateway

Qlik introduced a change in how automation permissions are handled for the Analytics Admin role.

When was the change introduced?

The change is already live as of the 11th of May, 2026.

What does that mean for me?

Analytics Admins can now claim ownership of another user's automation. After claiming ownership, they can make necessary changes to it and enable the automation. However, they can no longer transfer ownership to another user.

How do I claim ownership of an automation?

As an Analytics admin, to claim ownership of an automation:

1. Navigate to the Automations section in the Administration Console
2. Locate the automation you want to claim ownership of, and click the Actions menu (...)
3. Choose Claim ownership
   
   

This behavior change only applies to Analytics Admins. Tenant admins can still transfer ownership to any user with the appropriate access rights in the tenant.

Environment

• Qlik Cloud Analytics
• Qlik Automate

From the Qlik Download page

1. Access the Qlik Download page: Product Downloads
2. Log in with your Qlik ID
3. Select Qlik Data Analytics (Category)
4. Select Qlik Sense Desktop (Product)
5. Choose the appropriate version (Release)
6. Choose the appropriate release number (Release Number)
7. Click the download link

HTTP Response Header exposes Microsoft-HTTPAPI/2.0 as the server source. An attacker could use this information to expose known vulnerabilities for the server source.

Resolution

This header is included in the HTTP header by .NET framework, which means it can not be directly controlled by Qlik software. 

Environment

Qlik Sense Enterprise on Windows, all version
QlikView, all versions
Qlik NPrinting, all versions

Internal Investigation IDs:

• QLIK-90522

Method 1: From the Data Sources

1. Open the Qlik Analytics Service
2. Select  Catalog 
3. Pick your Space 
4. Click Space Details then
5. Select Data Files from the context menu
   
   
   
   
   
6. Locate the data you wish to delete
7. Click the ellipses to open the next menu
8. Click Delete
   
   
   
   
   
9. Alternatively, add /data at the end of the URL.

Method 2: From the Data Load Editor

1. Open the App with a connection to the data files you wish to edit
2. Go to Data Load Editor
3. On the Right Side of the Data Load Editor under add data section select your data space.
4. Click on the table icon under datafiles.
   
   
    
5. select the Delete option on the right side of each file that you want to delete.
   
   

Environment

• Qlik Sense Business 
• Qlik Cloud 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

After upgrading to Remote Engine 2.13.13, when enabling the option to execute a job from Studio on a remote engine, the process fails due to SSL and PKCS-related errors.

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Resolution

SSL Configuration for Talend Studio to Connect with Remote Engine

1. Retain the Keystore and Truststore Passwords Generated During Installation

   During the installation of Talend Remote Engine, SSL credentials are automatically generated. To retrieve the keystore password, execute the following command:

   cat /opt/TalendRemoteEngine/bin/sysenv

   and locate the line

   TMC_ENGINE_JOB_SERVER_SSL_KEY_STORE_PASSWORD=<PASSWORD>

2. Required Keystore and Truststore Files

   The following files are necessary for secure communication between Talend Studio and the Remote Engine:

   /opt/TalendRemoteEngine/etc/keystores/jobserver-client-keystore.p12
   /opt/TalendRemoteEngine/etc/keystores/jobserver-client-truststore.p12 (Truststore file added with RE 2.13.13)

   Transfer these files to your Talend Studio workstation and store them in a dedicated folder.

3. Configure Talend Studio to Use SSL

   Edit the Studio startup configuration file, depending on your operating system:

   • For Linux (x86_64): studio/Talend-Studio-linux-gtk-x86_64.ini
   • For ARM architecture: studio/Talend-Studio-gtk-aarch64.ini  
   • For Windows: Talend-Studio-win-x86_64.ini
4. Add the following JVM options to the configuration file, and adjust the file paths and password values accordingly:

       -Dorg.talend.remote.client.ssl.force=true
       -Dorg.talend.remote.client.ssl.keyStore=path_to_keystore/jobserver-client-keystore.p12
       -Dorg.talend.remote.client.ssl.keyStoreType=PKCS12
       -Dorg.talend.remote.client.ssl.keyStorePassword=<password_from_step_1>
       -Dorg.talend.remote.client.ssl.keyPassword=<password_from_step_1><
       -Dorg.talend.remote.client.ssl.trustStore=path_to_truststore/jobserver-client-truststore.p12
       -Dorg.talend.remote.client.ssl.trustStoreType=PKCS12
       -Dorg.talend.remote.client.ssl.trustStorePassword=<password_from_step_1>
       -Dorg.talend.remote.client.ssl.disablePeerTrust=false
       -Dorg.talend.remote.client.ssl.enabled.protocols=TLSv1.2,TLSv1.3
      

Cause 

Talend Remote Engine enforces SSL communication by default, ensuring that all interactions with the engine are encrypted. If Studio does not have the appropriate certificates installed, it will be unable to establish a secure connection with the Remote Engine.

Environment

• Talend Studio 
• Talend Cloud 

When using Key Pair authentication and creating a new Snowflake connection, you might encounter the following error:

Illegal Argument

Resolution

The provided private key file (.p8) is not in the correct format, or the key file password is invalid. 

To get the actual error, install SnowSQL utility in the Linux machine where the Qlik Data Movement gateway is installed and try to connect to the same account:

snowsql -a <account> -u <username> --private-key-path <path to file/rsa_key.p8>

This will provide the exact error on why the connectivity is failing and assist in identifying which root cause applies.

Cause

Environment

• Qlik Talend Cloud

At Qlik Connect 2026 I hosted a session called "Fast 15" with my top 10 visualization tips. Here's the app I used with all tips including test data.

Tip titles, more details in app:

• Product Catalogue
  How to make a product catalogue. Here's a variant with the new Pivot table using inline SVG images. The product images have been converted to Base64 and inlined within the inline SVG. The text is just positioned on top of the image.
• Table waterfall with subtotal and partial sum
  How to make table waterfall with add bars, and bars for subtotal and retro sum. Spreadsheet for layout, rangesum() and above() for offset and bar, master measures and SVG for waterfall.
• Switches revisited
  How to make a switch. Create a variable vSwitch set value to 0 Use the button, to toggle the variable, use action "set variable"
• Button examples
  How to style a button. Examples of button styles.
• Map with 3d bars
  How make 3d bar map point layer. Use a simple SVG with two rects: the bar and the shadow in Data URI with inline SVG. Added a top and base triangle for a little extra 3d effect.
• Rank box chart
  How to make a rank box chart. Use unicode boxes and repeat().
• Filter pane examples
  How to place a filter pane. Example of top panel, side panel and drawer style.
• Half Gauge
  How to make a multi half gauge. Use the map and two line layers.
• Pie chart value and percentage in the same label
  How to customize pie chart labels. Use dual() and number format measure expression.
• Line chart symbols
  How to add symbols in the line chart. Use dual and unicode symbols.
• Control chart with combo chart
  How to make a control chart with dynamic bounds. Use combo and measures for center, upper and lower bounds
• Formatting x-axis and keep field
  How to format the x-axis. Use dual and aggr.

I want to emphasize that many of the tips were discovered by others than me, I tried to credit the original author at all places when possible.

If you liked it, here's more in the same style:

• 24 days of visualization Season III, II, I
• Top 10 Tips Part X, IX, VIII, VII, VI, V, IV, III, II , I 
• Let's make new charts with Qlik Sense
• FT Visual Vocabulary Qlik Sense version
• Similar but for Qlik GeoAnalytics : Part III,  II, I

Thanks,
Patric

After an admin invited a user to a Qlik Cloud tenant, the user never received the invitation email.

How can this be resolved quickly?

Resolution

There are several possible reasons for a user not to receive their expected invite email, such as temporary glitches with the recipient's mail server, a spam filter capturing the invite, or even a simple accidental deletion of the invite.

However, an invited user does not actually need the invitation email to access the tenant. They can log in to the tenant after the invite was sent, regardless of whether or not they received the email.

To get a user you previously invited into your Qlik Cloud tenant:

1. Request that the user access the tenant's URL (example: https://TENANT.REGION.qlikcloud.com)
2. They are redirected to the login panel
   • If the user already has a Qlik account with the same email used for the invitation, ask the user to log in
   • If the user doesn't have a Qlik account with the same email used for the invitation, ask them to sign up for one, which will redirect them to https://register.myqlik.qlik.com/
     
     
     
     For instructions, see How to Register a Qlik Account.
     
     
   • Once the user has successfully logged in, they can use the tenant as normal.

Environment

• Qlik Cloud Analytics

This template was updated on December 4th, 2025 to replace the original installer and API key rotator with a new, unified deployer automation. Please disable or delete any existing installers, and create a new automation, picking the Qlik Cloud monitoring app deployer template from the App installers category.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With a single Qlik Automate template, you can now install and update the apps on a schedule with a set-and-forget installer using an out-of-the-box Qlik Automate template. It can also handle API key rotation required for the data connection, ensuring the data connection is always operational.

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

'Qlik Cloud Monitoring Apps deployer' template overview

This automation template is a set-and-forget template for managing the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software (OSS) GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically verified prerequisite settings, roles, and entitlements, notifying the user during the process if changes in configuration are required, and why.
• Installs latest versions of specified applications from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Creates a daily reload schedule.
• Reload applications post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions.

Configuration:

Update just the configuration area to define how the automation runs, then test run, and set it on a weekly or monthly schedule as desired.

Configure the run mode of the template using 7 variable blocks

Users should review the following variables:

1. configuredMonitoringApps: contains the list of the monitoring applications which will be installed and maintained. Delete any applications not required before running (default: all apps listed).
2. refreshConnectorCredentials: determines whether the monitoring application REST connection and associated API key will be regenerated every run (default: true).
3. reloadNow: determines whether apps are reloaded immediately following updates (default: true).
4. reloadScheduleHour: determines at which hour of the day the apps reload at for the daily schedule in UTC timezone (default: 06)
5. sharedSpaceName: defines the name of the shared space used to import the apps into prior to publishing. If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring - staging).
6. managedSpaceName: defines the name of the managed space the apps are published into for consumption/ alerts/ subscription use.If the space doesn't exist, it'll be created. If the space exists, the user will be added to it with the required permissions (default: Monitoring).
7. versionsToKeep: determines how many versions of each staged app is kept in the shared space. If set to 0, apps are deleted after publishing. If a positive integer value other than 0, that many apps will be kept for each monitoring app deployed (default: 0).

App management:

If the monitoring applications have been installed manually (i.e., not through this automation), then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. The automation will update any managed apps that don't match the repository's manifest version.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the application's installation process to a managed space. It will scope the API key name to `QCMA – {spaceId}` of that managed space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already. It will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes, but an update of the template from the template picker will be required, since the applications are hard coded into the template. The automation will begin to fail with a notification an update is needed once a new version is available.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: Each upgrade may generate a new set of QVDs if the data models for the applications have changed due to bug fixes, updates, new features, etc. The history is preserved in the prior versions of the application’s QVDs, so the data is never deleted and can be loaded into the older version. 

After upgrading to Microsoft Windows Server 2025, the installed Qlik Sense Enterprise on Windows patch version is no longer visible in the Installed Updates summary.

In previous Windows Server versions, navigating to Control Panel > Programs and Features > Installed Updates displayed the patch version. 

Changes in Windows Server 2025 affect how installed updates are displayed in the Control Panel. This does not indicate a failed installation.

You can verify what patch version of Qlik Sense Enterprise on Windows you have installed by retrieving it from the Windows registry. Alternatively, see What version of Qlik Sense Enterprise on Windows am I running?

Resolution

The registry key including the patch version is:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\QlikSenseEnterprisePatch

You can query the registry using PowerShell.

Administrator privileges are required to access the Registry or to run the recommended PowerShell script.

Option One: Use Get-QlikSensePatchInfo.ps1 

We recommend using the attached Get-QlikSensePatchInfo.ps1 script. 

1. Download Get-QlikSensePatchInfo.zip and extract it
2. Run Get-QlikSensePatchInfo.ps1
3. The script will return:
   • DisplayName: Patch name
   • DisplayVersion: Patch version number
   • UninstallString: Uninstall command

Example output:

DisplayName : Qlik Sense May 2025 Patch 17
DisplayVersion : 14.231.29
UninstallString : "C:\ProgramData\Package Cache\c70a85bf-ecb8-4772-affb-80f28a97bdcb\Qlik_Sense_update.exe"

Option Two: Query the registry manually

1. Open a PowerShell command line with elevated permissions
2. Run the following PowerShell command:
   

   Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\QlikSenseEnterprisePatch" |
   Select-Object DisplayName, DisplayVersion, UninstallString​

Environment

• Qlik Sense Enterprise on Windows
• Windows Server 2025

Starting from Qlik Replicate versions 2024.5 and 2024.11, Microsoft SQL Server 2012 and 2014 are no longer supported. Supported SQL Server versions include 2016, 2017, 2019, and 2022. For up-to-date information, see Support Source Endpoints for your respective version.

Attempting to connect to unsupported versions, both on-premise and cloud, can result in various errors.

Examples of reported Errors:

• Qlik Replicate 2024.5 accessing Microsoft Azure SQL Server 2014
  
  [SOURCE_CAPTURE  ]W:  Table 'dbo'.'tableName' has encrypted column(s), but the 'Capture data from Always Encrypted database' option is disabled. The table will be suspended  (sqlserver_endpoint_capture.c:157)
  
  
• Qlik Replicate 2024.11 accessing Microsoft SQL Server 2014
  
  [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: 42S02 NativeError: 208 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid object name 'sys.column_encryption_keys'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4067)

Cause

The system view sys.column_encryption_keys is only available starting from SQL Server 2016. Attempting to query this view on earlier versions results in errors.

Reference: sys.column_encryption_keys (Microsoft Docs)

Resolution

Upgrade your SQL Server instances to a supported version (2016 or later) to ensure compatibility with Qlik Replicate 2024.5 and above.

Internal Investigation ID(s)

00375940, 00376089

Environment

• Qlik Replicate versions 2024.5, 2024.11, and higher
• Microsoft SQL Server 2014, 2012, and lower (unsupported)