Komet
This application failed to start because no Qt platform plugin could be initialized
Describe the bug When trying to start the latest version of MediaElch on Windows 11 I'm getting the error: This application failed to start because no Qt platform plugin could be initialized
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error / Crash
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
MediaElch Version:
- [ ] 2.12.1-dev (nightly)
- [ x] 2.12.0 (stable)
Operating System:
- [ x] Windows
- [ ] macOS
- [ ] Linux (distribution: .)
Additional context Add any other context about the problem here.
This error appeared on my notebook. I then istalled ME on my desktop and it worked. So obviously something else on my NB causes this.
Do you also use Windows 11 on your desktop?
I only recently installed Windows 11 in a virtual machine. I'll try it out.
Just to be sure: You're using the version for "Windows 10 or later" on both systems, right? :)
Yes, Windows 11 on both PCs and yes Version for Windows 10 or later on both as well.
Thanks. I am not able to reproduce your issue, yet. Normally, this may be due to a *.dll file missing, but then I should notice it as well. Do you have any Anti-Virus software installed? Maybe changed some settings regarding DLL loading? :)
I'm using the Windows 11 integrated Anti-Virus software. Also no changes regarding DLL loading. This is really strange. One question: I understand that ME includes the Qt runtime, correct? So there is nothing else required on the PC that needs to be installed in addition?
So there is nothing else required on the PC that needs to be installed in addition?
Yes, MediaElch uses Qt 6.x for Windows. There shouldn't be anything missing. You don't happen to have different Windows flavors, do you? Like Home Edition vs Professional? If I remember correctly, there were differences for Windows 7 a few years ago 😄
I'm using Windows 11 Pro 24H2 on both systems. I suppose that some other software that is installed on the notebook causes this issue. Its difficult to find out but if I find out I'll let you know.