Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SBIE2203 error after Vivaldi update #821

Closed
Deadite333 opened this issue Apr 29, 2021 · 10 comments
Closed

SBIE2203 error after Vivaldi update #821

Deadite333 opened this issue Apr 29, 2021 · 10 comments
Labels
fixed in next build Fixed in the next Sandboxie version HW acceleration Hardware acceleration issues

Comments

@Deadite333
Copy link

Deadite333 commented Apr 29, 2021

With todays Vivaldi update Sandboxie can no longer start the browser:

SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 15 - WerFault.exe [FF000000]

De- and reinstalled, tried a previous Sandboxie version, to no avail.

@isaak654
Copy link
Collaborator

A similar issue is under investigation: #795
Did you try to turn off hardware acceleration outside of the sandbox, as workaround?

@oximeter
Copy link

This happens after the Vivaldi update to Chrome 90. Hardware acceleration is disabled already. Chrome 89 branch works.
Edge is not affected by the Chrome 90 issue, just Vivaldi
See here
https://www.wilderssecurity.com/threads/sandboxie-plus-0-7.436454/page-10#post-3003603

@isaak654
Copy link
Collaborator

isaak654 commented Apr 29, 2021

There are similar reports for Edge, Chrome, Brave updated to v90... the only difference is that disabling hw acceleration doesn't always work (as workaround) and some browsers can't start for just some users, rather than all users.

EDIT: tried last version of Vivaldi on a VM, it's broken here too on 0.7.4. Another issue related to v90 update.

@NotepadPlusUser
Copy link

For what it's worth, here are the 12 lines of the error message that Sandboxie-plus 0.7.4 generated this morning when I tried to open Vivaldi 3.8.2259.37 (with Chrome/90.0.4430.95) in the DefaultBox. There seemed to be problems with Edge 90.0.818.51. I'm working on a 64-bit desktop with Windows 10 20H2 (19042.928).


WerFault.exe (15348): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (15348): SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 15 - WerFault.exe [FF000000]
WerFault.exe (4156): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (4156): SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 15 - WerFault.exe [FF000000]
WerFault.exe (12812): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (12812): SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 15 - WerFault.exe [FF000000]
WerFault.exe (22316): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (22316): SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001; MsgId: 15 - WerFault.exe [FF000000]
WerFault.exe (15348): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (4156): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (12812): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1
WerFault.exe (22316): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1


@bighippo999
Copy link

I'm getting the same kind of errors but only 7 lines worth.
I did manage to start Vivaldi though:
Right click sandbox> Run Sandboxed > Run Any Program > type (without quotes) "vivaldi.exe --no-sandbox"
Hopefully it works for you too until it's fixed in an update.

@NotepadPlusUser
Copy link

Thanks @bighippo999. I have a button to turn disable_forcing on and off quickly, so no worries running Vivaldi unsandboxed. But it's a great nuisance, as it was a few months ago when a previous change in Chrome similarly caused Vivaldi not to run in Sandboxie.

Hopefully the next version of Sandboxie-plus will again make the necessary adjustment.

APOLOGIES: I made a typo in my report above. I meant to type:
'There seemed to be NO problems with Edge 90.0.818.51.'

I also failed to report that turning hardware acceleration on and off seems to make no difference to these results in either Edge or Vivaldi.

@isaak654
Copy link
Collaborator

isaak654 commented May 5, 2021

Someone renamed vivaldi.exe to firefox.exe with success as workaround here.

@Deadite333
Copy link
Author

Thanks, especially for the suggested workarounds.

It's pretty weird, but the firefox-method works well, nice find.

@FredB750
Copy link

FredB750 commented May 7, 2021

I experienced trouble with all 64 bit chrome v90+ browsers. The 32bit versions seem to run OK.??
Would like to hear if anyone else has found the same to be true?

@DavidXanatos
Copy link
Member

the issue will be fixed in the next build,
till then you can use this patched SbieDll.dll: https://xanasoft.com/Downloads/SbieDll_5.49.8a.zip

@DavidXanatos DavidXanatos added the fixed in next build Fixed in the next Sandboxie version label Jun 4, 2021
@isaak654 isaak654 added the HW acceleration Hardware acceleration issues label Jan 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in next build Fixed in the next Sandboxie version HW acceleration Hardware acceleration issues
Projects
None yet
Development

No branches or pull requests

7 participants