virtualbox.org

Host is Win 10 Home up to date
intel i7-6700
16gb ram
I even tried a reboot, but to no avail.
Vbox output message ....

Failed to acquire the VirtualBox COM object.

The application will now terminate.

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.

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

Hi

I am running Windows 10 1803/x64 on an AMD A8.

I've downloaded both 6.0 Beta 3 and today 6.0 RC1.

I installed RC1 and it crashed with the following error;

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.

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

I've uninstalled it and reinstalled Beta 3; Beta 3 runs with no apparent problems. I uninstalled Beta 3 and reinstalled RC1 and it crashes.

Unless there's something you want me to do or try, I'll uninstall and wait for RC 2 and see if that works instead. I'll keep RC1 installed for a little while and watch this thread before I do, though.

Thank you for everything!

Btw the way, I did some googling and copied the VirtualBox.xml-prev to Virtualbox.xml and that didn't seem to help, neither did removing the old .Virtualbox folder (which I renamed instead of deleting, so my Beta 3 settings wouldn't be lost).

The only tip I've read that I haven't tried has been trying to run the executable in compatibility mode.

more info to add to my earlier post.
1) This is Win10 1809
2) This same message occurs when I try to just start VBOX 6.0.RC1 without the extpack installed.
3) This was an upgrade from beta 3.

Thanks,
John

I tried it on a Win10 1607, 64-bit VM and I had no problem installing VirtualBox or the ExtPack. Are you using any 3rd party antivirus by any chance?

@rliegh
I've merged your posts with the posts of "jrc55", you seem to have the exact same problem. So, both 1803 and 1809 seem to fail, 1607 works. I'll try to upgrade mine to 1809 or even better I'll create a new Win10 Oct1809 and see what happens...

To answer socratis question .... I am running with just the anti-virus that comes with Win 10 Home. No 3rd party products.

Thanks,
jrc55

I'm the same; no third party antivirus, just Windows Defender.

The same problem here, I then uninstalled VirtualBox, deleted the Oracle folder in Program Files and deleted .VirtualBox folder in the user. The first attempt failed again but the second attempt all worked fine.

However, Windows 19H1 (18298.1000.181205, just released to insiders) installed without a sound card (sound hardware missing in the guest). In VMware 15.0.2 it installed without a problem.

I installed Win10 64-bit (Oct1809, 17763.107) in a VM and I was able to install VirtualBox 6.0.0_RC1 (r127378) without any problems.

I even tried to run a DOS VM, something that I was able to do in the past, but it went Guru Meditation on me, but that's another story...

@Simple07
I'm not sure if I should leave your message here (since you're talking about the Beta/RC), or if I should move it to the "Windows Pre-releases" area. I'll leave it here for now, but please remember that there's a dedicated area for the pre-release Windows OSes...

And please remember to ZIP your logs, it helps save a (virtual) tree or two...

Virtualbox 6 rc1 version is not working. I did clean installation, it still didn't work.

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.

REGDB_E_CLASSNOTREG (0x80040154)
Bileşen:
VirtualBoxClientWrap
Arayüz:
IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Windows 10

I deleted the .VirtualBox folder in the user folder. Now work.

C:\Users\"user"\.VirtualBox

I just got another report on the IRC channel about a Win10, 1803, 64-bit, Home version failing. Can you please all involved state the complete version of your host? The only one I know so far completely is from "jrc55" and the one from "marcoagpinto" from the IRC:

• jrc55: Win10, 1809, 64-bit, Home.
• marcoagpinto: Win10, 1803, 64-bit, Home.

@zbahadir
I merged your posts with the topic that is already dealing with this issue. Can you please state your complete host version? See my previous post for two examples...

Same here but a Windows 8.1 x64 Pro 6.3.9600 Host. Usually when this happend previously a one time repair install would work. Not this time.