global policy & 4.x & SBIE2205

[btm]

...first I'll start by saying I have been on 3.76 for some time now for reasons I've covered elsewhere. As it happens one of those problems was being worked on in the newest MBAE experimental build and I wanted to test it out. Anyway, I updated to 4.14 on my live system and even after resetting the sandboxie.ini I am plagued with a particular problem attempting to sandbox any program. Tested on a clean VM and sandboxie didn't throw any errors. I'm currently proceeding on the idea that it involves changes I've made with gpedit.msc between the last time I was testing a 4.x build and now as not much else has changed. It's an access denied error but so far I can't figure out which policy might be interfering.

SBIE2205 Service not implemented: Win32Init.5 (00000005)
SBIE2205 Service not implemented: Win32Init.5 (00000005)
SBIE2205 Service not implemented: Win32Init.5 (00000005)
SBIE2203 Failed to communicate with Sandboxie Service: *GUIPROXY_00000001 - SandboxieRpcSs.exe [FF000005]

Obviously it was working fine with 3.76 (which I will be once again reverting to as mbae isn't quite working 100% with 4.x still) but I would like to have this figured out on my end before I make the switch to 4.x permanently.

I know it's a shot in the dark without access to my changes but I'm hoping there might be someone who has seen this before. I am considering resetting back to default but I'd really rather not spend hours going over them one by one again and testing to figure it out on my own. Any clues/ideas would be great.

Windows 7 x64

Well it turns out it may not have been related to the global policy changes after all. I found that when I set up the program to run as a different user (C:\Windows\System32\runas.exe /user:) the error popped up again. I imagine it has something to do with the "ANONYMOUS LOGON" shift in the 4.x line. No worries though, all is working great now.


I finally had some spare time so I went through and tested changes one at a time and finally figured out the cause. When I removed Users from "Bypass traverse checking" in User Rights Assignment and attempted to launch a forced program via runas I got this error once again. Adding Users back allows me to use runas to launch the program and Sandboxie 4.x does not throw the SBIE2205 Win32Init.5 error any longer.