You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installation of latest DiscordSetup.exe inside a Standard Isolation Sandbox (through sandboxed Windows Explorer) works and Discord installs itself succesfully. During the installation, two error messages appear: "gpu_encored_helper.exe: SBIE2205 Service not implemented: ConsoleInit (C0000D4)". I don't know if this is relevant to the main problem. Picture attached:
After installation, Discord opens itself automatically for the first time succesfully. After exiting Discord completely through the tray icon (confirmed through Sandboxie that all Discord processes are closed), any opening of the Discord application fails after like a second from clicking. Discord updater window shows and the updater process shows in the Sandboxie view. Then the updater window exits abruptly and updater processes close themselves.
Discord can't therefore open itself after exiting at least once, while installed completely inside the Standard Isolation Sandbox. Sandboxie blocks something during the opening update check of Discord.
I disabled Discord's hardware accelleration during the first open after install, but it doesn't seem to be the culprit. Discord's dll injection for screen sharing was also disabled before first exit.
This initially started with an established Discord installation, which probably means either something in the Discord Updater, or Sandboxie, changed recently (last month or so).
I also tried to switch to virtualization scheme v2, but it didn't help.
Describe what you noticed and did
Installation of latest DiscordSetup.exe inside a Standard Isolation Sandbox (through sandboxed Windows Explorer) works and Discord installs itself succesfully. During the installation, two error messages appear: "gpu_encored_helper.exe: SBIE2205 Service not implemented: ConsoleInit (C0000D4)". I don't know if this is relevant to the main problem. Picture attached:
After installation, Discord opens itself automatically for the first time succesfully. After exiting Discord completely through the tray icon (confirmed through Sandboxie that all Discord processes are closed), any opening of the Discord application fails after like a second from clicking. Discord updater window shows and the updater process shows in the Sandboxie view. Then the updater window exits abruptly and updater processes close themselves.
Discord can't therefore open itself after exiting at least once, while installed completely inside the Standard Isolation Sandbox. Sandboxie blocks something during the opening update check of Discord.
I disabled Discord's hardware accelleration during the first open after install, but it doesn't seem to be the culprit. Discord's dll injection for screen sharing was also disabled before first exit.
This initially started with an established Discord installation, which probably means either something in the Discord Updater, or Sandboxie, changed recently (last month or so).
I also tried to switch to virtualization scheme v2, but it didn't help.
Trace log URL authentication:
username: troubleshooter
password: 8vuL82tZgzG4o5MfdXmn6xMNfN
How often did you encounter it so far?
Discord fails to open every time after the first exit of Discord.
Affected program
Discord Windows Desktop app, latest
Download link
https://discord.com/api/downloads/distributions/app/installers/latest?channel=stable&platform=win&arch=x86
Where is the program located?
The program is installed only inside a sandbox (NOT in the real system anyway).
Expected behavior
Discord should open normally after the first exit of Discord.
What is your Windows edition and version?
Windows 10 Pro 22H2 64-bit
In which Windows account you have this problem?
A local or Microsoft account without special changes.
Please mention any installed security software
Eset NOD32 Antivirus, Windows Firewall
What version of Sandboxie are you running?
Sandboxie Plus 1.9.2 64-bit
Is it a new installation of Sandboxie?
I recently did a new clean installation.
Is it a regression?
Bug appears in multiple versions.
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.
Did you previously enable some security policy settings outside Sandboxie?
No relevant security policies are enabled.
Crash dump
No response
Trace log
https://axolul.kapsi.fi/tracelogsforsandboxie/
Sandboxie.ini configuration
The text was updated successfully, but these errors were encountered: