Is there any chance Kaspersky 2016 gets supported? [SOLVED]

[Oekonom]

Hi,

since the win10 offer expires soon I am bound to upgrade until July.
Can you tell me the progress of Kaspersky 2016 and Sandboxie with Win10?

I currently use Kaspersky 2015 with 8.1 and have no problems

[henryg]

After years of using KIS with SB, very reluctantly at the time, I had to switch to AVG as I wanted both Win10 & SB. AVG is more user friendly than KIS IMO, and it seems to do the job well enough even if it does not do as well in the AV tests. Cheap deals out there too.

[Craig@Invincea]

As for KIS, no. They have code possibly related to their failed sandbox that hooks deep into Windows and it's blocks SBIE. We've tried to work with them, and well.. no.

We recommend Windows Defender. It does what it needs to do.

[Oekonom]

Can you link me to the overview of the supported AV Software?

[Craig@Invincea]

Some that have tested in the past here http://forums.sandboxie.com/phpBB3/view ... 11&t=21539
We recommend Windows Defender.

[henryg]

[SOLVED]? [UNSOLVED] maybe. And I'm not suggesting it is SB's fault etc, only that the thread name is misleading.

[Craig@Invincea]

No, it's solved. At this time, SBIE and KIS are not compatible with one another. There are no plans for this unless KIS drastically changes their code. Of course, we cannot change SBIE code.

[bvr124]

I faced the KS 2016 and Sandboxie 5.12 incompatibility problem. Last night I installed Opera Browser and the incompatibility is gone! It seems to me that the browser choice also has role in this incompatibility because I could not get Sandboxie to open using Mozilla Firefox browser. Only Opera works - don't know why! just for information, I run windows 7 OS.

[Craig@Invincea]

Yes, but most of the time, it doesn't work. It will remain a known conflict software and we don't recommend it's use with SBIE.
The only AV we recommend, and only because it doesn't cause a conflict, is Windows Defender.
If you're using SBIE, then any AV will work as long as it doesn't conflict. Malware is contained in the sandbox no matter what...and removal is as simple as deleting the contents of that sandbox, then move on.

[roader]

Another Feedback:
SBIE 5.12-64 can coexist with Kaspersky-IS 16.0.1.445(c) on Win7pro-64 and Win10pro-64.

Everything is running except Firefox/Edge/Internet Exploder:
SBIE2205 Dienst nicht implementiert: Win32Init.6 (000000AA)

Use Opera-38 instead!

Best regards, r.

[Craig@Invincea]

SBIE 5.12-64 can coexist with Kaspersky-IS 16.0.1.445(c) on Win7pro-64 and Win10pro-64.

Everything is running except Firefox/Edge/Internet Exploder:
SBIE2205 Dienst nicht implementiert: Win32Init.6 (000000AA)

This is why KIS is, and will be considered a Known Conflict. It causes serious issues, even done to the code level you cannot see.

[JohnA]

Another Feedback:
SBIE 5.12-64 can coexist with Kaspersky-IS 16.0.1.445(c) on Win7pro-64 and Win10pro-64.

Everything is running except Firefox/Edge/Internet Exploder:
SBIE2205 Dienst nicht implementiert: Win32Init.6 (000000AA)

Use Opera-38 instead!

Best regards, r.

I can confirm that it works great with Opera. Kaspersky continues to detect threats properly and Sandboxie contains. I've seen no side effects of having both software installed other than threats being detected in the sandbox.

I'm sorry that Sandboxie and Kaspersky couldn't resolve differences. From my vantage, however, there really wasn't an effort because neither side really wanted it to happen. The hooks mentioned in Kaspersky have been around forever and it wasn't until recently that it became a problem. The previous owner of Sandboxie made an accommodation with Kaspersky and it worked fine. From day 1 in the new architecture and owner, the attitude here was that one didn't need Kaspersky, there were alternatives. I didn't see that attitude with any other AV vendor and wonder if there's more to it than meets the eye. However, with that attitude, I'm not surprised nothing was worked out.

[bo.elam]

JohnA, Kaspersky has been conflicting with Sandboxie forever. Search the forum.

Bo

[Craig@Invincea]

The previous owner of Sandboxie made an accommodation with Kaspersky and it worked fine

\

That's before KIS made their owned, failed Sandbox. THAT's part of the reason it's conflicting. So please understand the entire story. We will NOT lower the security of SBIE for KIS.

We can't be compatible with everyone, otherwise SBIE would not work.

From day 1 in the new architecture and owner, the attitude here was that one didn't need Kaspersky, there were alternatives.

When was day 1? Just so you are well informed, SBIE worked with KIS since day 1 thank you.....Since your have the history and notes? It was 2013. KIS worked until last year around the summer, until Win 10 and their failed SB code and other odd coding caused issues.

Architecture? Yes, because we have to work with Windows XP through Win 10 and a whole hell of alot of other programs to make SBIE do what it does well, changes in code are needed to keep up. Or nothing would work. Should we just make KIS work for you? And not Chrome? or Firefox? Or Windows 10? Would that work for you? It doesn't work for us. But if you would like to point out the exact architecture changes that broke KIS / SBIE, please. Post. We'd love to review it.

Our Devs have sent many messages to them pointing out what they need to do. As have I. We're not going to beg them to fix what they need to fix. Sorry. We have other important things to do that make just one more A/V program work, when we have a list of over a dozen. And besides, IF YOU choose to use A/V with SBIE, we recommend Windows Defender. The creator of SBIE, before we destroyed it in your opinion, also recommended Windows Security Essentials (father of Defender) then too.

As you can see, I take issue with your uninformed assumptions.

[JohnA]

>> That's before KIS made their owned, failed Sandbox. THAT's part of the reason it's conflicting. So please understand the entire story. We will NOT lower the security of SBIE for KIS.

Kaspersky had a Sandbox long ago (Safe Run) which existed from at least 2009 and removed it replacing it with Safe Money in KIS 2013 using some of the technology. Safe Money still exists today. Now that's actually when I switched over to Sandboxie. Sandboxie worked fine with KIS 2013 and 2014 until KIS changed things (starting with KIS 15) to work on Windows 10. So blaming this on the "failed Sandbox" makes no sense to me, sorry.

>> When was day 1? Just so you are well informed, SBIE worked with KIS since day 1 thank you.....Since your have the history and notes?

The "day 1" I'm referring to is the thread that you started claiming Kaspersky as well as an AV solution in general wasn't needed and expected to conflict to which I responded. It was probably close to the time that KIS 15 was released in 2014 or shortly thereafter. The relationship between Kaspersky and Sandboxie has been complicated - I remember when Sandboxie was listed as an incompatible application by Kaspersky support and was told to remove it before receiving support. At that time, I had to convince Kaspersky that Sandboxie was not incompatible which they then acknowledged. The accommodation I was referring to still exists under Software Compatibility although it doesn't work any more.

>> Our Devs have sent many messages to them pointing out what they need to do.

Well, I saw one of your messages on the Kaspersky forum which I responded to. And if you noticed, you didn't get much sympathy there the way is was presented.

>> We have other important things to do that make just one more A/V program work, when we have a list of over a dozen.

Exactly the attitude I am referring to. Look, nobody is saying that this shouldn't have been a problem. What I'm arguing about is the lack of will in coming up with a solution on both sides. We are not talking about new products here. Kaspersky committed to having this fixed in KIS 16/MR1 and then backtracked - they have some share in the blame. I don't know why they changed - but when you make statements like this and post messages on their forum, is it really surprising? I'm sure they think they have many more things to do that get one sandbox product co-existing properly as well. In the end, users lose out. Perhaps you've made the financial calculation that it doesn't matter. As a Kaspersky user, I am disappointed and am telling you this - not to disparage or belittle you. I've told this to Kaspersky as well.

>> IF YOU choose to use A/V with SBIE, we recommend Windows Defender.

I'm sure you would since Windows Defender is on every Windows 10 platform and you couldn't very well tolerate an incompatibility there for long. But tell me the technical reasons why you recommend this. If someone decides to have an A/V solution, why would they not go for the best rather than settle for the minimum? Or are you claiming Windows Defender is the best A/V solution?

>> As you can see, I take issue with your uninformed assumptions.

Of course, you have knowledge of the current versions of Sandboxie - but as far as how Kaspersky worked over the years and it's relationship with Sandboxie previous to the current ownership, I'm not so sure that you are as well informed.