forced folder and *reg file [Solved in Beta 5.21.6]

[vgishmasters]

Hello! i use sandboxie 5.20 and win10 1703 x64. Problem occurs with forced folders and starting *reg file. I used forced folders for my flash drive E:/ And any application from flash drive starts in sandboxie exclude any *reg file. When i'm starts any *reg file then i'm have notification, that sandboxie block it, but after that starts microsoft registry editor( not in sandboxie) and succesfully add information from *reg file to windows registry. Is this normal?

[Barb@Invincea]

Hello vgishmasters,

You can right-click--> Run Sandboxed on the *.reg file in order to launch it Sandboxed VS. opening directly from a Forced Folder.

I'll talk to the devs about the behavior you are seeing (I saw it too), might be the way ForceFolders works, but I'll have to confirm.

Regards,
Barb.-

[vgishmasters]

Ok! I'll waiting for solution. (Maybe it will be on 5.21 )

[Barb@Invincea]

Hello vgishmasters,

The devs explained that what's happening is that Sandboxie is trying to load a registry hive via a .reg file (which will not work, not even on the host) when using the ForceFolder feature.
You can find more info here:
https://www.sandboxie.com/SBIE1241

For the time being, you'll have to right-click on the .reg file instead, in order to run it sandboxed.
We will update this thread if any functionality changes are made to the Force Folder feature.

Regards,
Barb.-

[vgishmasters]

Barb, i mean that - if happens adding *reg to real registry(from sandbox), it will be big security problem. Can devs fix it? any file or application from forced folder must start only in sandbox, because launching in real system(like in my case) may damage the system.

[Brummelchen]

i can not confirm sandboxie behavior (5.21.2/5.20)
using a reg file from a forced (root > includes subfolders as well) folder (usb-stick) starts regedit in the box.
there is something wrong with your settings.

i assume you are trying to use a portable app from stick - which program is it?

[Barb@Invincea]

Hello Brummelchen,

Please try this:

Create a .reg file by exporting a registry key from your host (any will do)- Windows 10 CU.
Put it in a folder on your Desktop, set that folder as forced in Sandboxie .
Double- Click on the .reg file, and you will see the behavior.

The devs are aware and if anything comes up, I will update this thread.

Regards,
Barb.-

[Brummelchen]

is this a specific 1703 CU issue or any windows 10?
i am running LTSB only without the app crap and current is 1607 (14393.1715)

at least it does not matter if exported or manually created - i am capable to do both on the fly.

same test - no problem here. either its a CU issue or details for reproduction missing.

btw - no exceptions defined for programs, it remains all in the box.

[Barb@Invincea]

Hello Brummelchen ,

Thanks for the update. We can repro this on Win 7 as well, not only 10 X 64 CU.
If you are seeing something else, please provide more info so that we can review it.

Just to be sure we are following the same steps:
Create a .reg file by exporting a registry key from your host (any will do)- Windows 10 CU / Win 7 x64
Put it in a folder on your Desktop, set that folder as forced in Sandboxie . (Right-click on your Sandbox --> Sandbox Settings --> Program Start ---> Forced Folders).
Configure --> Reload configuration to apply the new settings
Double- Click on the .reg file located inside the forced folder.
UAC prompt will show, (outside Sbie), then the registry editor message will appear (outside Sandboxie). If you click yes, the changes are applied outside Sandboxie.

Regards,
Barb.-

[Brummelchen]

is UAC mandatory? it is not activated here (complete off).

[Barb@Invincea]

Hello Brummelchen ,

I turned off the UAC notification and the registry file opened Sandboxed in Win 7, from a forced folder.
However, it did not do the same thing in Windows 10 CU . It opened the prompts un-sandboxed as reported in the original post.

Regards,
Barb.-

[Barb@Invincea]

Fixed in beta 5.21.6
viewtopic.php?p=129389#p129389