Violation of LSA Policy

mingya

Member
2 problems found:
(1) sandboxie caused the following and machine rebooted as a result:
An anonymous session connected from ##### has attempted to open an LSA policy handle on this machine. The attempt was rejected with STATUS_ACCESS_DENIED to prevent leaking security sensitive information to the anonymous caller.
The application that made this attempt needs to be fixed. Please contact the application vendor.
(2) Tried v1.17.6, still could not open web pages from inside app, tried it with doomsday, also cannot, it hanged the sandboxie instance. The instance is emulating admin rights.

Please advise how to workaround this without disabling security, or suggest a fix method.

In addition, how I can run 2 versions of sandboxie on the same device that points to different sandbox folder path. I tried placing them in different folders, sandbox1 and sandbox2, running portable mode. Inside each folder is sandboxie-plus folder and sandbox folder (instance content), but somehow they always point to the same sandbox path. Please note, I want to keep the old working on, while trying the new one before replacing.
 
(1) sandboxie caused the following and machine rebooted as a result:
On what system did this occur? (E.g. Windows 11, 25H2)

In addition, how I can run 2 versions of sandboxie on the same device that points to different sandbox folder path. I tried placing them in different folders, sandbox1 and sandbox2, running portable mode. Inside each folder is sandboxie-plus folder and sandbox folder (instance content), but somehow they always point to the same sandbox path. Please note, I want to keep the old working on, while trying the new one before replacing.

@DavidXanatos please advice, if that is supported. It appears like the portable causing more problems than it does good. Maybe the installer should show some information about the portable version, when the user selects it.
 
Pardon the delay in answering. I got into an accident that required some extensive resting
On what system did this occur? (E.g. Windows 11, 25H2)
Windows 11 Pro, 25H2

Once I manage to stay online a bit longer, I'll try to run the dual portable so I could do testing. I'd really like to keep my version up to date. Right now I can only use version 1.1.73
 
Best wishes for your recovery.

I was not aware that this was also a problem on recent versions of Windows.
I never used any other windows version. This device has always been Windows 11 Pro, 25H2 + some minor security updates

Thanks for your wishes. I'm at 70%, able to sit and work a bit.

FYI, while I was updating a network driver, I found Windows Hello and Windows Live login caused reboot on Sandboxie-Plus. I disabled them, turned to local login, that reboot stopped. Still need to test the latest version on accessing web page from inside the app, I'll use doomsday for testing, since they have a bunch of heavy loaded web pages. Will keep you updated.
 
Tested the latest release 1.17.9 on the same windows version, using doomsday. Still unable to access web pages right from the start, login page. Also the LSA policy appeared again, even with local login (no Windows Hello and Windows Live Login).
There had to be a specific difference between 1.17.3 and the subsequent later versions. I tried a few times with different general settings on the compatibility, it seems to trigger LSA Policy violation. The difference is, without Windows Hello and Windows Live Login present, it is triggered when the app inside the instance starting.
 

Attachments

  • sandboxie-bug-2026-06-30-055205-1179-cannot-access-web.png
    sandboxie-bug-2026-06-30-055205-1179-cannot-access-web.png
    70.1 KB · Views: 4
I get the same error in Event Viewer with SBIEPLUS 1.18.0, however for the time being from what I can tell both Chrome and FireFox run fine from within the sandbox.

An anonymous session connected from XXXX has attempted to open an LSA policy handle on this machine. The attempt was rejected with STATUS_ACCESS_DENIED to prevent leaking security sensitive information to the anonymous caller.
The application that made this attempt needs to be fixed. Please contact the application vendor. As a temporary workaround, this security measure can be disabled by setting the \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\TurnOffAnonymousBlock DWORD value to 1.
This message will be logged at most once a day.

Event ID 6033
Source LSA (LsaSrv)

OS: 25H2 as well.
 
FYI, I have just confirmed the problem.
It seems changes introduced in newer Sandboxie-Plus versions starting after v1.1.73 alter how sandboxed applications interact with embedded browser components, launchers, or web-based authentication systems, and therefore expose compatibility problems.

For example, v1.1.74 (corresponding to 5.72.4 in the newer numbering scheme) introduced additional Electron/WebView compatibility handling. These changes may have introduced compatibility issues for applications relying on embedded browsers, WebView components, or launcher-based workflows.
 
Back
Top