Sandboxie Acquired by Invincea

Trouble is I can't get to the Sandboxie Control>Configure dialog because it's greyed out due to the 'Check For Updates' pop-up dialog.

If I try and update C:\Windows\Sandbox.ini directly I am not able to (though I do run as admin) ...

 

No, nothing happens and I get an error when closing the installer. But I will upgrade to the newest SBIE.

 

I gather you cant open Configure because the button is grayed out and you think that's because of the message.

Perhaps your Sandboxie.ini is corrupted. I would try reinstalling SBIE. Run the SBIE installer and choose Uninstall (so you dont save settings), reinstall afterward.

Bo

 

I installed DL a few times without issue. The thing that bothers me with this program is the auto update it does automatically when you install it.

The Sandboxie upgrade might help, I suggest you get rid of your old settings and start fresh. Download a fresh copy of SBIE and choose Uninstall, reinstall afterward.

Bo

 

Bo - I backed up my existing Sandboxie.ini file just in case, and uninstalled, including removing (reluctantly) all the settings - and sandboxes. Then reinstalled, rebooted - but same problem (now with defaultbox only) with new (or old) .ini file. Same problem also with latest stable version.

Also the recover to the Downloads folder stopped working yesterday, downloads just go to C:\Sandbox\...\Firefox\\user\current\Downloads and the recovery prompt does not appear.

I thought it might have to do with a recent upgrade of BlackFog Privacy, so imaged back to before that, 4 days ago, but the problem even occurred then. Which is strange because I am pretty sure the problem only appeared more recently. May have to try going further back to see (not sure when I last rebooted), though I would prefer to avoid to much 'forward recovery'.

Else it looks like there must be something else going on - I have now imaged back to today, so I am back to where I was, but except for aforementioned Sandboxie update checking and absent download recovery, all seems OK.

TBH I'm lost on this one. It can't seem to modify the .ini file (see one of the pop-ups in addition to those in #4501 below).

I will have to play around some more, else I may have to remove Sandboxie (for now at least).

 

notepad is installed where?
it does not matter if you start notepad as admin - you need to give notepad the rights to save its files.

btw notepad? windows notepad is a stupid litte thing.
get notepad++ instead!

you need to start npp with admin rights -> create a link and edit options -> [x] admin rights
npp will have addional text [Administrator] in its window title. no text? no admin, no saving!

 

Will try playing with Notepad++ tomorrow.

Just wondering why this is happening. I did not change anything in Sandboxie. Something must have changed the permissions on that folder / file.

 

For the recovery prompt to appear, you need to make sure Immediate recovery is ticked in Recovery. You imaged back but thats probably what you needed to do to solve that.

For the issue about writing to Config file, perhaps it would be best you post about it at the SBIE forum.

Bo

 

Sandboxie 5.25.2 has been released.

https://forums.sandboxie.com/phpBB3/viewtopic.php?f=65&t=25684#p133187

Bo

 

All is working well with 5.25.2 in my W10 1709 build 16299.402.

Bo

 

Thanks for your suggestions Bo. Immediate Recovery would have been checked, I have always had that checked and never changed that.

Happily, after the last reboot, the update check message has not appeared, I am able to access the Config file and Immediate Recovery is working again. All is back to normal! (Reluctant to reboot in case the issue returns ).

It would appear that the update check (message) is only active for a few days, and causes some issue - on my machine at least, as this is the second time it has happened (though I didn't notice the Immediate Recovery issue then). I may report it on the Forum, or at least the next time it happens. Probably unique to my system, else if it was a bug it would surely have been reported already.

And this is prior to installing 5.25.2 so it is not to do with that.

Re these parameters, mine are now:
SbieCtrl_NextUpdateCheck=1525324907 (don't know what it was before, but now > than the value on yours)
SbieCtrl_UpdateCheckNotify=y (I have successfully edited this now to 'n' in the hope that the update check message then does not return)

 

I don't know what's going on, but even with the latest SBIE version and a clean sandbox it still won't work. Perhaps it's a Win 8 thing, or perhaps it's because I block access to certain data, but this shouldn't cause any problems. So there's something fishy going on and I decided not to install it on my real system. The good news is that with the latest SBIE, both Vivaldi and Opera install and work just fine from inside the sandbox.

 

Perhaps the problem you are having installing DL in the sandbox is because you are blocking AppData and C drive. If you block those folders, DL cant be installed in the sandbox. DL requires access to Local and LocalLow in AppData and also needs access to Windows and Program files. Try installing DL without blocking those folders or try using WriteFilePath (files in those folders are hidden from sandboxed programs but they can still write to their copy in the sandbox) instead of ClosedFilePath.

Yes, you should be happy, 5.25.2 is a nice version for Opera and Vivaldi users .

Bo

 

I will try one more time without any data protection. But it's clear that sometimes Sandboxie is the problem, for example all of a sudden AgaueEye is now able to run, this wasn't the case with older versions of SBIE.

http://www.softpedia.com/get/System/System-Info/AgaueEye.shtml

 

from my understanding it makes no sense to allow other and block those. either complete in the box or outside.

i manage my downloads in the box where nothing can be executed - and when (eg notepad or winrar to view) it stays in the box.

but as you show me sandboxie can be screwed that bad to malfunctioning - nothing to comment for this... sigh

 

DL creates files in the sandboxed copy of AppData and C drive, so, if you block access to the real folders, DL cant be installed in the sandbox. Do what I suggested, either don't do nothing regarding blocking those folders via Sandbox settings or hide files their by using WriteFilePath instead of ClosedFilePath. When you make those folders Write only, sandboxed programs cant read files, files are hidden (protected from being accessed) but sandboxed programs can write what they need to write to the copy of those folders in C:\Sandbox.

Regarding why AgaueEye can run now and not before, that's not unusual. Compatibility changes all the time, its never static.

Bo

 

So far, so good between Sandboxie and 1803. As of this moment all I tested are my browsers (Firefox and IE), and watching videos in YouTube and CBS Sports using Firefox to test sound and video, and all is well. I ll be back later when I have some more to tell.......

Bo

 

I tested everything I do sandboxed, all was successful, no errors. I even tested functions I dont do, like opening a CD sandboxed. Flawless. Sandboxie (Right off the bat) Beta 5.25.2 is compatible with W10 64 bits 1803.

Bo

 

sbie is futile since it cannot sandbox win apps under w10. and soon windows will become a platform of apps instead of programs due to winrt architecture.

 

Sandboxie is not compatible with Universal apps. Let me tell you something. I like Windows. Why I like Windows? Because the user pretty much can do whatever he wants to do with his computer (even now), And there are more programs developed for Windows than for any other system. If that ever changes, I ll move to the system that allows me to have a free hand in choosing the programs I want to use.

In today's W10, I dont use the Store, or Edge. I totally avoid those programs. I avoid any program that cant be sandboxed. All I do with Universal apps is make sure they are updated and that's it. To this moment in time, it works for me. In this regard in particular, I don't worry about what the future will bring.

Bo

 

Metro Apps don't need to be sandboxed, they already are via Appcontainer...

 

yeah, i know. that's why sbie is and will be futile. would you use sbie on a windows phone? the answer is no. same with windows os.

 

i am using sandboxie with Win10 because i don't only run Metro Apps or Edge...
And as far as i know Appcontainer doesn't sandbox folders.

 

isolation
https://msdn.microsoft.com/en-us/library/windows/desktop/mt595898(v=vs.85).aspx

sandboxie
https://www.sandboxie.com/HowItWorks

now leave...