GlassWire fails to start – Qt platform plugin error (“no Qt platform plugin could be initialized”)

GlassWire Help
1

Hi,

I’m facing a persistent startup issue with GlassWire on Windows.

When I run GlassWire, I immediately get a popup error saying:

“This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.”

Available platform plugins are:
minimal, offscreen, webgl, windows
(from: C:\Users\...\Python310\Lib\site-packages\PyQt5\Qt5\plugins\platforms)

Important details:

  • This error appears only when GlassWire is installed and launched

  • Reinstalling GlassWire does not fix the issue

  • I tried:

    • Clean uninstall + reinstall

    • Installing GlassWire on a different (non-system) drive

    • Restarting the system

  • I also noticed the error references PyQt5 / Python Qt plugins, even though GlassWire shouldn’t depend on my Python environment

  • Removing or disabling Python-related paths temporarily makes the error change, but I don’t want to rely on environment variable hacks

It looks like GlassWire is picking up Qt plugins from my system Python installation instead of its own bundled Qt runtime, causing a conflict.

Questions:

  1. Does GlassWire rely on Qt internally, and can it conflict with an existing Python/PyQt installation?

  2. Is there a way to force GlassWire to use its own Qt platform plugins only?

  3. Are there known conflicts between GlassWire and PyQt5 / Python 3.10+ on Windows?

Any guidance or official fix would be appreciated.
Thanks.

2

It certainly sounds like a conflict. GlassWire devs are currently working on updating to Qt6 so hopefully they will address this at the same time.

1 Like
3

It looks that PyQt5 path is in the your PATH env var.

You can create “run-gw.bat” script with custom PATH and use it to launch the GW.

4

GlassWire does use Qt for its UI framework. As @ittroll mentioned, we will soon be in the process of updating the framework to the latest version. I’ll share your scenario and questions with our engineering team so that they are aware and get back to you with any info that may be helpful.

1 Like
5

Hi @dimuth_sakya, thanks for your patience.

I shared the details you provided with our development team, and they were able to investigate further. They’ve identified the root cause of the issue and plan to include a fix in the next version we release.

In the meantime, you can use the following workaround.

  1. Create a file named glasswire.bat on your Desktop.

  2. Open the file and add the lines below. If GlassWire is installed in a non-standard location, replace C:\Program Files (x86)\GlassWire with the correct path.

  3. Save the file and double-click it to run GlassWire.

@echo off

set QT_PLUGIN_PATH=C:\Program Files (x86)\GlassWire
set QT_QPA_PLATFORM_PLUGIN_PATH=C:\Program Files (x86)\GlassWire\platforms

start "" /d "C:\Program Files (x86)\GlassWire" "GlassWire.exe"

Please let us know if this workaround helps, and thank you again for reporting the issue.

Thanks,
Huda

6

Maybe these paths can be configured by “qt.conf” file?

7

I posed this question to our development team and their response is that the qt.conf file we use is built into the GlassWire executable itself. It isn’t a separate file that you can drop next to the exe, so adding your own qt.conf beside GlassWire.exe won’t change how Qt loads its plugins.

This issue will be fixed in the next version of GlassWire.

3 Likes