Opened 9 years ago
Last modified 7 years ago
#15217 new defect
McAFee Agentblocks virtual machine running
Reported by: | Owned by: | ||
---|---|---|---|
Component: | host support | Version: | VirtualBox 5.0.16 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Good Morning,
I use the Business PDL with O.S. Host Windows 7 Enterprise edition (x64). In this sistem running McAfee Agent and i can't uninstall it. But this block a VirtualBox Process. The VM is extremely important to testing a Engineering Siemens's software on Debian's O.S.
The message error are:
supR3HardNtChildPurify
supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED
Apertura di una sessione per la Macchina Virtuale Debian non riuscita.
The virtual machine 'Debian' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Bresciani\VM\Debian\Logs\VBoxHardening.log'.
Codice 'uscita: E_FAIL (0x80004005) Componente: MachineWrap Interfaccia: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Attachments (3)
Change History (6)
by , 9 years ago
Attachment: | 2016_03_08_VirtualBox.jpg added |
---|
by , 9 years ago
Attachment: | 2016_03_08_VirtualBox_Details.jpg added |
---|
by , 9 years ago
Attachment: | mcafee agent.txt added |
---|
comment:1 by , 9 years ago
I'm seeing the exact same problem. Host is Windows 7 Enterprise 64 bit with SP1, also with McAfee. VirtualBox version is 5.0.16 r105871. I can provide logs if necessary.
Edit: 5.0.17 r106005 also has this bug.
comment:2 by , 7 years ago
... two years old ticket. I just experienced the very same issue: VB 5.1.10 McAffee installed.
VB 5.1.10 is the latest version supported by StorageCraft's VirtualBoot. Hence I could not upgrade VB to 5.2.x
Host OS: Window 10 Home (64bit) Guest: Windows Server 2012 Foundation
Is there any way I can resolve this w/o removing McAfee or (possibly) upgrading VB?
Thanks
comment:3 by , 7 years ago
Tell McAffee to not stick their noses where they have no business, or if they want to, they better be 1) properly signed and 2) update the Windows certificate database. For more information and details about the issue, see the article "Diagnosing VirtualBox Hardening Issues" to get some ideas...
Start VM