NOTE 12th Dec: if you have a Windows 7 host that started failing in the last few days then this is most like due to buggy Windows update KB3004394. Microsoft have released a fix here. Do not post about your problem until you have tried their fix. While this Windows bug does trip over the VirtualBox hardening feature, it is not caused by it, and therefore is not a problem that should be discussed in this topic.
This topic is specifically for Windows users that may still have issues seen in version 4.3.20 caused by security being strengthened.
If you want to be taken seriously you need to post a few items as attachments (compressed is preferred)
1) Host OS and version
2) VBoxStartup.log (zipped)
3) Mention any host anti-virus, firewalls, protection software, and debugging programs etc which might be relevant.
As in the previous (4.3.14, 4.3.16, 4.3.18) discussions, the purpose of this topic is to gather diagnostic data needed to solve the hardening issues, and nothing else. Wibble posts, opinion posts, and posts that don't include necessary diagnostics will most likely be deleted. If a test build is created then you'll be expected to have tried it before you post.
Please be explicit about errors. Don't say "same as xxxxx". See list above for what's required.
I thought we'd best create this, as people are posting 4.3.20 problems at the end of the 4.3.18 thread...
Please post entries here
Early signs are that:
Comodo has problems with the 4.3.20 build 96996 build.
Symantec Endpoint Protection has problems with the 4.3.20 build 96996 build.
It sounds like Avast is working.
Last edited by mpack on 7. Feb 2015, 16:39, edited 18 times in total.
Reason:Add standard preamble.
Starting with VirtualBox v4.3.18, including all the VirtualBox v4.3.19 Test-Builds and the VirtualBox v4.3.20 Release-Build, the following error occurs with all VM's (32-Bit and 64-Bit) that I try to launch under Windows 7 (x64):
The last VirtualBox version that was still working under Windows 7 (x64) was v4.3.16. Pleaser fix this serious regression...
(At least restoring the "working" state from v4.3.16 would be a first step )
Host System: Windows 7 (x64), Service Pack 1, fully patched
Antivirus: Microsoft Security Essentials
Firewall: None (except for the standard Windows Firewall, of course)
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.
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.
Resolved problem for me too... thank you very much...
Regards...
I'm running VirtualBox 4.3.20 on fully up-to-date Windows 8.1. I already tried disabling anti-virus (Eset 8 Smart Security) but it doesn't change anything.
Version 4.2.12 works without a problem.
As with previous builds, the release version of 4.3.20 is not working for me. SFC /SCANNOW has not found anything. Restarting has not changed anything. Will try removing A/V to see if that changes anything.
Error message when trying to start up virtual machine that previously worked with 4.3.12 (last usable version)
vbox-4.3.20-error.PNG (9.88 KiB) Viewed 68901 times
Edit: I can confirm in my case that Bitdefender AV Free is the culprit. Disabling the AV had no apparent effect, but uninstalling and rebooting did. I get got an error about the USB 2 controller (as I had not updated the extension pack yet - but disabling that in the VM settings resulting in normal startup). I've attached the log file for the working VM startup.
So deleting posts is the reaction to people making legitimate bug reports? What's the purpose of a discussion forum (and even a dedicated thread!), if feedback is unwanted?
(For the very least, if you delete other people's posts, send a PM to inform those people about this action. And explain why it has been taken)
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.
@Petr Vones:
Peter Vones, thank you very much for this valuable information. Reverting to the standard theme has fixed it for me indeed!
@VirtualBox Developers:
Please add an error message that is at least somewhat expressive, so normal users like me (who are not VirtualBox developers) have a chance to understand why VirtualBox refuses to work.
Please make it clear, on the web-site and in the documentation, that VirtualBox v4.3.18 and v4.3.20 do not work on Windows when custom themes are in place. How could anybody have known that this can be a problem?
Please add an option to allow VirtualBox to operate when custom Windows themes are in place. Security is good, but if VirtualBox dictates the user which themes he/she is allowed to use, then this has gone too far!
Last edited by MuldeR on 25. Nov 2014, 16:40, edited 4 times in total.
Hi,
Just to reeport it is working!
Host : win 8.1 all updates ; KB 3000850 removed
Cpu : intel i5
Dual GPU : Intel 4600 and Nvidia Gt740M
Guest: Linux Mint; Win 10 Preview x32 /x64
AV: Windows Defender and Windows Firewall
Guest Aditions is also working
Some remarks:
I find 4.3.20 is slower than 4.3.12 and seems to me not so responsive to the keyboard. There are some delays on the keystrokes.
I think there is some problem with "Windows Database Update", I am getting error 80070490 when I run the troubleshooting . It says it is repaired but if I run it again the error is still there.
After installing 4.3.20 and re-run that troubleshooting , VB could not start afterwords, there was a msg to re-install it and had some garbage on the msg.
Uninstall VB a re-install it solved the problem.
That error 80070490 was apearing with 4.3.12.
After I uninstaled KB 3000850 the error 80070490 was gone. Next time I removed 4.3.12 it appeared again and I can not get ride of it.
EDIT: 4.3.20 is as quick as 4.3.12 or even more quick. The slowness I exepreeinced above was, may be, because of the first Starts of the Guest's or heavy system activity.
It is the 2nd. time I get a error on closing VirtualBox : There pop's up a Windows saying something like "Runtime error - Pure Virtual Call". it is Microsoft Visual C++ error message. I also have that error in other App.
RelakS wrote:@MuldeR
Let me guess, you were the one who _copied_ the log file instead of attach it.
Nope, you are guessing wrong. Why should I do that? Also, I wonder how this would be relevant to the underlying problem?
(BTW: You could have easily verified that all my error reports always had the corresponding log files attached. Well, at least you could have checked those reports that have not "disappeared" for unknown reasons)
The reason your post disappeared is likely that you suggested that they reconsider forcing this hardened security upon us, creating all of these incompatibilities with antivirus vendors and dll injector programs. The mod(s) don't take kindly to ideas like that, I believe, which is a bit disappointing, since valid concerns/feedback end up getting nuked. It's a sticky situation. Probably best to just keep pointing out the problems, until the developers reach the same conclusion as your proposition.
I've had my posts deleted, and my threads locked, as well. Very frustrating. In fact, I'm uncertain how long this post will remain visible, which makes it very difficult to give feedback.
Failed to open a session for the virtual machine test debian.
The virtual machine 'test debian' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\KHG\VirtualBox VMs\test debian\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Starting with VirtualBox v4.3.18, including all the VirtualBox v4.3.19 Test-Builds and the VirtualBox v4.3.20 Release-Build, the following error occurs with all VM's (32-Bit and 64-Bit) that I try to launch under Windows 7 (x64)...
I'm not 100% sure but I think your problem is fixed in the updated 4.3.20 Windows build (rev 96997, old rev was 96996). Please could you check?
)
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.
