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
isaak654
changed the title
Spotify program crashes with BreakoutProcess=Spotify.exe
Spotify program crashed with BreakoutProcess=Spotify.exe
Jun 9, 2023
Describe what you noticed and did
C:\Sandbox\User\DefaultBox\user\current\AppData\Local\CrashDumps
Spotify.exe: SBIE2205 Service not implemented: GdiInit.00000001
Sandboxie.ini configuration
[DefaultBox] Enabled=y RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Desktop% BorderColor=#02f6f6,on,6 Template=OpenBluetooth Template=SkipHook Template=FileCopy Template=qWave Template=LingerPrograms Template=AutoRecoverIgnore ConfigLevel=10 BoxNameTitle=n BlockNetParam=n BreakoutProcess=Spotify.exe EnableMiniDump=y
How often did you encounter it so far?
Whenever it is applied the sandbox configuration provided above.
Affected program
Spotify
Download link
https://www.spotify.com/us/download/windows/
Where is the program located?
The program is installed only inside a sandbox (NOT in the real system anyway).
Expected behavior
No crash with Spotify.exe / Sandman.exe.
What is your Windows edition and version?
Windows 10 22H2 x64
In which Windows account you have this problem?
A local account (Administrator).
Please mention any installed security software
Microsoft Defender Antivirus
What version of Sandboxie are you running?
Sandboxie Plus 1.9.7 x64
Is it a new installation of Sandboxie?
I recently did a new clean installation.
Is it a regression?
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.
Did you previously enable some security policy settings outside Sandboxie?
No response
Crash dump
No response
Trace log
No response
The text was updated successfully, but these errors were encountered: