Sandboxie Acquired by Invincea

using fast- or insider-ring is users option to deal with its flaws. if not capable -> leave such rings

is announced for the april 10th, current is april 5th. so invicea has 5 more days to fix it.
(and i am sure they will)

 

The day Fall Creators Update was released, Sandboxie did not have out yet a version that officially supported it. But even so, that day I was able to do everything I do regularly under Sandboxie without any problem (Except running Windows explorer sandboxed, which was a known issue and was fixed a couple days later). I expect at worst, something somewhat similar when Spring Update is released.

Bo

 

I never expected software to work at 100% efficiency right away after such upgrades, MS used to change things the last second or even just after the upgrades.

 

1803 will brake the homenetwork some need to set services "FDResPub" and "fdPHost" to "automatic" instead manually. i will wait for the next LTSB/LTSC.

 

I have updated Malwarebytes and the issue seems to have gone away. There was also a post on their forum advising that some of the older versions of malwarebytes exploit caused some delays - so will have to monitor if this issue pops up again in the future. For now operation is normal again.

 

I am glad you are good now.

Bo

 

on Spring Update, Sbie has the hive registry error: "Cannot mount registry hive" , so unusable, we will have to wait an updated version.

 

Thanks @guest for that heads up. Will have to hold off adding it for the time being as you suggested.

 

Hi guest, did you test 1803 yourself? If so, were you using non default Sandboxie settings (like moving the Container folder)?

Bo

 

@bo elam yes tested myself with free sbie default settings and using the shortcut.

Basically i installed it and tried right away to launch the browser from the Sbie's shortcut.

Edit: tried same procedure on another machine with Spring update, this time sbie launched properly.

i will investigate.

Edit 2: retried today on the same machine where the error occurred, this time launched normally...

Maybe it was a glitch or something.

Edit 3: this time, on a 3rd machine, i moved the container, and i get the registry hive error.

Interesting, this situation didn't triggered the error with the Fall update.

 

https://forums.sandboxie.com/phpBB3/viewtopic.php?p=133092#p133092

 

ok i see , thank you.

 

Yes, sadly a known issue but it won't be fixed until 1803 is released to public.

 

yes, anyway i can live with my container being on C for a bit more

 

I think that would be considered a "bug". Odd how problems for some products are blown off as "issues" whereas with other products it would be trumpeted as a "bug".

 

my definition:

Issue: prevent/affect the software to perform its main job.
bug: doesn't prevent/affect the software to perform its job.

 

An interesting thought. However, since the 1803 isn't even released to public I find it hard to call the problem a "bug" and not an "issue". A bug is something wrong with the existing code, it's an issue if it doesn't exist any code.

 

This is true... until tomorrow.

 

We'll see! I won't have a problem since I don't have Sandboxie installed these days. Windows 10 security has finally matured enough to protect me with official group policies/system settings and not "fake" policies that Sandboxie uses.

 

Thanks, guest.

As far as I know, the problem occurs only when the container has been moved. I dont move the Sandbox folder, I should be OK.

So guest, can you confirm, were you able to reproduce the registry hive error ONLY when the container was moved from default location?

As far as I know (confirmed to me by Barb), that's the only known issue with 1803 as of this moment. In my book, that makes compatibility between Sandboxie and 1803 even better than what it was the day 1709 was released (that day we couldn't run File explorer sandboxed, or it would take a long time before running).

Bo

 

Yes i confirm.

You will be happy, this time it works properly

 

Thats what I thought. Thanks, guest.

Last time, Sandboxie did work properly with the Fall Update right off the bat. The issue with File explorer was minor in my opinion. I am confident will be OK tomorrow, so I am forcing the update. If I had doubts, I wouldn't.

Bo

 

@bo elam Just don't enable "Core Isolation" yet.

 

Thanks, guest. I disable everything related to real time security but the Firewall in WD Security Center.

Bo

 

Yes except WD and WF, the other security features are so badly implemented that they don't worth the use.
Controlled Folder is, in term of usability, the most pathetic feature i ever saw since i use Win10, even the telemetry was better made.