loader wrote:VirtualBox 4.3.20
Does not work since 4.3.14 on all our computers with CryptoPro cryptografic software installed (Windows XP, Windows 7, Windows 8.1).
cadespluginucsp.exe v3.9.8209 (test build) --> The virtual machine has terminated unexpectedly during startup with exit code 1073741819 (0xc0000005) [E_FAIL 0x80004005]
cadespluginucsp.exe v3.6.6785 (official build) --> BSOD (CProCtrl.sys)
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\CProExclude\VirtualBox]
"FileName"="VirtualBox.exe"
Failed to open a session for the virtual machine Ubuntu Linux.
The virtual machine 'Ubuntu Linux' has terminated unexpectedly during startup with exit code -1073741424 (0xc0000190). More details may be available in 'C:\Users\gburke\VirtualBox VMs\Ubuntu Linux\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Virtual Box: tried 3 different versions: 4.3.18 r96516, 4.3.20 r96997, 4.3.21 r97569
on Windows 64bit v8.0 (Version 6.2, Build 9200)
Symantec Endpoint Protection 12.1.5 (12.1 RU5) build 5337 (12.1.5337.5000)
Edit: Rolling back to 4.3.12 (which I had in my download folder) has fixed the issue, so I can continue with that until this issue is resolved.
All was working well for me until today. I had VirtualBox 4.3.18 installed. I then tried the 2 other version mentioned above and got the same error.
Last week, a forced update to SEP was installed but required a reboot. I didn't reboot until I turned off on Friday and on again this morning (opting to sleep instead each evening).
While I've no doubt that Windows Update has been an issue for some people. For others including myself, the Windows Update did NOT cause problems.
The common denominator for me and many others (since July 2014) is Symantec Endpoint Protection 12.1. RU5, which seems to be particularly incompatible with VBox 4.3.14+ (specifically no builds since 4.3.17 bld 96342, work with it).
I've sent in many logs etc as have others, for many of us we can't turn off the device/application management settings in it. I've written to Symantec about it also.
Is there anything we can do to run VBox builds > 4.3.12 on it, reliably?
@Mike: I didn't say that everyone had the Windows update problem, I said that "gburke" did. It's quite obvious if you look at his log file, so I'm not sure what your point is.
pal1000 wrote:Microsoft Windows 7 Home Premium SP1 x64 patched to date. Had the taboo windows update, but it was removed via it's follow-up update (no manual update uninstall). Virtualbox has not been started in between.
Microsoft Security Essentials: 4.6.305;
Malwarebytes Anti-Malware 2.0.4.028;
This issue happens randomly sometimes. It goes away after reboot, but it can happen anytime (race condition - like behavior).
Fortunately it doesn't happen often. Chances don't exceed 10%.
Error signature is identical to the one from here: viewtopic.php?f=6&t=64777&start=30#p306213
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.
This issue mostly happens if I open Virtualbox while a web browser is running. This scenario makes the security software over-thinking things and blocks Virtualbox. Disable real-time protection + re-log on is not enough to lift the ban, have to reboot.
Good news. This seams to be no longer reproducible in v4.3.21-97569.
After trying Malwarebytes Anti-Exploit Free, which disappointed me, this seams to be back.
New log attached:
After reading the log it appears it conflicts with MBAMSwissArmy.sys, a MalwareBytes Anti-Malware protection driver. As I said before it is most likely to happen if a web browser is running or already ran during same windows session.
@pal1000: We do not support VirtualBox forks on these forums. Please go to the Portable VirtualBox forums (if they have any) for support, or install the official version.
@MagFlip: see my answer to gburke. Your issue seems identical.
VBoxStartup.log wrote:
1054.119c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
Edit: Hmm. Nope, I take that back. You seem to be running Windows 8.1, not Win7. This is the first I've seen of these symptoms on a Win8.1 host. Is it 32bit?
@mpack - To what MikeDiack was saying a few posts back...
Can you confirm whether the issue that we are experiencing, that is separate from the Microsoft patching issues and seems to possibly be SEP related with VBox 4.3.18 and higher, is being investigated by anyone? I have only heard chatter regarding the other (known) problems that have been encountered around MS patches.
Can you provide any update on the issue causing the "Creating process for virtual machine..." stuck dialog window? Are you in agreement that this is indeed a different issue?
I greatly appreciate the time that everyone on here takes to make sure this product is as stable as possible. I just don't want this one to get lost among the others.
From my search, it looks like the following users have reported this specific issue: myself, rbal, ICE-vn, & MikeDiack.
Also, not sure if this helps (it's probably been seen already since it was in one of the logs I posted earlier), but here is a "failure" message that I noticed in a 4.3.20 startup log, including a bit of the log before and after as well for reference...
Windows 7 x64 SP1 patched to date
Microsoft Security Essentials 4.6.305.0;
Malwarebytes Anti-Malware Premium 2.0.4.1028
Installed Virtualbox 4.3.21-97569. Did this after short web browsing session. At the end of installation it asked for a reboot. I am very familiar with the fact that ask for reboot =failed installation. Rebooting doesn't solve the problem. Ran Virtualbox and the failing results are embedded. Checking driver status with
results in not found error. So the driver was rejected from installation by security software. Got the VM running by rebooting the host and then running the installer again in repair mode.
pal1000.vbox.log wrote:
4f4.5c0: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\kernel32.dll [lacks WinVerifyTrust]