Discussion in 'sandboxing & virtualization' started by ad18, Dec 16, 2013.
Jarmo - idd its my attitude and i wont be ashamed for it, but its for real and not arrogant because you are one of those who probably never will understand, please dont let me point out your statements here in the forum.
but what i can tell you that this issue seems only happen to win7, and mayby there only x64. currently working on win8/x86. Firefox is right now in the box. Windows 8 was not offered patch kb3096447.
Again you just keep making mistakes:
"The update in question KB3088195 (Win 10 it is KB3097617) --->) "
that quoted is from the link you have been given 2 times.
win7, 64bit, sbie4.20, norton ns22.5, ff40.0.3 ran windows security updates only, started getting sbie errors and a bsod. uninstalled microsoft update kb3088195(took 1 hr to uninstall). today i got sbie errors again and a bsod. i have no win10 updates-service disabled. since win10, nothing works anymore. if sandboxie worked on linux i would dump windows in a heartbeat. i've been reading the threads about firejail on the linux forums. i have 2 xp machines duel booting ubuntu and i'm liking it. just ranting. thanks
Hello topo. Installing kb3088195 can trigger a BSOD when running Firefox with Flash under SBIE. It doesn't happen in every computer. And its not likely the BSOD would occur when running Firefox sandboxed in computers that don't have the plugin installed. The BSOD shouldn't happen when using browsers like Chrome, Opera or IE. Installing the KB causes errors in Chrome and Opera but nothing more than that. Running IE sandboxed should work fine in computers that have the KB. In one short paragraph, that's the story between kb3088195 and SBIE....Update with the fix, coming soon.
Time: 8:19 a.m. CET.
Ummmm... I would like some help.
I included F:\ and G:\ in my Default Box as Forced Folder entries. F is a 16GB ThumbDrive, and G is a 2TB External HDD.
When F loads up in SBIE, all is well; one Explorer window pops up.
However, when G loads up in SBIE, two Explorer windows pop up, both identical. Both mention G in the Window Bar. I sorta' expected one might be "Computer", but this was not the case. Both indeed show G in between the [#]'s...
Ummm, what the hell?! lol...
I am using W7HP x64 in LUA and the latest SBIE beta. This behaviour was also seen with the latest stable version, and some v4's.
I installed LP for Windows as opposed to using a plugin/addon for IE and FF. The installer provided an option for what browser to inject into, so I haven't had to add anything special in browser sandboxes for LP. I have also unticked the Software Compatability option for LP in Sandboxie. Firewall access must be provided for LP since it stores credentials for login and password for sites on its server (this is important for those that use rules for browsers; if remote address for browsers is set to "all", then disregard this sentence). The only reason you would need to directly access the LP AppData folder is if you are exporting/importing all details out of/into LP itself (needs confirmation for Shadow Defender, will be reintroducing SD soon, still feeling naughty and naked without real-time AV/AM/Ax).
Damn, totally overlooked trying this in the browser. I went with adding "ProtectedMode=0" to mms.cfg in windows/syswow64.
I never knew this was possible, thanks!
After the last Windows update, Sandboxie has become simply UNUSABLE on Windows 8.1 and Windows 10 computers.
We need Tzuk back.
In addition, everybody is talking about problems with Firefox and Chrome, but I have the same issues with Internet Explorer. NO browsers are working with Sandboxie after the last Windows update.
It's Update KB3097617 - Uninstall it and it affects more than SBIE. IE is not affected. Edge does not work with SBIE. If you're using flash plug in, remove that too.
As for Tzuk, Stop living in the past.
For Windows 10 is KB3097617.
After uninstalling, you may wish to hide the update temporary using wushowhide.diagcab.
The system installed KB3097617 back after I have uninstalled it, so I used this tool to temporarily prevent the update.
Thank you so much. It worked. No issues after uninstalling KB3097617 with FIREFOX ONLY!
Chrome is still messing up.
Also, what is the KB number for Windows 8.1 that is similar to KB3097617?
I could not use Internet Explorer on my Windows 8.1 laptop. I did not know that Windows 8.1 has Edge.
P.S. I don't want to discuss my personal vision about big ("bloated"-ly bureaucratic) companies acquiring truly entrepreneurial, free-market based and ownership-oriented businesses.
I've said it. Now, let's forget about it.
You're obviously mis-informed. Invincea, is a small startup (100 employees) with dedicated devs for Sandboxie. Tzuk willingly sold the company. Invincea, is a free market, minority owned. No bat for a program that is essentially free for you to use.
Thanks for the tool!
I disagree. Tzuk was frequently slow at fixing problems. Invincea has been more responsive IMO. If you want to lay blame go for Microsoft.
From your info.
1 Tzuk = 100 employees of Invincea.
Also, what has a "free Market" to do with "minority owned" (...)
Anyway, you have not answered my question about crashing Sandboxed Internet Explorer for Windows 8.1.
I've been using Sandboxie for many years
, but only very recently I've started encountering BIG problems with Sandboxie (after Tzuk sold the company).
Don't get me wrong. I fully understand that it has SO MUCH to do with Windows OS upgrades; therefore, it is DIFFICULT to compare
Tzuk's time period with Invincea tenure because it's so EASY to blame MS.
Been a longtime user of Sandboxie for a while now. I understand that a kernel level change in Windows is a big shakeup, but advising people to uninstall that update and blaming Microsoft is and extremely poor idea. This alteration was made for critical security purposes, not to mess with Sandboxie. You are very likely less secure on an unpatched kernel running Sandboxie than you think you are.
I keep hearing that this isn't Sandboxie's fault. Maybe that's true, but I've seen no other issue with ANY program other than Sandboxie. I don't blame them for the situation, but it's rather tiresome to see them point fingers over and over again on their forums rather than finding solutions.
Telling their customers to uninstall a critical security update and open a vulnerability feels extremely ill advised.
Invincea has been/is super responsive. M$ does it's thing and we all play catch up.
No blame. Just, is what it is.
I mean this thread is super responsive and very appreciated.
I do not see how anyone can find fault/blame/non-responsive by reading Craig@ messages.
My two cents.
marzametal, Mozilla has made it easier to disable Flash protected mode. Now it can be done via Firefox Tools>Addons>Plugins, Click Options for Shockwave Flash, untick Enable Adobe Flash protected mode. Doing it in about:config or adding ProtectedMode=0 is not necessary anymore.
I like your answer.
I DON'T BELONG TO ANY FAN/"my team is better", etc... CLUBS.
I'm just upset that this morning - in MANY YEARS - my wife will use an un-Sandboxed Browser,
and I don't feel good about it.
Your advice worked for Firefox, but my wife uses Chrome.
Could you help me to resolve that "unhappy" Sandboxie issue with Chrome?
Thanks in advance.
For all systems except W10, KB3088195 is the one that has to be removed (temporary workaround).
Zmechy, I dont have Chrome in my system. I cant be sure but I don't think the SBIE message you are getting with Chrome has anything to do with the recent Windows updates. Perhaps your antivirus or another security software is conflicting with SBIE. I cant remember now but what AV are using now?, etc.
Zmechy, about Chrome. You can try things like, creating a new sandbox and running chrome in it instead of in the old Chrome sandbox. When you create the sandbox, dont copy settings from any existing sandbox. Also try running Chrome in the sandbox without Drop Rights. Untick Drop Rights and see what happens. Some programs in some computers work better without DR, that includes Chrome. For the current Chrome sandbox that you are using, if its not set to delete on closing, delete it manually. After a browser update like Chrome had a couple of days ago, the sandbox has to be deleted otherwise the new version of the browser wont work in the sandbox with contents of the old version. This things are pretty standard but they fix a lot of SBIE issues.
Don't be discouraged, Zmechy, I know you are a huge Sandboxie fan but feel frustrated now because of recent issues. In my opinion, Sandboxie is in good hands now. Tzuk knew what he was doing when he sold his baby to Invincea. I am glad Sandboxie was sold to a company based in the US and the truth is that this guys have maintained SBIE real well. Nothing is perfect in life, not even my wife or SBIE but pretty much everything that I do in my computers is done under SBIE and all I do feels smooth and feels fine. When I click on files and programs they open and close fast. I dont have any other security program along SBIE and that helps but the key for you personally, is finding and using programs that dont conflict with SBIE. Thats really the key to enjoy using SBIE.
Minuette, not installing or uninstalling the KB that breaks Sandboxie is a temporary workaround. In my personal case, I always wait days or weeks before installing Windows updates. So, me personally, even if nothing had been broken by Octobers updates, I would still not have installed any of the recently released Windows updates. Waiting a few days to install Windows updates doesn't make any difference. In fact, I think it is wise to wait days or weeks before installing Windows updates because sometimes this updates break computers. Thats why I do updates that way. In the end, all important updates get installed in my computers and I never have issues when they get installed.
Separate names with a comma.