QlikView Desktop September 2025 IR/SR1/SR2 – Severe Performance/Responsiveness Issues
Hi,
We have QlikView Server and QlikView Desktop installed on a Windows Server 2022 machine, which we access via Remote Desktop.
Earlier this year, I upgraded our QlikView installation from May 2023 to September 2025 SR1. After the upgrade, I noticed that QlikView Desktop had become extremely slow and unresponsive.
When QlikView Desktop is started, the menus and the application itself initially seem to work normally. However, as soon as I open a QlikView document, the application becomes very sluggish. On AccessPoint everything works fine.
For example:
- Clicking the QlikView > About menu can take 2–4 seconds before anything happens. - Right-clicking an object on a report can take several seconds before the context menu appears. - Scrolling in list boxes is very jerky and noticeably delayed. - In general, there is a significant delay between clicking something and QlikView responding.
At the time, I did not have time to investigate the issue further.
Today I uninstalled QlikView Desktop and installed the May 2023 version again. The performance immediately returned to normal. When clicking objects or menus in a QlikView document, everything responds almost instantly.
I then upgraded QlikView Desktop to May 2024 SR1, and the performance was still normal.
After that, I upgraded to September 2025 IR, and the performance problem immediately returned.
So far, my testing looks like this:
- May 2023: Good performance - May 2024 SR1: Good performance - September 2025 IR: Very slow / significant UI delays - September 2025 SR1: Very slow / significant UI delays - September 2025 SR2: Very slow / significant UI delays
I have also disabled the antivirus temporarily, but this did not make any difference.
Has anyone else experienced similar QlikView Desktop performance or UI responsiveness issues with the September 2025 releases?
I did notice that post, but I’m not sure the OP is experiencing the same issue. Their problem seems to occur even when no files are open in QlikView Desktop, and it sounds more like a graphical/rendering issue.
In my case, the problem only starts when a .qvw file is opened. If no document is open, QlikView Desktop works perfectly fine.
I think it's a graphic issue and not related to the associative/calculation engine because things like moving an object does not trigger a calculation and scrolling within a listbox/table only after n extra rows.
Therefore try a few of the suggestions from the mentioned post to exclude systematically the potentially causes. I think I would start with the desktop clinet and an absolute clear new-installation + ensuring that there is no previous configurations (removing the settings.ini after a backup) and creating a new application with a few dummy inline-data (no actions/macros, easter egg stuff, extensions, bookmarks, connections, ...).
We still had our old Windows Server 2012 R2 Qlik Sense server online, and it did not have QlikView installed.
I decided to test this by installing QlikView Desktop September 2025 SR2 on that server as well, and I experienced exactly the same performance issue there when opening reports.
I also created a new QlikView document using a simple inline load with 20 rows and added a list box to the user interface. This worked normally, without any performance issues.
This suggests that the problem may not be specific to our Windows Server 2022 environment or our particular server configuration.
I copied one of our QlikView documents to the server where I tested it with QlikView Desktop September 2025 SR2.
The document contains a Dashboard with four bar charts, nine KPIs (Text Objects), and a list box + some titles etc (Text Objects). The document is approximately 500 MB in size and works well with QlikView Desktop versions prior to September 2025.
With September 2025 SR2, however, the document was practically unusable. Almost every interaction had a significant delay — for example, clicking something or right-clicking an object could take several seconds before QlikView responded.
I started deleting objects from the Dashboard to see if I could identify what was causing the problem. When I deleted one of the Text Objects containing the expression =Now(), the severe performance issue disappeared.
The document is still slightly slower than with May 2024 SR1, but it is now usable.
For example, with May 2024 SR1, when I right-click a Text Object, the context menu opens immediately. With September 2025 SR2, it takes approximately one second. This is still slower, but it is no longer several seconds and the document is usable.
It hints for an incompatibility between the QlikView releases which created and/or saved the qvw's. In the earlier days there was a clear recommendation to migrate from one major-release to the next major-release and not skipping one.
Means open + running + storing the apps to ensure that new/changed features/settings were properly adjusted. Further to have no mismatch between releases which touch the apps - means all desktop clients on the server as well as one each developer machine and of course also the server should be the same. In many scenarios the users don't experience any issues if the above mentioned release-stuff isn't implemented so stricly but it remains some risks - and if anything strange happens it should be the first to look for.
Beside this could now() - there are also warnings of the use within the docu - really becoming a performance killer - especially if it's implemented within variables because their change is a trigger for further calculations. The reason of the issue since QV 2025 may a change or a switch within an underlying library which not query the system-time each milli-second else now in nano-seconds and/or the counter how often the query is performed within a second changed ...
I did some further testing with different QlikView documents.
In the document I tested earlier, one of the Text Objects contained the Now() function. The document was extremely slow with September 2025 SR2. After removing the Text Object containing Now(), the performance improved significantly, although the document is still noticeably slower than with earlier QlikView versions.
I then tested another document where I could not find any use of Now(). This document was also slow, although somewhat faster than the first one.
When I added a simple Text Object containing Now() to this second document, the performance became extremely slow, and navigating the QlikView menus also became very sluggish.
