Tino Pyssysalo

Updated Qt Installer Released

Published Thursday April 11th, 2019
26 Comments on Updated Qt Installer Released
Posted in Dev Loop, Qt Installer Framework | Tags:

We are happy to announce the new Qt Installer release, based on the Installer Framework 3.1. The main reason for a new installer was that we wanted to provide a more intuitive and streamlined user experience.

We simplified the component tree view by introducing package categories. This has a significantly improved the metadata download performance, as there is no need to load the metadata of all the packages anymore. In addition, it is more intuitive for new users to pick up the right packages instead of selecting everything just in case.

The updated Qt Installer contains four package categories:

  • Latest releases category shows the latest supported releases, e.g. Qt 5.12.2. Additional releases may be visible, if Qt products have dependencies on them.
  • Preview shows the latest unofficial release previews, including snapshots, alpha, beta, and RC releases.
  • Archive contains all supported releases.
  • LTS contains the latest Long-Term Support releases, such as Qt 5.12.2 and 5.9.7.


Qt Installer does not contain unsupported releases anymore. This reduces the download size of the metadata even further which makes the installation process faster and smoother. Another reason why we removed the unsupported versions was that unsupported releases have known security issues that will remain unaddressed. Thus, we do not recommend you using them anymore. Lastly, having fewer releases available significantly lowers the amount of data our mirrors need to store.

The older versions of Qt have not completely disappeared. You can still find them in the archive on http://download.qt.io, where we keep a full history of all our releases. In addition, commercial users will still be able to see old releases in the Qt Installer, as they can purchase extended support.

The Qt Installer is still not yet perfect. We are considering improving login/sign-up experience, and adding a default installation option to improve the on-boarding of new users. However, right now we are researching how to separate the installer UI from the component model. Tight coupling of the UI and the package repository model has set several challenges to improve the UX.


Updates in Maintenance Tool

Qt Installer’s Maintenance Tool has a few improvements as well. Signing is now enabled in Windows. Note however that old Maintenance Tool itself breaks the signing. If you update from Qt Maintenance Tool 3.0.6 or older to 3.1, the tool still lacks the signing. However, after you have updated to 3.1, the future Maintenance Tools include the signing.

In addition, we have enabled the use of Qt Installer and Maintenance Tool, even if there are some broken components. Previously, “Cannot find missing dependency..” or “SHA mismatch detected..” errors aborted the installation. In the new version, you can continue the installation despite some broken components. You will notice that these broken components are greyed out in the component tree and cannot be selected for the installation.

Feeling curious? Try it out for yourself here.

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Dev Loop, Qt Installer Framework | Tags:


RealNC says:

Old Qt versions should still be installable. No support needed, just the ability to install them. I like to keep my code compilable by users who run LTS versions of Ubuntu or CentOS and such, which provide old versions. You’re making it unnecessarily hard to install these old versions.

Again: No support is needed. Just the ability to install them.

Tino Pyssysalo Tino Pyssysalo says:

As mentioned, open-source users can download and install old versions from https://download.qt.io/archive/. Licensees may still use the Archive category in the installer.
Our intention is not to make installation of unsupported versions harder for open-source users. We just have to solve the problem that Qt is growing too large for the CDN mirrors.

Letrab says:

Is there a guide/tutorial/use-case on how to provide updates for your own application installations when using QtIFW? This would be really helpful! (Like updating the MaintenanceTool itself in Qt installations, but applied for your own applications which uses QtIFW)

Like how the config.xml / package.xml should look like, what to put in the installscript.qs …

But nice to see QtIFW is progressing in the right direction! Keep it up!

Tino Pyssysalo Tino Pyssysalo says:

Unfortunately, there is no such a guide or tutorial. You may vote for this suggestion in https://bugreports.qt.io/browse/QTIFW-634 to push it forward.

Leena Miettinen Leena Miettinen says:

Have you seen this page in the Qt Installer Framework Manual:


What kind of additional information would you need?

Letrab says:

Thanks Tino, I voted for the issue.

Yes Leena, I read that page before. What I am looking for more specifically is how to provide the “MaintenanceTool” as a separate package when using QtIFW with own applications. Such that it can be signed (code-signed) and updated separately, as Qt itself is doing. Currently QtIFW itself “just installs” a MaintenanceTool, and for me it is not clear how to take over that part.


John says:

One of the biggest problems with Qt offline installer is the inability to change selected features. For example, if I want to install 32 bit Qt in addition to the previously installed 64 bit Qt, I have to remove the installation, and again reinstall both of them.

Tino Pyssysalo Tino Pyssysalo says:

Indeed, many offline installer users would like to be able to install to the same folder where the previous installation is located. We will work on this.

Juan Pedro Rodríguez says:

Have you fixed the problem of qtcreator installation/update breaking in windows leaving folders with bad permissions and not accessible? . This is happening since many versions ago.

John says:

Can we download the Qt Installer Framework 3.1? The download page is empty: https://download.qt.io/official_releases/qt-installer-framework/3.1.0/

iieklund says:

IFW 3.1 release packages will follow next week / week after that.

Letrab says:

Will it be updated in the MaintenanceTool as well? That one is still on 3.0.6…


RaspiFan says:

Support for Raspberry Pi (Compiled Qt Versions for Raspbian) would be nice.

Tino Pyssysalo Tino Pyssysalo says:

We have moved most QBSPs from the online installer to Qt Account. The justification is that we expect to have dozens of images in the near future. There is an image/toolchain for Raspberry 3 in Qt Account portal. Click on Downloads, choose Qt for Device Creation license and QBSP download.

Flavio says:

Great job! Much faster and easier to use. A few suggestions:

– “Remove all components” should not be the default action
– Metadata download should start in the background while the user performs/skips authentication
– The radio button screen with “Add/Remove”, “Update” and “Remove all” should be ditched and the “Add/Remove” view should be directly shown
– Updates should be presented in another tab with a “count badge” in its title
– “Remove all” can be hidden somewhere in the bottom of the “Add/Remove” view

Eeli Kaikkonen says:

I agree with “Remove all components”. Additionally “Add or remove” and “Update” aren’t very logical. I have used the tool maybe dozens of times but I still can’t remember what the “Update” can actually update, except that the Maintenance Tool updates itself. If I want to update Qt I can use Add or remove, right? Or can I?

At least the metadata could be preloaded and information about the possible updates could be given, or the option could even be disabled if there’s nothing to update.

Tino Pyssysalo Tino Pyssysalo says:

Thanks Favio and Eeli about your feedback.
There are quite many votes to change the default action in MaintenanceTool, so this should happen https://bugreports.qt.io/browse/QTIFW-349.
“Update” and “Add and Remove” are not exactly the same. “Add and Remove” shows that there are new versions of components, but if the user does not add or remove any components, nothing happens. “Update” will install the new version of already installed components.
For example, I cannot use “Add or Remove” to update my Qt Creator to 4.9. However, I can easily update my 4.8.2 to 4.9.

NoName says:

Great work

Do we also get Visual Studio 2019 binaries?

Tino Pyssysalo Tino Pyssysalo says:

After MSVC 2019 is added to supported configurations. This is not an installer issue.

Abhishek says:

For the open source version, there are no Australian mirrors, hence it’s very slow. What I understood by reading some bug reports it re-directs automatically to Chian or Japan. Is there any way users can choose which mirror installer should download from? or is there any place where all the mirrors are listed so users can add and try which are better for there connection?

iieklund says:

Hi Abhishek,

the mirror list can be seen here: https://download.qt.io/timestamp.txt.mirrorlist

Unfortunately there is no mirror in Australia.
The system should pick “closest” mirror based on ping times.

If you want to try another mirror there is a tool (unofficial) you can give a try: https://github.com/JKSH/QtSdkRepoChooser

Carlos Perez says:

Hi. I’m glad that you update the installer with a nicer UX. But I will appreciate the support for offline updates, I mean, install in the same folder and update the software. All installers that I have tested works in that way, except for Qt Installer Framework. For that reason I needed to use an alternative installer framework. But they are not cross-platform, and it’s always a lot of work to maintain multiples installers.
There is this this Jira suggestion:


BogDan says:

I have on big problem since you’ve changed the way you update the revision/micro versions.
Until that change you’ve always updated the revision/micro versions on the same folder (e.g. 5.12).
Now it’s just ridiculously, I have five 5.9.x, 5.10.0, two 5.11.x and two 5.12.x folders, but NONE has the latest revision/micro version! Not a single one!
IMHO all 5.x.y revision/micro versions should go by default in 5.x folder and if an user really want to use a specific version he can install it from “archive” folder.
As a Qt maintainer, I wonder, quite often, if it worth to spend time to fix bugs that will go in revision/micro versions as long as even I, as a Qt maintainer, don’t use them … I imagine that the percentage of Qt users that are using the latest Qt versions is very low…

Nikita says:

Sorry, but this looks very bad.

“The main reason for a new installer was that we wanted to provide a more intuitive and streamlined user experience.”
It became very unintuitive, you need to know what does “Archive”, “LTS”, “Latest releases” mean, you need to press Refresh button after selecting these types, refreshing takes a couple of seconds, Qt Installer freezes while refreshing.

I need older versions, but even “Archive” doesn’t allow me to use them.

“We simplified the component tree”
It’s not simplified, it’s truncated.

Seems “Qt Installer does not contain unsupported releases anymore” “significantly improved the metadata download performance”, not by “introducing package categories”.

I’m very disappointed by this release.

Carlos Perez says:

Are you planing providing an UI based on Qt Quick Controls 2? That will provide the best UX ever.

Tino Pyssysalo Tino Pyssysalo says:

We have all the options still open wrt the installer UI. Currently, we doing research to use a package manager in the installer.

Commenting closed.

Get started today with Qt Download now