Launching on Windows 7 fails with an error message stating that api-ms-win-core-console-l2-1-0.dll is missing. This library is apparently part of the Windows 10 Universal C Runtime, which in theory should also be present on Windows 7 after applying the SP1 update. Still doesn't work though. Visual Studio 2017, 2019 and using the v140 platform toolset makes no difference.
Suspicion: Linking Qt statically might cause the problem. Not sure why, but it's just not meant to be. It never works as expected. So test this first and maybe keep copying the Qt dlls into the installation directory via windeployqt, even though that's slightly retarded.
Official Windows 7 support ends in January 2020, so it won't be long until we can think about also dropping it. Preferably together with the 32 bit version.
Launching on Windows 7 fails with an error message stating that
api-ms-win-core-console-l2-1-0.dll
is missing. This library is apparently part of the Windows 10 Universal C Runtime, which in theory should also be present on Windows 7 after applying the SP1 update. Still doesn't work though. Visual Studio 2017, 2019 and using the v140 platform toolset makes no difference.Suspicion: Linking Qt statically might cause the problem. Not sure why, but it's just not meant to be. It never works as expected. So test this first and maybe keep copying the Qt dlls into the installation directory via
windeployqt
, even though that's slightly retarded.Official Windows 7 support ends in January 2020, so it won't be long until we can think about also dropping it. Preferably together with the 32 bit version.