Constant "SBIE2101 Object name not found" Errors

Question

Evening. 
 I used to use this program on Windows 7 last year without fail. Worked fine when I had to update to Windows 10. Now months ago I formatted my drive and system and installed a clean Windows 10 and installed Sandboxie 5.33.1 fresh. I can not get it to work the way I used to use it. I used to always just run it in Windows Explorer and execute programs from there. I even tried these from Sandboxie Control to no avail now. 
 I always get similar errors when I try to execute files. Whether trying to install a program or a single file (runs with just one exe file) program or game that I have had for decades, nothing ever runs and I get errors all with the same beginnings (using an old game I had for a long time as an example below): 
 SBIE2101 Object name not found: \Sessions\1\BaseNamedObjects\ISWWH_BEACON @150c@EFR-controller, error CreateEvent (C0000022) access=001F0003 initialized=1 SBIE2101 Object name not found: , error OpenProcess (C0000022) access=001FFFFF initialized=1 SBIE2314 Canceling process ELFBOWL.EXE [5388 / 7] SBIE2101 Object name not found: \Sessions\1\BaseNamedObjects\ISWWH_BEACON @22c8@EFR-controller, error CreateEvent (C0000022) access=001F0003 initialized=1 SBIE2314 Canceling process ELFBOWL.EXE [8904 / 7] 
 Whatever I try to do, I get and SBIE2101 Object name not found: \Sessions\1\BaseNamedObjects\ISWWH_BEACON nothing runs. I have looked in these boards but found nothing really similar to what I have going on, unless I missed a post mentioning a working solution I not tried (on this fresh installation of the program). 
 I have seen people post their config file so here is mine. Thanks for any thoughts on the matter. 
 [GlobalSettings] Template=7zipShellEx Template=AutoSizer Template=WindowsRasMan Template=SynapticsTouchPad Template=WindowsLive Template=OfficeLicensing [UserSettings_083601A6] SbieCtrl_UserName=main SbieCtrl_NextUpdateCheck=1587682598 SbieCtrl_UpdateCheckNotify=n SbieCtrl_ShowWelcome=n SbieCtrl_WindowCoords=343,150,880,450 SbieCtrl_ActiveView=40021 SbieCtrl_ProcessViewColumnWidths=250,70,300 SbieCtrl_BoxExpandedView=DefaultBox [DefaultBox] ConfigLevel=7 AutoRecover=y BlockNetworkFiles=y Template=qWave Template=WindowsFontCache Template=BlockPorts Template=LingerPrograms Template=Chrome_Phishing_DirectAccess Template=Firefox_Phishing_DirectAccess Template=AutoRecoverIgnore RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Favorites% RecoverFolder=%Desktop% BorderColor=#00FFFF,ttl Enabled=y

Filippo Bruno · Answer

Hi, 
 I used Sandboxie in Win7 64bit without any problem (except when installing software that created virtual printer drivers). Then 2 years ago I moved to Win10, and problems began to arise, but after Win10 September 2019 update nothing works anymore! Impossible for me to install EVERYTHING. Last year on a VMware Win10 image I installed qbittorrent: after Win10 update I could still run it sandboxed; I tried to install the same qbittorrent executable on another VMware image (based on the same empty Win10 source) but after the Win10 update and Sandboxie always fails with SBIE2101 error. 
 It is very frustrating because I cannot install any software in the sandbox. 
 But, yesterday I did a more refined search and I succeeded in installing a software using this trick (it requires relaxing Sandboxie's protection, so I am not going to use it to test potentially dangerous software, but only trusted software I want to be able to uninstall simply by deleting the sandbox). 
 I started Sandboxie (my version is 5.31.6 64bit), opened File|Resource Access Monitor and I launched sandboxed my setup.exe using the context menu. Sandboxie failed with SBIE2101 error as usual. I copied and pasted the Resource Access Monitor log into a Notepad blank window and I looked for the last IPC entry, that with a "X" instead of an "O". My item was 
 "\Sessions\3\BaseNamedObjects\ISWWH_BEACON@8808@EFR-controller" 
 So I opened my Sandbox Settings and in Resource Access|IPC Access|Direct Access I added the following: 
 *\BaseNamedObjects\ISWWH_BEACON* 
 Then I tried to run the setup.exe again. The SBIE2101 error rose again but with a different message. I ran Resource Access Monitor again and so forth and I found that the previous ISWWH_BEACON... entry was ok and the problem were in another part. I added another ICP entry in Direct Access list and I succeeded in completing the setup.exe installation! 
 I don't know what an ICP is, how dangerous could it be to allow direct access to some of those entries, but at last I understood how to install something. 
 I hope this could be useful to you, even if I strongly desire that Sophos would address this issue more seriously as months passed since its first reports. 
 Regards, 
 Filippo