Solved: Entropia Launcher blank / ClientLoader invisible (caused by 4t Tray Minimizer)

Information Content Releases/VU Info
,
1

UPDATE (2026-08-07):

I reported the issue to the developer of 4t Tray Minimizer and provided a full WinDbg dump and analysis.

The issue has now been fixed in 4t Tray Minimizer 6.08.

Official changelog:

Fixed an issue that could cause Google Chrome 151 and other Chromium-based applications, including Microsoft Edge, to crash.

Thanks to Steve Ritchie and the 4t Niagara Software team for the incredibly fast investigation and fix.

Hi everyone,

After spending many hours troubleshooting this issue, I wanted to post the solution in case it helps someone else.

Symptoms

On Windows 10, the Entropia launcher would not display correctly.

  • ClientLoader.exe starts successfully.

  • The process remains running.

  • The launcher window never appears (or only shows a tiny blank/invisible window).

  • No error message is displayed.

  • The game cannot be launched.

What I tried

Before finding the real cause, I tried almost everything:

  • Reinstalled Microsoft Edge

  • Reinstalled Microsoft Edge WebView2 Runtime

  • Repaired Windows with DISM

  • Ran sfc /scannow

  • Repaired the Windows component store

  • Reinstalled Visual C++ Redistributables

  • Process Monitor

  • Process Explorer

  • WinDbg crash dump analysis

None of these solved the issue.

The actual cause

The problem turned out to be 4t Tray Minimizer.

More specifically, its injected DLL:



ShellEh6055x64.dll

During WinDbg analysis, the crash occurred inside:



msedgewebview2.exe

with:



Exception code:
0xc0000005 (Access Violation)

Faulting module:
ShellEh6055x64.dll

The DLL is injected while WebView2 creates its window and causes the launcher to fail before it can render.

Solution

Simply exit 4t Tray Minimizer completely.

As soon as I closed it:

  • Edge worked normally.

  • WebView2 applications worked normally.

  • The Entropia launcher opened correctly.

  • The issue became 100% reproducible (running 4t caused the problem every time).

Additional information

My system:

  • Windows 10 Pro 22H2 (19045.4651)

  • Microsoft Edge 151.0.4129.59

  • Microsoft Edge WebView2 Runtime 151.0.4129.59

  • 4t Tray Minimizer 6.07 (latest version)

I have already contacted the 4t Tray Minimizer developer with the WinDbg findings so they can investigate the compatibility issue.

Hopefully this saves someone else several hours of troubleshooting.

P.S. If you’re using any software that injects itself into other applications (window managers, shell extensions, tray utilities, etc.), try disabling it before reinstalling Windows or WebView2. It may save you a lot of time.

P.S.2: If needed, I can provide the WinDbg dump and analysis to the developers or to anyone trying to reproduce the issue.

2

​I contacted the 4T Tray Minimizer devs, and they created a new version that solved this incompatibility in just one day.

​Best regards

Manuel

3

Wow, gratz for getting it fixed! Do you have more knowledge about this?

I’m running the game using Lutris on Linux and starting the Client Loader is the first mini-game and it may take a few attempts to actually see the Client Loader.

It’s as you described, after starting it, it takes a bit and parts of the screen look somewhat as if something is on top of it with some transparency. Also every even-numbered attempt the loader closes within two seconds, so I only have the odd-numbered attempts.

It would be really cool if the developer could publish the low-level cause of the issue, so that maybe someone in the Wine-area can take a look.

4

Thanks!

Unfortunately, I don’t know the exact low-level fix. The developer only asked me for the full WinDbg dump and analysis, and after reviewing them they released version 6.08 the next day.

From the debugging I performed, what I can say with confidence is:

  • The crash occurred inside ShellEh6055x64.dll (part of 4t Tray Minimizer).

  • The affected process was msedgewebview2.exe (Microsoft Edge WebView2), not Entropia itself.

  • The failure happened during the very early initialization of the Chromium/WebView2 window, before the launcher could render.

  • Closing 4t Tray Minimizer immediately fixed the problem, and I was able to reproduce it 100% of the time.

After I sent the dump to the developer, they investigated it and released version 6.08 within a day.

The official changelog says:

“Fixed an issue that could cause Google Chrome 151 and other Chromium-based applications, including Microsoft Edge, to crash.”

So it looks like this was actually a Chromium/WebView2 compatibility issue rather than something specific to Entropia.

Your Wine/Lutris issue sounds visually similar, but I wouldn’t assume it’s the same root cause. In my case the crash was caused by a native Windows DLL injected into the Chromium process. Under Wine there are additional layers that could produce similar symptoms for completely different reasons.

If the developer ever shares the technical details of the fix, I’ll gladly update this thread.

5

Doesn’t Steam on Linux takes care of all this?

6

Maybe, but I don’t want to install Steam just for that. I mean besides that the game works fine, I guess.

1 Like
7

I just play with original client, not with Steam and i font know if u have the same problem with Steam installed.