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?
Does this happen if you make a brand new document and add the Now() in text object? We've noticed this version is much slower in non-webview mode but I personally have not seen a difference adding Now() in text objects when I tried it. We are using September 2025 SR2.
I haven't yet tested whether the same issue occurs in a completely new QlikView document.
I only noticed the Now() issue by coincidence. One of our older reports was significantly slower to use than the others, so I started investigating what could be causing it. I eventually found that for some reason one of the Text Objects contained the Now()function.
I just wanted to mention this because, at least in our environment, using the Now() function seems to make the performance issue significantly more noticeable with the September 2025 versions. No problems with older versions.
I will also test this by creating a completely new document and see how it behaves.
I have now done some testing with a new QlikView document.
First, I created a new document in September 2025 SR2 with a simple inline load containing around 50 rows of data. I then added a Text Object with the expression =Now(). In this case, I could not notice any performance issues. The UI remained responsive and the QlikView menus worked normally.
I then created another new document and loaded a single QVD file containing approximately 577 MB of data, 57 columns, and 7 million rows.
After loading the QVD, I added a new Text Object to the UI with a width of 1000 and a height of 3000, and then scrolled down the page. Compared to May 2024, the scrolling was noticeably more jerky in September 2025 SR2. The scrollbar movement is not smooth, which makes it clear that something is not quite right.
However, opening the Text Object properties and navigating the QlikView menus were still mostly responsive at this point.
I then added =Now() to the Text Object.
After doing that, QlikView Desktop became extremely slow. Opening the Text Object properties and even navigating the QlikView menus became very sluggish, with noticeable delays after clicking.
If I would now remove the Now() function from the Text Object and start adding more objects to the document, such as charts, tables, and KPIs, I am fairly confident that editing and navigating the document with September 2025 releases would gradually become as slow as it is in all of our existing QlikView reports.
None. Someone had used Date(Now()) in a Text Object in one of our older applications for some reason. I have already fixed it from the production application.
I only kept it for testing because it makes the performance issue in the September 2025 versions much more noticeable and should be easier to reproduce.
September 2025 version makes everything we have slow in the desktop mode that we use for app development. Even the default Start Page takes a few seconds to render the objects on that page.
Oh yeah, I had the Start Page disabled. If I go to Help > Show Start Page, the difference is pretty obvious. In May 2024, the Start Page opens almost immediately (less than a second), whereas in September 2025 it takes several seconds (3-4) to render.
Make sure that you check all already hinted possibilities - especially to make a complete new start with QV 2025 which inherits nothing - no earlier installation, user-settings, applications ... nothing.
My earlier testing was done on a clean server where I installed QlikView Desktop September 2025. The test applications were created on that, and they show the same performance issue compared to May 2024 on another server.
