Thorium Browser shows an error about Gdilnit when run in a Sandbox

[Dyras]

Describe what you noticed and did

1. Install Thorium Browser. I installed it using winget with a --scope for current user only:
   winget install Alex313031.Thorium --scope user
2. Make thorium.exe run in a new sandbox. Sandbox type: Default. I named mine Thorium
3. Start Thorium. Notice how it now delivers a message:

How often did you encounter it so far?

Whenever I run Thorium in a Sandbox

Expected behavior

It should work just fine, just like Brave and other browsers do.

Affected program

Latest Thorium

Download link

https://github.com/Alex313031/Thorium-Win/releases

Where is the program located?

The program is installed only outside the sandbox.

Did the program or any related process close unexpectedly?

No, not at all.

Crash dump

No response

What version of Sandboxie are you running now?

1.13.2 64-bit

Is it a new installation of Sandboxie?

I recently did a new clean installation.

Is it a regression from previous versions?

No response

In which sandbox type you have this problem?

In a standard isolation sandbox (yellow sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

What is your Windows edition and version?

Windows 10 Edu, all updates

In which Windows account you have this problem?

A Microsoft account (Administrator).

Please mention any installed security software

Malwarebytes Anti-Exploit, with no shields that should affect Thorium

Did you previously enable some security policy settings outside Sandboxie?

No response

Trace log

No response

Sandboxie.ini configuration

Shouldn't play a role but I'll add it if you feel otherwise.

[bastik-1001]

(Just as additional information: This browser is based on Chromium.)

[offhub]

I did not encounter a black screen, but the GdiInit message appeared in the green box.

[Dyras]

The black screen only occurs when "Add sandboxed processes to job objects" is enabled, strangely enough. The same thing happens with Edge so I'm gonna exclude that from this issue.