Suggestion to devs to help Windows SEP users

[PassinThru]

Since 4.3.12 is the highest version of Virtualbox I can currently use, it would be very helpful if the devs would upgrade the Guest Additions and Extension Pack for 4.3.12 with the latest changes. That way we wouldn't have to jump through hoops to run recent versions of Linux (I'm struggling with Ubuntu 14.10) with full functionality. Currently I can only run Ubuntu 14.10 at 640x480 resolution, and shared folders don't work at all.

Virtualbox is rapidly approaching 10 releases that haven't worked with Windows systems with SEP installed. It would be nice to have some version that works with current guest operating systems.

- Scott

[michaln]

I'm sorry to say that releasing some sort of updated VirtualBox 4.3.12 is not an option for Oracle. It is unfortunate, but so far no one has figured out how to make VirtualBox compatible with every piece of Windows AV software out there and keep VirtualBox secure.

If you can get official support from Oracle, please do it--issues reported by customers do get fixed. If you can get support from Symantec, please do it. If you can not get support from either, you might need to re-evaluate the wisdom of using two conflicting software packages neither of which you can get any support for. You might have to wait until someone with a support contract runs into the exact same problem (so far that hasn't happened), or dump either SEP or VirtualBox.

BTW how did you arrive at 10 releases? The way I'm counting, 4.3.14/16/18/20 is four releases, not ten. Not that that makes the situation any less bad.

[PassinThru]

Ah, right you are. I was doing simplistic subtraction of the version numbers. .22-.12 = .10, but I forgot that releases are always even numbers.

In the main defect on SEP, klaus rightfully points out this is very important for VirtualBox security. He argues that being able to disable the work done so far would expose users to a serious security issue.

To that I respond that my VirtualBox Ubuntu 14.10 VM is 100% secure. That's because I can no longer use it. I have moved to VMware for the time being, as I have too much invested in that VM to move to another easily, and have to get my work done. Once the problem is solved, I will gladly move back, as I much prefer VirtualBox, and think the developers are doing great work on our behalf.

Not allowing the disabling of the current work simply means that there are a significant number of people who can no longer use VirtualBox. It seems to me that whether users are exposed to the possible security issue should be their decision.

That said, I don't expect that to happen. I am not naive enough to think that such an encapsulation of the existing work would be a trivial exercise, and any time spent doing that would be time not spent actually addressing the problem.

I was fortunate. For the longest time, 4.3.16 worked for me. Then a couple of weeks ago, probably as the result of an SEP update, it stopped working. 4.3.14 didn't work either, and 4.3.12 forced me to work in a 640x480 desktop. So I had to move.

I will continue to monitor progress on this issue. I already miss VirtualBox.

UPDATE: Corrected version numbers to be real.

[mpack]

For the longest time, 4.20.16 worked for me. Then a couple of weeks ago, probably as the result of an SEP update, it stopped working. 4.20.14 didn't work either, and 4.20.12 forced me to work in a 640x480 desktop.

You seem to be having a continuing problem with version numbers: there has never been a 4.20.16 release. Or 4.20.14, or 4.20.12. When highlighting what versions work and don't work it is surely important to be accurate in your identification.

[PassinThru]

Two things:

- I apologize about the version numbers. I was confused. I have corrected my post.

- 4.3.22 now WORKS!!! Great job, folks! Since my SEP installation is under corporate control, I had no say in whether exceptions were granted. Now I don't need them.

Today is a good day.