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

BSOD happened when 微信 launched in a sandbox #1483

Closed
StrollStars opened this issue Dec 27, 2021 · 5 comments
Closed

BSOD happened when 微信 launched in a sandbox #1483

StrollStars opened this issue Dec 27, 2021 · 5 comments
Labels
BSOD Critical error screen crash dump Dump file attached for a detailed analysis fixed in next build Fixed in the next Sandboxie version Regression A Sandboxie build broke compatibility, it was working before

Comments

@StrollStars
Copy link

Describe the problem
When 微信 launched in a sandbox, BSOD happened.

To Reproduce
Steps to reproduce the behavior:

  1. Double click to lauche WeChat.exe.
  2. BSOD happened.

Screenshots
No

Expected behavior
The 微信 launched in a sandbox successfully.

System details and installed software

  • System: Windows 10 Home 21H1 64-bit
  • Sandboxie-Plus-x64: 1.02 and 1.03 have no problem, but 1.04 and 1.05 have the problem.

If you had a compatibility issue or a crash

Additional context
No.

@isaak654 isaak654 added Log available Trace log attached for a detailed analysis Regression A Sandboxie build broke compatibility, it was working before crash dump Dump file attached for a detailed analysis and removed Log available Trace log attached for a detailed analysis labels Dec 27, 2021
@DavidXanatos
Copy link
Member

Do you have HVCI enabled and does EnableWin32kHooks=n solve the issue?

@isaak654
Copy link
Collaborator

isaak654 commented Dec 27, 2021

For your information, HVCI is labeled as "Memory integrity" in the Windows Security app and it can be accessed in this way:
Settings > Update & Security > Windows Security > Device security > Core isolation details > Memory integrity

@StrollStars
Copy link
Author

@isaak654 "Memory integrity" disabled can solve the problem, but I prefer what @DavidXanatos said.
Thank you very much.

@isaak654
Copy link
Collaborator

The HVCI fix is already on 1.0.6, thanks for the confirmation.

@isaak654 isaak654 added already fixed Already fixed at some point fixed in next build Fixed in the next Sandboxie version and removed already fixed Already fixed at some point labels Dec 28, 2021
@StrollStars
Copy link
Author

StrollStars commented Jan 1, 2022

@isaak654 Thank you, it works even without EnableWin32kHooks=n.

@isaak654 isaak654 added the BSOD Critical error screen label Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BSOD Critical error screen crash dump Dump file attached for a detailed analysis fixed in next build Fixed in the next Sandboxie version Regression A Sandboxie build broke compatibility, it was working before
Projects
None yet
Development

No branches or pull requests

3 participants