Starts with E_NOINTERFACE (0x80004002) after installing KB4474419

[Joe Forster/STA]

This is a Windows 7 SP1 x64 host, with VirtualBox 6.1.14. After installing KB4474419 (SHA-2 code signing support update), VirtualBox doesn't start up anymore, dies with the error below. If I uninstall the update, it starts working again. It probably has nothing directly with the SHA-2 code signing - I see the executables are already signed with SHA-256 -, rather some Windows component (kernel, DLL) installed by the update. I noticed exactly the same error with previous VirtualBox versions, too, but I didn't need the Windows updates so I uninstalled them - now I do need the update because my USB audio card's drivers are signed with SHA-256 only.

Code: Select all

Failed to acquire the VirtualBox COM object.

The application will now terminate.

Failed to instantiate CLSID_VirtualBox w/ IVirtualBox, but CLSID_VirtualBox w/ IUnknown works.

PSDispatch looks fine. Weird.

Result Code: E_NOINTERFACE (0x80004002)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

I also tried a very small VBS script:

Code: Select all

MsgBox TypeName(CreateObject("VirtualBox.VirtualBox"))

It shows the same problem: the output is "Unknown" but it should be "IVirtualBox".

Thanks for any help!

[scottgus1]

After installing KB4474419 (SHA-2 code signing support update), VirtualBox doesn't start up anymore, dies with the error below. If I uninstall the update, it starts working again.

What about:

After installing KB4474419 (SHA-2 code signing support update), I then reinstalled VirtualBox.

What happens when yo do this? Right-click the installer and Run As Administrator.

[Joe Forster/STA]

I actually installed the update two weeks ago and installed VirtualBox 6.1.14 today (on top on VirtualBox 6.1.10). But, okay, I uninstalled and reinstalled VirtualBox 6.1.14 right now, it didn't help.

[scottgus1]

Hopefully the reinstall was Run As Admin.

This may be a new glitch. Post on the Bugtracker, and we'll see if further reports come up.

Does 6.1.10 work with the update?

[Joe Forster/STA]

No, the same error existed with 6.1.10, too. I tried reinstalling the first and last patch versions (third version number) of previous major releases (first and second version number). All crash upon startup; 5.0.0 and 5.0.40 give a slightly different error message:

Code: Select all

Failed to create the VirtualBoxClient COM object.

The application will now terminate.

Callee RC: REGDB_E_CLASSNOTREG (0x80040154)

I reinstalled 6.1.14 with option "-l" which created a large log file but I couldn't find any obvious error message in it. I also manually registered all DLL's in the installation directory, and then restarted the VirtualBox service, but it didn't help.

(Edit) VBoxManage gives the same error. For a dummy command:

Code: Select all

vboxmanage createvdi -filename xxx -size 64

I get

Code: Select all

vboxmanage.exe: error: Failed to create the VirtualBox object!
vboxmanage.exe: error: Failed to instantiate CLSID_VirtualBox w/ IVirtualBox, but CLSID_VirtualBox w/ IUnknown works.
vboxmanage.exe: error: PSDispatch looks fine. Weird
vboxmanage.exe: error: Details: code E_NOINTERFACE (0x80004002), component VirtualBoxClientWrap, interface IVirtualBoxClient

(Edit) I did find errors in the setupapi.dev.log file:

Code: Select all

     sto:      {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE} 18:04:41.865
     inf:           Opened INF: 'F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.inf' ([strings])
     sig:           {_VERIFY_FILE_SIGNATURE} 18:04:41.872
     sig:                Key      = VBoxUSB.inf
     sig:                FilePath = F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.inf
     sig:                Catalog  = F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.cat
!    sig:                Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig:                Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     sig:           {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 18:04:41.907
     sig:           {_VERIFY_FILE_SIGNATURE} 18:04:41.908
     sig:                Key      = VBoxUSB.inf
     sig:                FilePath = F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.inf
     sig:                Catalog  = F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.cat
     sig:                Success: File is signed in Authenticode(tm) catalog.
     sig:                Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
     sig:           {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 18:04:41.933
     sto:           Validating driver package files against catalog 'VBoxUSB.cat'.
     sto:           Driver package is valid.
     sto:      {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0x00000000)} 18:04:41.935
     sto:      Verified driver package signature:
     sto:           Digital Signer Score = 0xFF000000
     sto:           Digital Signer Name  = <unknown>
     sto:      {DRIVERSTORE_IMPORT_NOTIFY_BEGIN} 18:04:41.937
     inf:           Opened INF: 'F:\Windows\System32\DriverStore\Temp\{142d2599-caaf-32fc-af2d-380404abac70}\VBoxUSB.inf' ([strings])
     sto:           Create system restore point:
     sto:                Description = Device Driver Package Install: Oracle Corporation Universal Serial Bus controllers
     sto:                Time        = 16ms
     sto:                Status      = 0x00000422 (FAILURE)
     sto:      {DRIVERSTORE_IMPORT_NOTIFY_BEGIN: exit(0x00000000)} 18:04:41.944

and

Code: Select all

     sto:           {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE} 18:05:00.087
     inf:                Opened INF: 'F:\Windows\System32\DriverStore\Temp\{4d626e32-e5ab-4174-ea4a-31322241ec29}\VBoxNetLwf.inf' ([strings])
     sig:                {_VERIFY_FILE_SIGNATURE} 18:05:00.094
     sig:                     Key      = VBoxNetLwf.inf
     sig:                     FilePath = F:\Windows\System32\DriverStore\Temp\{4d626e32-e5ab-4174-ea4a-31322241ec29}\VBoxNetLwf.inf
     sig:                     Catalog  = F:\Windows\System32\DriverStore\Temp\{4d626e32-e5ab-4174-ea4a-31322241ec29}\VBoxNetLwf.cat
!    sig:                     Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig:                     Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     sig:                {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 18:05:00.129
     sig:                {_VERIFY_FILE_SIGNATURE} 18:05:00.130
     sig:                     Key      = VBoxNetLwf.inf
     sig:                     FilePath = F:\Windows\System32\DriverStore\Temp\{4d626e32-e5ab-4174-ea4a-31322241ec29}\VBoxNetLwf.inf
     sig:                     Catalog  = F:\Windows\System32\DriverStore\Temp\{4d626e32-e5ab-4174-ea4a-31322241ec29}\VBoxNetLwf.cat
     sig:                     Success: File is signed in Authenticode(tm) catalog.
     sig:                     Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
     sig:                {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 18:05:00.157
     sto:                Validating driver package files against catalog 'VBoxNetLwf.cat'.
     sto:                Driver package is valid.
     sto:           {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0x00000000)} 18:05:00.159

(Edit) I simply uninstalled the KB4474419 update and rebooted - I did not uninstall or reinstall VirtualBox! - and it starts up without problems. I then reinstalled VirtualBox (6.1.14); the errors above appear again in setupapi.dev.log. So the installation procedure is fine, something else is wrong.

(Edit) I reinstalled the KB4474419 update and VirtualBox again crashes upon startup.