virtualbox.org

Topic locked. Continue the discussion here: viewtopic.php?f=6&t=67840

---- original message text follows.

Continuation of viewtopic.php?f=6&t=66400 for VirtualBox version 4.3.26.

This topic is specifically for Windows users that may still have issues seen in version 4.3.26 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 through 4.3.24) 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.

Test builds (when available) can be found here: https://www.virtualbox.org/wiki/Testbuilds

I can report that Virtual Box 4.3.26 is working for 32 bit XP/Linux guests on a 64 bit Win 8.1 host (with Comodo Internet Security 8.1) (as 4.3.24 and the 4.3.25 test build did also).
I will report on Symantec Endpoint Protection 12.1 RU5 as an AV on the host system shortly.

With VirtualBox version 4.3.26 I am experiencing "Error In supR3HardenedWinSpawn". This occurs with all existing VMs. I don't recall when the error first began, but it has been present for the last 3 or 4 main versions of VBox. I have also included screenshots of the error windows.

1. Windows 7 Professional x64 - all recommended updates installed.
2. See one example VM attached.
3. Microsoft Security Essentials, standard Windows firewall, Malwarebytes Anti-Malware installed, but not running.

Update: After a complete uninstall, reboot and fresh install of VBox, all my VMs are working again.

Many [lacks WinVerifyTrust] for system DLLs. Looks like you got hit by the broken Windows update which destroyed the certificate db.

Martin wrote:Many [lacks WinVerifyTrust] for system DLLs. Looks like you got hit by the broken Windows update which destroyed the certificate db.

I admit I haven't read through the hundreds of posts, so I apologize for being "that guy". That being said, is there a recommended course of action to resolve the errors?
Thanks!

mikesheadroom wrote:is there a recommended course of action to resolve the errors?

Google for "KB3004394".

Started getting "Error In supR3HardenedWinSpawn" errors after the latest Windows update on WIndows 8.1. (I believe the update happened last week? Can't remember. I was out of town.)

Running VirtualBox 4.3.26 r98988.
Windows 8.1 64bit host in a relatively vanilla configuration.
Microsoft Defender (built in to Windows 8.1). No other security products installed.

Happens when trying to start any VM, regardless of guest OS. Attached an example startup log from attempting to start one of of my VMs.

Really sucks. I'm locked out of all my development VMs at this point.

Edit:
Output from: sc.exe query vboxdrv

You can always revert to VirtualBox 4.3.12 in the meantime.

Reverting to 4.3.12 results in the following error in some key VMs that I need to run:

Unsupported version 14 of data unit 'vga' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).

Virtualbox was running until 2 weeks ago. Today had the failure with version 4.3.22 and now, after the update, with version 4.3.26.

1) Host: Windows XP SP3 + all published updates
2) attached logs for Windows XP guest and Windows 7 guest
3) Avira free antivirus V 15.0.8.650, no firewalls. Edit:
Output from: sc.exe query vboxdrv

johnkiel wrote:Reverting to 4.3.12 results in the following error in some key VMs that I need to run:

Unsupported version 14 of data unit 'vga' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).

Discard saved states before updating VirtualBox, especially if going backwards.

p.s. No more discussion of 4.3.12 in this topic pls.

31f4.3374: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on '\Device\HarddiskVolume1\Program Files\NVIDIA Corporation\coprocmanager\nvdxgiwrapx.dll'
31f4.3374: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on '\Device\HarddiskVolume1\Program Files\NVIDIA Corporation\coprocmanager\Nvd3d9wrapx.dll'
31f4.3374: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on '\Device\HarddiskVolume1\Windows\System32\nvinitx.dll'

Please can someone confirm this is being looked at? Self signed wasn't supposed to trip the new security...

Could somebody responsible for hardening on WIndows please contact me about coexisting with DigitalGuardian. I am a developer from DigitalGuardian and the hardening is keeping our customers from being able run Virtual Box with our software.

lud1 wrote:Could somebody responsible for hardening on WIndows please contact me about coexisting with DigitalGuardian. I am a developer from DigitalGuardian and the hardening is keeping our customers from being able run Virtual Box with our software.

You should use IRC or the DEVs mailing list
https://www.virtualbox.org/wiki/Community

Hello,
No go with the latest build.

OS - Win7 Professional 64bit - SP1
Trendmicro Office Scan - 11.0.1454
Virtualbox - 4.3.26

Screen shot and startup log attached.

I am happy to assist with debugging. Are there any switches or process that would provide additional diagnostic information?

Thanks,
Richard