virtualbox.org

I am using VirtualBox version - 4.3.20 r96997
Running Windows 7 Pro 32-bit
Anti Virus BitDefender latest version

When I attempt to start VM, I receive a popup message with the abort button:

NtWriteVirtualMemory/Peb failed: 0xc0000022 (RC=-1073741790)

I then recieve another popup "failed to open a session for the virtual machine "XXXX" ....

The error code is as follows:

Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

In the startup log, here are what seem to be some relevant details

c: Error (rc=-1073741790):358c.755
c: NtWriteVirtualMemory/Peb failed: 0xc0000022358c.755
c: Error -1073741790 in supR3HardNtChildScrewUpPebForInitialImageEvents! (enmWhat=5)358c.755
c: NtWriteVirtualMemory/Peb failed: 0xc0000022358c.755
c: supR3HardNtEnableThreadCreation:358c.755
c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.358c.755
c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'vboxrt.dll'.358c.755
.
.
c: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\Windows\system32\wintab32.dll': 0 (NtPath=\??\C:\Windows\system32\wintab32.dll; Input=C:\Windows\system32\wintab32.dll)358c.755
c: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\system32\wintab32.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=00704b1

Petr Vones wrote:

MuldeR wrote:The last VirtualBox version that was still working under Windows 7 (x64) was v4.3.16. Pleaser fix this serious regression...

The log says you very likely use modified unsigned vesion of uxtheme.dll to get useable UI in Windows 7. VirtualBox no longer allows this, you are no longer owner of your system, you must use signed DLLs only Try to copy original unmodified Microsoft uxtheme.dll (presuming you have its backup) into the virtualbox directory where virtualbox.exe resides. This should satisfy the malware check and VirtualBox UI will look ugly but it should not affect other applications look as you probably wanted. If it does not work you have to revert back to the original uxtheme.dll in windows system directory but you will lose the Windows UI customization at all, for all applications.

This solved the problem for me too, thanks! The easiest way to restore uxtheme seems to be running sfc /scannow in an elevated command prompt.

I'm having a problem that gives error messages that lead me here, so I assume it's related to security issues. I've been running 4.3.18 on a Windows 7 host, ubuntu guest. This morning, after some automatic updates, my guest failed to load, giving time out messages. I found the thread for 4.3.18 and some people mentioned that the upgrade to 4.3.20 fixed problems for them, but after upgrading I still have basically the same problem. I have very limited control over my virus and protection software due to company policies, although I could investigate the issue with IT support if necessary. I have not personally modified my uxtheme.dll; I'm not sure how to check if it was modified through company/IT "help". Any advice would be appreciated; I do a significant fraction of my work in that virtual machine. More details below.

Edit: works on VB 4.3.12.

Error popups as seen on 4.3.20:
VirtualBox - Error in supR3HardNtChildWaitFor
Time out after 60012 ms waiting for child request #1 (CloseEvents). (rc=258)

VirtualBox - Error
Failed to open a session for the virtual machine dans_ubuntu
The virtual machine 'dans_ubuntu' has terminated unexpectetdly during startup with exit code 1 (0x1). More details may be available in ...\VBoxStartup.log
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Host: Windows 7 Enterprise, SP1, 64-bit.
Symantec Endpoint Protection version 122.1.5 (12.1 RU5) build 5337.

I too have been having similar problems with all versions since 4.3.12.
The nag that I see is:

Error in supR3HardNtChildPurify
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc = -5673)

(I'll attach the log)

Hi,

I can't start any VM. Win7 64 + Avast.
Thanks.

Edit: VMs don't start even after Avast has been uninstalled.

I too am seeing problems with builds from 4.3.18 and later. I'm using Windows 7 latest SP's as a host and all my VMs fail on.18 and .20 but work on .16

I've attached a startup log file from a fail when running 4.3.20 with a Windows guest. This also happens with a Ubuntu guest.

Thank you for your help with this.


ps. Below is the error message:

Failed to open a session for the virtual machine DP Scrpt VS2010.
The virtual machine 'DP Scrpt VS2010' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\VMStore\DP Scrpt VS2010\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

4.3.20 Yet another FAIL!!

HOST OS = WINDOWS 7 64 BIT

VBOXSTARTUP zip ENCLOSED

AV = Microsoft Security Essentials
Firewall = default that comes with Win7

UI err messages below:

----------------------------------------

Failed to create the VirtualBox COM object.

The application will now terminate.



Callee RC: E_INVALIDARG (0x80070057)



Failed to open a session for the virtual machine slk.

The virtual machine 'slk' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\...\VirtualBox VMs\slk\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Same Problems...

Disappointing that this is going on so long...

I have not been able to use any version above 4.3.12 on a Windows 7 Ultimate x64, 12G RAM on a Corporate Domain with Symantec Endpoint Protection 12.1.3. Have tried various guest OS's (windows and Linux, even Solaris10). See attached zip with startup logs

I concur with jnpapado. No version > 4.3.12 is functional for me. Win 7 Pro 64 bit. Trend Micro Office Scan 6 (installed by corporate policy). Startup log attached.

I experience an issue related to security as well.
System:
Dell Vostro 2521-9566
Windows 8.1 Pro x64
Security software:
-Windows Defender 4.6.305.0;
-Malwarebytes Anti-Malware 2.0.4.1028.
Tests indicate that Malwarebytes doesn't cause any problems.
The interesting part is that, the issue can temporarily be prevented by following this steps:
1. Check if Fast startup is enabled, if it's not, it must be enabled;
2. Turn off Windows Defender;
3. Shut down computer;
4. Start Virtualbox and any virtual machine preferred (it will boot successfully this time);
5. While virtual machine is running turn Windows Defender back on.
Virtualbox will work until fast startup system image is flushed which happens in any of these scenarios:
-fast startup is disabled;
-system is restarted (power command 'Restart' is designed this way);
-most applications with built-in Auto-shutdown on complete task functionality implemented. This functionality is often incompatible with fast startup;
-system crash (BSOD).
When issue occurs VirtualBox.exe process cannot be terminated normally and as such it has to be task-killed manually or automatically on log off / shutdown /restart.

@Pal1000: Am I right in thinking that you're using the "Portable VirtualBox" fork? If yes then please be aware that forks are never supported on these forums. In your case it seems that VirtualBox.exe is itself failing the "alien code modules" test, presumably since the executable isn't certified any more.

-

Hello,

I have installed VirtualBox 4.3.21 r97191.

Virtualbox keeps hanging at starting every virtual Machine, no Errors shown - e.g. see Screenshot:


In Virtualbox 4.3.16-r95972 the machines are running fine - even Windows 10

My Hostsystem:

OS Host: Windows 7 Enterprise x64 SP1, fully patched
---------
Security: Symantec Endpoint Protection 12.1.4013.4013, Microsoft EMET 5.0
---------
Guest OS: Windows Server 2008 R2 x64, Debian Testing (Jessie) x64, Windows 10 x64 Technical Preview

Edit: Debian Stable (Wheezy 7.5) x64 & Debian Testing (Jessie) x64 Logs added

@Seeker. Although you say that you have a problem with all VMs, it's unfortunate that all of your logs concern the Windows 10 Technical Preview, which is not a supported guest and therefore might well hang with any version of VirtualBox. There are a number of other basic errors in the VM recipe which I won't go into in this topic.

p.s. It isn't isn't necessary to provide four copies of the VM log. Just one complete VBox.log which shows a legitimate security related problem should be enough, along with the VBoxStartup.log file.