Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Qt Creator 6.0.1 and Qt 6.2.2 running on Windows 7



  • Hi, Christmas is soon upon us, I thought I should bring a gift to those poor souls (like me) that are stuck/prefer working with Qt on Windows 7 instead of 10 or 11.

    Recently I installed Microsoft's new Visual Studio 2022 on my Windows 7 PC, when you install it you get a warning "We haven't designed this version of Visual Studio to work with this operating system. You can still install it but...." Anyway it seems to work nicely on my Windows 7 PC.

    Why cannot Qt Creator issue the same kind of warning and install anyway, instead of exiting with an 0xC0000005 error? Because it is based on Qt 6..2.2 which by design will not run on Windows 7 :-(

    Today I spent some time debugging how much trouble it would be to make Qt 6.2.2 run on Windows 7. Turns on there are 3 showstoppers: qt6core.dll, qt6gui.dll and the platforms plugin qwindows.dll. Some hacking/backporting later I had new versions of them.

    When I replaced both Qt Creator's dlls in C:\Qt\Tools\QtCreator\bin and the qwindows.dll in C:\Qt\Tools\QtCreator\bin\plugins.\platforms, voila! It started just fine:

    Xmas gift

    Next step was to be able to build and run Qt 6.2.2 apps on Windows 7. So I installed MSVC 2019 64-bit 6.2.2 on my Windows 7, late in the installation process it stops with a qmake error (because qmake runs on an unpatched qt6core.dll) but if you click Ignore 2 times it will install anyway. Then if you replace Qt6Core.dll, Qt6Gui.dll and qwindows.dll in C:\Qt\6.2.2\msvc2019_64 compiling and building widgets based programs seems to work fine.
    (I also tested a qtquick program but got the error "Cannot load library C:\Qt\6.2.2\msvc2019_64\qml\QtQuick\qtquickplugin.dll: file not found"
    that plugin dll also needs some patching for Windows7. However since I only work with widgets this problem has low priority.)

    So the Xmas gift is a zip with the 3 patched dlls if you're feeling adventurous...

    P.S. They are a bit rough around the edges so only use them on a Windows 7 PC, on a Windows 10 PC use the real stuff. Merry Xmas!


  • Lifetime Qt Champion

    @hskoglund said in Qt Creator 6.0.1 and Qt 6.2.2 running on Windows 7:

    I thought I should bring a gift to those poor souls (like me) that are stuck/prefer working with Qt on Windows 7

    Not sure why you still want to work with Windows 7 which reached end of life long time ago?
    As far as I know it does not even get security fixes anymore?



  • I use Windows 10 also, for sure. But at least on 2 occasions when I went to get a coffee, coming back and finding Windows 10 has restarted my machine without my consent, does not help. Re. security updates, you are correct. So I make sure my PC cannot be reached from internet, does not have any email capability and only surf to qt.io and google.



  • @hskoglund said in Qt Creator 6.0.1 and Qt 6.2.2 running on Windows 7:

    Windows 10 has restarted my machine without my consent

    This can be prevented, you know. There are settings for that.



  • @artwaw
    Maybe, but Win 10 does tend to have a "I know better than you" attitude, compared to Win 7 ;-)


  • Moderators

    @hskoglund said in Qt Creator 6.0.1 and Qt 6.2.2 running on Windows 7:

    So I make sure my PC cannot be reached from internet, does not have any email capability and only surf to qt.io and google.

    lol. Henry, I'ven't taken you as one of them tinfoil-hat people ... ;)



  • Don't worry @kshegunov , no hat for me. But those ancient Windows installations you have to treat gently so they don't break :-)



  • Thank you,you save me!



  • @hskoglund : There are Qt 5 based builds of Qt Creator 6.0.x on https://download.qt.io/snapshots/qtcreator_qt5/6.0/



  • @andr Thank you! I know I've seen that link before but couldn't find it.

    If those Qt5-flavored builds of Qt Creator keep coming, that'll solve almost all of my issues with Qt and Windows 7, except if I want to build and test a Qt6 app. In that case my patches above could still be useful :-)


Log in to reply