I just did a new install of VirtualBox using VirtualBox-4.3.20-96996-Win.exe on a Win 7 Pro SP1 machine. Before starting I carefully uninstalled and removed leftover files from VirtualBox-4.2.12, which I had been using for a while now.
I get errors when starting a VM. Any help or suggestions would be
appreciated. Details are below.
I created a new VM with these specs:
Name: Ubuntu2
Type: Linux
Version: Ubuntu (64 bit)
Memory: 1024M (out of 4G)
Disk: 16GB HD, VDI, dynamically allocated
All of that seemed to go smoothly.
When I Start the new VM I get an error pop-up with this text:
VirtualBox - Error In supR3HardNtChildPurify
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED rc=-5673
Button: Abort
After clicking Abort I get a 2nd popup with this text:
Failed to open a session for the virtual machine Ubuntu2.
The virtual machine 'Ubuntu2' has terminated unexpectedly during
startup with exit code 1 (0x1). More details may be available in
'C:\Users\200006507\VirtualBox VMs\Ubuntu2\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
I've attached VBoxStartup.log. The last few lines, which seem
relevant to me, are also here:
4b4.1c94: Error (rc=-5673):
4b4.1c94: supHardenedWinVerifyProcess failed with Unknown Status -5673
(0xffffe9d7): NtAllocateVirtualMemory (0000000000030000 LB 0x1000)
failed with rcNt=0xc0000018 allocating replacement memory for working
around buggy protection software. See VBoxStartup.log for more details
4b4.1c94: Error -5673 in supR3HardNtChildPurify! (enmWhat=5)
4b4.1c94: supHardenedWinVerifyProcess failed with Unknown Status -5673
(0xffffe9d7): NtAllocateVirtualMemory (0000000000030000 LB 0x1000)
failed with rcNt=0xc0000018 allocating replacement memory for working
around buggy protection software. See VBoxStartup.log for more details
4b4.1c94: supR3HardNtEnableThreadCreation:
I tried to start the VM several times and always got the same result.
Rebooting the host did not help. I got the same result when starting
the VM after a reboot of the host. I also got the same result with
VirtualBox-4.3.18-96516-Win.exe.
The host is a corporate machine that uses McAfee firewall and
monitoring software. I do not know if that matters.
Thanks,
Fred Wheeler
VBoxStartup.log
Description: Binary data
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
