Closed Sqrlly closed 1 year ago
Update. I had downloaded from the https://sandboxie-plus.com/downloads/ site which showed 1.0.8 as the newest. I have now gotten 1.0.10 direct from github and can confirm the issues are exactly the same. This did also occur in 0.9.8d, which promoted me to update (to 1.0.8). So not a regression but something that changed in Chrome that bypasses the Sandboxie protection.
i don't have hulu, do thay offer free videos? or is teh issue present with netflix? or with that else?
Try disabling Win32 hooks and rebooting
Yes I had this happen with all of Hulu, Netflix, or Youtube TV (not regular Youtube though).
As for the hooks do you mean to set 'EnableWin32kHooks=y' to 'n' instead? If so, I did that and still get the messages, but screen capture works again (though guessing because it probably results in disabling hardware acceleration).
im getting SBIE2203, Msgid: 12 [C0000024] while running a screen capture software, spamming constantly on "touch"(task switch, window focus switch?). and if i start the capture, a bunch of messages. updated the other day to sbie+ v1.0.20. i did not had that in the previous version. cant remember which one it was, but it was beyond v1.0.10. maybe .17. i dont have problem with the sc program. it seem to be working normally. i have the experimental win32k hook enabled. tried to disable it, still the same. restarted sbie service. did not reboot. will update, if it changes on next reboot. ... reboot did not help. still gives the issue, with the hook disabled. ... it seems like the old version of the screen capture program works fine, without making error messages. its possible that the issue is in some new and buggy technique that has been implemented at large. its also possible, that the new version was giving messages all along[^1]. [^1]:its a lot of mess all around me for the last 5 years. i cant focus on yet another annoyance. my government is repressing me 24/7/365
As far as I can tell this is intended behavior of the chromium web browser, also (correct me if I'm wrong) the change happened with a chromium update not with a new sandboxie build. So we did not break anything, thay broke it on purpose, the behaviorue is the same when running unsandboxed, hence I'll Close this issue without a fix as explained else ware sandboxie is not an Anti DRM tool.
Also it seams that with firefox OBS studio can still capture netflix just fine so I would recommend to use to a more free browser then chrome to resolve this issue.
What happened?
Yesterday the Chrome web browser updated for me to Version 98.0.4758.82 64-bit. Since then when I play videos on services like Hulu, Netflix, or Youtube TV I get the following errors:
This is with:
The video still plays correctly, but the errors come up each time a video is played. And it now once again blackens the video area when doing a screen capture (Win-Shift-S or PrintScrn, etc.) which the sandbox had prevented prior to the Chrome update.
Regular Youtube does not appear to be generating the error so far.
To Reproduce
Expected behavior
To not get the errors and for Sandboxie to prevent chrome from interferring with my screen capture.
What is your Windows edition and version?
Windows 10 Home 21H2 19044.1466
In which Windows account you have this problem?
A local or Microsoft account without special changes.
Please mention any installed security software
Windows Defender provided with Windows.
What version of Sandboxie are you running?
Sandboxie-Plus v1.0.8
Is it a regression?
No response
List of affected browsers
Chrome version 98.0.4758.82 64-bit
In which sandbox type you have this problem?
In a Standard isolation sandbox (yellow sandbox icon).
Is the sandboxed program also installed outside the sandbox?
Not relevant to my request.
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
Sandboxie-Plus.ini configuration (for Plus interface issues)
No response