Noobie tutorial and 5.11 to 5.12 upgrade
-
It hates me... lol.. Since everything was fine on the VM install, I decided to change the main system. Went out and renamed the other VS folders back to their original names (just to keep Microsnot happy), removed the full QT package to start clean. Rebooted, disabled the AV (just in case... never reported problems with the other installs but, you know... fingers crossed right?) then ran the installer again. Only selected the mingw option, plus the default tools (same as I did on the VM).. got to the end and gave this error.
Ignored it.. said it was finished. Loaded QT, went to build the sample text editor (same as on the VM, which worked) and it failed with this showing in the Application Output screen:14:58:17: Starting C:\Qt\Examples\Qt-5.12.0\widgets\mainwindows\build-application-Desktop_Qt_5_12_0_MinGW_64_bit-Debug\debug\application.exe...
qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.*sigh.. While I could just do all this in the VM side of things, I like to go full screen on the main system (22 inch monitor) and then use the second screen (32 inch tv monitor) for docs, help files etc... and of course I can't drag those out of the VM to the other screen.
Not sure why something that should be so simple is causing so many problems. And thanks for the grid link, I'll certainly check that out. :)
Gary
-
It hates me... lol.. Since everything was fine on the VM install, I decided to change the main system. Went out and renamed the other VS folders back to their original names (just to keep Microsnot happy), removed the full QT package to start clean. Rebooted, disabled the AV (just in case... never reported problems with the other installs but, you know... fingers crossed right?) then ran the installer again. Only selected the mingw option, plus the default tools (same as I did on the VM).. got to the end and gave this error.
Ignored it.. said it was finished. Loaded QT, went to build the sample text editor (same as on the VM, which worked) and it failed with this showing in the Application Output screen:14:58:17: Starting C:\Qt\Examples\Qt-5.12.0\widgets\mainwindows\build-application-Desktop_Qt_5_12_0_MinGW_64_bit-Debug\debug\application.exe...
qt.qpa.plugin: Could not find the Qt platform plugin "windows" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.*sigh.. While I could just do all this in the VM side of things, I like to go full screen on the main system (22 inch monitor) and then use the second screen (32 inch tv monitor) for docs, help files etc... and of course I can't drag those out of the VM to the other screen.
Not sure why something that should be so simple is causing so many problems. And thanks for the grid link, I'll certainly check that out. :)
Gary
-
Yeah, strange indeed. Not being a developer of QT I cant begin to ponder on where the issue is, and there seems to be a lot of issues. As for the VM, it's workstation 12... a net search shows that dual monitors can be done. Tried a couple of the 'tricks' with limited success. It was getting late, tired.. frustrated, so I just put it all away.
Thanks for the tips and suggestions.
Gary
-
Yeah, strange indeed. Not being a developer of QT I cant begin to ponder on where the issue is, and there seems to be a lot of issues. As for the VM, it's workstation 12... a net search shows that dual monitors can be done. Tried a couple of the 'tricks' with limited success. It was getting late, tired.. frustrated, so I just put it all away.
Thanks for the tips and suggestions.
Gary
Hi @cmwDev,
I know these days ;)
But there is hope: I found QTBUG-57983: For the reporter it helped to enable Application Experience.
Maybe you give it a further try?
-
*chuckles
I have everything "Application Experience" disabled. The actual program, every item that is referenced in task scheduler for that is disabled... Anything that I can do to stop windows from giving Microsoft any information... I have done.
MS, even in Win7, likes to send a lot of data to the home office. Even at boot time, when the computer starts and does its first DNS queries.. Besides confirming the DNS connections, it also gets additional information to 'say hello' to MS on an entire range of multiple IP's... and all of this is just to confirm that it has internet access. Its what takes the ! mark out of the internet icon. Or to some, it means that MS knows every time you boot your system.
Just saying :)
-
*chuckles
I have everything "Application Experience" disabled. The actual program, every item that is referenced in task scheduler for that is disabled... Anything that I can do to stop windows from giving Microsoft any information... I have done.
MS, even in Win7, likes to send a lot of data to the home office. Even at boot time, when the computer starts and does its first DNS queries.. Besides confirming the DNS connections, it also gets additional information to 'say hello' to MS on an entire range of multiple IP's... and all of this is just to confirm that it has internet access. Its what takes the ! mark out of the internet icon. Or to some, it means that MS knows every time you boot your system.
Just saying :)
@cmwDev I guess you're on the wrong O/S then. I've went away from MS 20 years ago. Only at work I'm forced to use it - and its getting worse with every release.
Just saying, if MS blocks the installer, we cannot do much. Sorry.
-
I don't think MS is 'blocking' the install. The mingw version works fine on the clean install of Win7 on the VM. It does fail, with the errors shown when I do it on the main machine.
The install on the main machine "worked" when I had the MSVC side installed, it just did that annoying thing with running that vctip part as a service of some sort. I had expected that when I nuked the main machine install and re-did the install with just mingw it would work.
It did not.
-
I don't think MS is 'blocking' the install. The mingw version works fine on the clean install of Win7 on the VM. It does fail, with the errors shown when I do it on the main machine.
The install on the main machine "worked" when I had the MSVC side installed, it just did that annoying thing with running that vctip part as a service of some sort. I had expected that when I nuked the main machine install and re-did the install with just mingw it would work.
It did not.
-
sorry for the delay, I wasn't expecting more replies :)
Yes, I did, twice. It linked to another forum, and I got a little lost but the second time I viewed it I spent time doing more in depth reading.
So I changed the Application Experience service from disabled to automatic, did a reboot just to be safe. Nuked the previous new install of the latest QT (3.0.6 I believe), ran the installer again. I checked off the mingw, and the 2 debug items. This time, I also went down to the Tools section of the installer, and checked the same mingw item there.
Ran the install... no errors. Ran QT, did a sample app build (notebook) and ran it, no problems. Closed QT. Went back into services, stopped Application Experience, disabled the service. Ran QT again, loaded the 'contacts' sample app, ran it.. no problems.
Crazy that ... can't say much more. Other than I don't have to worry about running and having the dual screen hassles with VMWare. So, thanks!
Shakes head at Microsoft... *mutters
Gary
-
sorry for the delay, I wasn't expecting more replies :)
Yes, I did, twice. It linked to another forum, and I got a little lost but the second time I viewed it I spent time doing more in depth reading.
So I changed the Application Experience service from disabled to automatic, did a reboot just to be safe. Nuked the previous new install of the latest QT (3.0.6 I believe), ran the installer again. I checked off the mingw, and the 2 debug items. This time, I also went down to the Tools section of the installer, and checked the same mingw item there.
Ran the install... no errors. Ran QT, did a sample app build (notebook) and ran it, no problems. Closed QT. Went back into services, stopped Application Experience, disabled the service. Ran QT again, loaded the 'contacts' sample app, ran it.. no problems.
Crazy that ... can't say much more. Other than I don't have to worry about running and having the dual screen hassles with VMWare. So, thanks!
Shakes head at Microsoft... *mutters
Gary
