Ticket #1535 (closed defect: obsolete)

Opened 9 years ago

Last modified 14 months ago

cannot install Symantec Endpoint Protection

Reported by: hramrach Owned by:
Priority: major Component: VMM/RAW
Version: VirtualBox 3.2.12 Keywords:
Cc: Guest type: other
Host type: other

Description (last modified by aeichner) (diff)

On OS X host win XP sp2 guest installing Symantec Endpoint Protection 11 results in various exceptions.

After rebooting the system is completely broken, exceptions in random processes break even basic functionality.


sym1.tiff.png Download (384.0 KB) - added by hramrach 9 years ago.
sym2.tiff.png Download (385.0 KB) - added by hramrach 9 years ago.
sym3.tiff.png Download (382.0 KB) - added by hramrach 9 years ago.
sym4.tiff.png Download (24.3 KB) - added by hramrach 9 years ago.

Change History

Changed 9 years ago by hramrach

Changed 9 years ago by hramrach

Changed 9 years ago by hramrach

Changed 9 years ago by hramrach

comment:1 Changed 9 years ago by marcel

Try doing custom install and selecting only anti-virus. Seems to work for me, but I think my VM is hosed from the previous SEP installation attempt.

comment:2 Changed 9 years ago by hramrach

Thanks for the tip, for me it works if I do not select firewall.

Still this is some problem with the VM since the firewall works on real hardware and in other VM solution.

comment:3 Changed 9 years ago by eplese

I had this problem also. I found that you can do a custom install and select everything except "Application and Device Control" and it will work. The recommendation to keep the firewall unselected works as well because it forces you to also unselect "Application and Device Control" when the firewall portion is unselected.

comment:4 Changed 9 years ago by cross

Thanks. Unfortunately, my company is distributing a large setup.exe binary that doesn't allow any configuration, so I am unable to perform a custom configuration to disable either of the suggested portions of the installation. :-(

Has anyone done any work on figuring out why this portion of this application suite causes these severe problems? Clearly, it's something wrong in the way it's working with VirtualBox, and I'd hope it could be fixed.

Anyone looking into it? Any idea on if a fix may appear? Thanks.

comment:5 follow-up: ↓ 6 Changed 9 years ago by Nomad_RJ

I have the exact same problem, even with Vbox latest release (2.1.2).

comment:6 in reply to: ↑ 5 Changed 9 years ago by fkochiv

I am experiencing the same problem while using Vbox 2.1.4. Without a fix, I will not be able to use this at work. :(

comment:7 Changed 7 years ago by frank

  • Version changed from VirtualBox 1.6.0 to VirtualBox 3.2.12
  • Component changed from other to VMM/RAW

We have a confirmation that this work if VT-x/AMD-V is enabled.

comment:8 Changed 14 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use