[Chromium] NW.js x64 (v0.40.0-beta1 and newer) issue with Sandboxie while NW.js x32 works fine

[RandomGOTI]

Describe what you noticed and did

nwjs has stopped working

Steps

1. Try to launch sandboxed in standard isolation or app compartment
2. See nwjs error

How often did you encounter it so far?

No response

Affected program

nwjs x64

Download link

https://nwjs.io/downloads/

Where is the program located?

Not relevant to my request.

Expected behavior

nwjs launches without issue

What is your Windows edition and version?

Windows 7 Ultimate SP1 x64

In which Windows account you have this problem?

I use the built-in Administrator account.

Please mention any installed security software

None/WD disabled

What version of Sandboxie are you running?

Plus 1.2.7 x64

Is it a new installation of Sandboxie?

I just updated Sandboxie from a previous version (to be specified).

Is it a regression?

No response

In which sandbox type you have this problem?

All sandbox types (I tried them all).

Can you reproduce this problem on an empty sandbox?

I can confirm it also on an empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No response

Crash dump

No response

Trace log

No response

Sandboxie.ini configuration

No response

[RandomGOTI]

nwjs x32 is not affected by this, only x64 ¯_(ツ)_/¯

Direct dl links for testing
https://dl.nwjs.io/v0.66.1/nwjs-v0.66.1-win-x64.zip
https://dl.nwjs.io/v0.66.1/nwjs-v0.66.1-win-ia32.zip

[RandomGOTI]

monologue update
nwjs-v0.39.3-win-x64 is latest to work , nwjs-v0.40.0-beta1-win-x64 and above not working
https://dl.nwjs.io/v0.39.3/
https://dl.nwjs.io/v0.40.0-beta1/

[RandomGOTI]

Still an issue with NW.js Stable v0.70.1 03-Nov-2022 and Latest Sbie Release v1.5.3 / 5.60.3
This issue is stalled in terms of participants , closing ┐(ﾟ～ﾟ)┌

[isaak654]

✔️ nwjs-v0.70.1-win-x64.zip extracted with Windows 10 21H2 x64 + v1.5.3 x64 (standard sandbox) = nw.exe runs fine sandboxed
⚠️ nwjs-v0.70.1-win-x64.zip extracted with Windows 7 SP1 x64 + v1.5.3 x64 (standard sandbox) = nw.exe doesn't run sandboxed, it was suddenly shut down
✔️ nwjs-v0.70.1-win-x64.zip extracted with Windows 7 SP1 x64 + v1.5.3 x64 (green sandbox) = nw.exe runs fine sandboxed

---

👇

⚠️ nwjs-v0.70.1-win-x64.zip extracted with Windows 7 SP1 x64 + v1.5.3 x64 (standard sandbox) = nw.exe doesn't run sandboxed, it was suddenly shut down

For this use case, I tried to use the EnableMiniDump=y option.
Unfortunately it only created a crash dump of 0 byte (practically useless), why is that?

EDIT: During my unsuccessful attempts to find a fix through the Trace log feature, I've also got the following BSOD: #2466

[RandomGOTI]

[1.5.3 x64] Maintenance -> Stop All
Delete %windir%\Sandboxie.ini
Start Sandman
Maintenance complete 🎉
Create green box 🟩
extract and retest nwjs v0.70.1 x64

• standard 🟨 = has stopped working ❌
• green 🟩 = has stopped working ❌

The only difference is that the green box has no message logged like SBIE2224 Sandboxed program has crashed: nw.exe [DefaultBox]

• unsandboxed = no issue ✅

[isaak654]

⚠️ nwjs-v0.70.1-win-x64.zip extracted with Windows 7 SP1 x64 + v1.5.3 x64 (standard sandbox) = nw.exe doesn't run sandboxed, it was suddenly shut down

My workaround for the use case above: OpenIpcPath=nw.exe,*

I tried to refine it further by enabling the tracing option IpcTrace=*, but could not find the right IPC.

[RandomGOTI]

NW.js Stable v0.70.1 x64 03-Nov-2022 and Latest Sbie Release v1.9.7 x64
Not running in any sandbox , but runs outside 🤷‍♂️