Sandboxie Support

Hi,

I keep getting this popping up: SBIE2101 Object name not found: , error OpenProcess (C0000022) access=001FFFFF initialized=1

Information ???
viewtopic.php?p=104180#p104180

Hi,

Sorry, here is more details:

Sandboxie 5.20 (64bit)

FireFox (64bit)

Windows 10

Windows Defender

After running FirFox in Sandboxie and then close FireFox a few seconds after the error pops up and keeps popping up despite my closing the Sandboxie error.

Hi, again sorry i am running FireFox 56.0

Simplelife123abc wrote: ↑

Sat Oct 21, 2017 3:13 pm

Hi,

Sorry, here is more details:

Sandboxie 5.20 (64bit)

FireFox (64bit)

Windows 10

Windows Defender

After running FirFox in Sandboxie and then close FireFox a few seconds after the error pops up and keeps popping up despite my closing the Sandboxie error.

The first thing you should do is update Sandboxie to beta 5.21,6. Specially if you have upgraded W10 to Fall Creators Update. Get the beta in the link below.
viewtopic.php?f=61&t=24329

What version of W10 are you using?

So far, I haven't seen any message 2101 with Sandboxie 5,21,6 in the Fall Creators Update but I used to see one once in a while when launching Firefox in previous versions of W10. I used to just close the message, and Firefox continued to work properly. You could try clicking Hide in the message next time you get the message if Firefox works properly despite the message and after you close it.

Bo.

Hi,

Thanks for the reply.

Can you tell me why ? when i try updating Sandboxie from the help section it shows no updates.

Simplelife123abc wrote: ↑

Sat Oct 21, 2017 3:49 pm

Hi,

Thanks for the reply.

Can you tell me why ? when i try updating Sandboxie from the help section it shows no updates.

Betas dont show there. Thats only for officially released versions of Sandboxie,

In he case of W10, you are better off using the beta. It contains updates for the on going changes that are continuously taking place in the system.

You need to mention the version of W10 you are using.

Bo

Hi,

Thanks, the beta update has solved the issue.