Unable to install programs in Sandbox

[henryg]

screenCapture_672859_778394625_0.png (11.25 KiB) Viewed 426 times

This happens on most but not all programs (exe, msi) I try to install directly into a sandbox. The odd program that uses old fashioned installers seem to work. It's been going on for some time and is a nuisance as I cannot test programs anymore before normal installation.

I set up a new default sandbox and tried that as well as my various personalised one; and I also deleted my ini file and allowed SB to create its default one with no difference.

SB 5.24x64, Win 10x64

[henryg]

Is anyone from Sandboxie looking into this?

[Barb@Invincea]

Hello henryg ,

As we asked last time: viewtopic.php?f=11&t=25026&p=130838#p130838
Please provide a list of some the affected programs so that I can test them.
Include a copy of your configuration file (Configure --> Edit Configuration . Copy/paste the output, highlight it and click on the "</>" button to format it).

Also, be sure to provide all the info required here:
viewtopic.php?f=11&t=19746

Regards,
Barb.-

[Sam777]

This happens on most but not all programs (exe, msi) I try to install directly into a sandbox. The odd program that uses old fashioned installers seem to work. It's been going on for some time and is a nuisance as I cannot test programs anymore before normal installation.

I've come across this error on an occasion. The solution I use doesn't always work with every program but it's worth a try. The most common method to install software into a sandbox is to right-mouse click on the exe and select - Run sandboxed. The other method in a newly created sandbox, is to open SB control panel. Right-mouse click on the sandbox and select: Run Sandboxed\Run Any Program. In the popup window type in NOTEPAD and click OK. This actions creates the drive folders and registry within the sandbox.

Now right-mouse click on the sandbox and select EXPLORE CONTENTS. Open the the DRIVE\C folders and create a new folder called TEMP or whatever you like. Copy the program you are trying to install into the newly created temp folder and try installing from there. This doesn't work with all programs. There are some software that cannot be sandboxed no matter what you do because the developers prevent it somehow.

[henryg]

Sorry for the delay in replying, but my PC has been playing up.

Programs to test:
An easy program to get to try is Bowpad64 (http://www.majorgeeks.com/files/details ... 4_bit.html). Assuming it fails, msiexec.exe cannot be terminated in the sandbox or via Task Manager. Very odd.

Skype Desktop v7.41 (full instal version not stub) does the same. I don't use the store version, or v8 which I disliked.

There have been many more, but I didn't keep a note as they were transient, but hopefully this should enable you to recreate the problem, if indeed you suffer the same.

I tried Sam777 suggestions (thank you for those) but it made no difference.

Windows 10 1709 16299.334
SB 5.24
AVG Internet Security 18.3.3051 (build 18.3.3860.309)

If you need anything more, let me know.

[Barb@Invincea]

Hello henryg,

I logged in to a VM with Win 10 x64 + Sbie 5.24, launched a Sandboxed browser in a new Sandbox with default settings, downloaded BowPad from your link, executed it and launched it without issues.
Upon closing the program, it took a few seconds to finish all processes, but they all terminated correctly .

I was also able to install Skype version 7.41.10.101 (downloaded from their website, Classic version). It launched, logged in to an account and closed correctly.

I did ask for a copy of your Sandbox config file in case there's something there that might be preventing you from running these apps. I recommend that you uninstall your AV software to see if it is holding on to files (you may also need to empty your temporary folders files as AVs hide stuff in there sometimes. I remember this with AVG specifically). This is for testing purposes, you should re-install your AV protection after testing.
Always test in a new Sandbox with default settings and use fresh download copies of the programs you want to install, to avoid carrying over any corrupted files/issues from a previous box.

Regards,
Barb.-

[henryg]

Sorry, I thought you had my ini file already. If you don't see the same problem then it must be local, and I'll have to try uninstalling AVG etc etc, but of course I had tried with a vanilla ini file per my first post.

Que sera.