VirtualBox

Opened 16 years ago

Closed 8 years ago

#1535 closed defect (obsolete)

cannot install Symantec Endpoint Protection

Reported by: Michal Suchanek Owned by:
Component: VMM/RAW Version: VirtualBox 3.2.12
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by aeichner)

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.

Attachments (4)

sym1.tiff.png (384.0 KB ) - added by Michal Suchanek 16 years ago.
sym2.tiff.png (385.0 KB ) - added by Michal Suchanek 16 years ago.
sym3.tiff.png (382.0 KB ) - added by Michal Suchanek 16 years ago.
sym4.tiff.png (24.3 KB ) - added by Michal Suchanek 16 years ago.

Download all attachments as: .zip

Change History (12)

by Michal Suchanek, 16 years ago

Attachment: sym1.tiff.png added

by Michal Suchanek, 16 years ago

Attachment: sym2.tiff.png added

by Michal Suchanek, 16 years ago

Attachment: sym3.tiff.png added

by Michal Suchanek, 16 years ago

Attachment: sym4.tiff.png added

comment:1 by marcel, 16 years ago

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 by Michal Suchanek, 16 years ago

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 by Ed Plese, 16 years ago

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 by Chris Ross, 16 years ago

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 by Guilherme Moreira, 15 years ago

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

in reply to:  5 comment:6 by Fred Koch, 15 years ago

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 by Frank Mehnert, 13 years ago

Component: otherVMM/RAW
Version: VirtualBox 1.6.0VirtualBox 3.2.12

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

comment:8 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use