Read several posts about the issue w/ (Vista) & the x64 version of Sandboxie & "Drop Rights" possibly needing to be turned off before could install (test install / run) prgrms insides sandbox. My drop rights is unchecked (was already unchecked - maybe I did it & forgot) - yet still get the pop up w/ error 2217.

I tried browsing to the file (a beta setup.exe of Screenshot Captor), and also opening from sandboxed Explorer. Same error both ways.

I certainly have used Sandboxie to test install / evaluate prgms - but was many months ago. Obviously, something I'm missing / doing wrong.

Also, (may be normal) when browse to the file to be run from SB GUI, then click Open, the Run as Admin is grayed out.

Read the help file about "Experimental Protection" in x64 version of SB, & also about Drop Rights, but overall the instructions are a bit confusing to me. I see a lot of same questions posted, & can't get the suggestions to work, so far.

I'm sure someone w/ more experience can clear this up. Thanks.

EDIT:
1) It appears Sandboxie 64 bit won't run correctly from a user acct, even typing in admin PW when prompted, for launching SB, or installing / running a prgm sandboxed (even w/ Drop Rights unchecked).

2) Closed SB & logged into Vista x64 admin acct. Launched SB & checked Drop Rights setting. Even though that setting was UNchecked when started SB from a user acct - using "Run as Administrator" - & typed PW, when I later started SB from INSIDE an admin acct, the Drop Rights feature was still checked. Appears to save the setting on a per user basis, even though SB requires admin PW to start it in a user acct.

3) Once UN checked Drop Rights from SB while logged in admin acct, it allowed installing ScreenShot Captor (setup.exe). BUT...
** Install process did NOT create desktop icon NOR a startup shortcut, even though I selected both to be created during SSC's install (running in SB).

4) Was able to navigate to the executable for SSC by expanding the SB control box folder & then start SSC. Hardly one-click start up of a prgm installed INSIDE Sandboxie. Is this normal? That's ONLY way I can find to start this prgm that was INSTALLED under Sandboxie. NORMALLY, if installing prgms in a sandbox folder (logged in an admin acct), does SB allow creating desktop icons & start menu entries?

When reporting a problem, please post in the Problem Reports forum.

It sounds like Sandboxie thinks that the Drop Rights setting is enabled. If you use more than one sandbox, make sure you adjust the setting for the sandbox in which you are trying to install programs.

Thanks tzuk,

Yeah, I wasn't sure if this issue was just a lack of understanding on my part, so wasn't sure of correct forum. Good point about the settings in SB folder being used. I made the changes in the folder used to do the test prgm installation in a sandbox folder.

If others can, please address the other issues I saw when while logged in an admin acct, where no desktop icon and no start menu entry are created, despite these options being presented & selected during installation, inside a SB folder - even if logged in an admin acct.

However, in my edit to OP, seems Sandboxie will only allow installing prgms sandboxed (correctly) if logged into an admin acct. If logged in a user acct & SB is started using the admin PW, then installing prgms sandboxed doesn't work for me - even though PWs were entered. While logged in a user acct, installing a prgm into a sandboxed folder (w/ Drop Rights UNchecked) allows the installation process to go through, but after finishing, no files are in the SB folder.