VirtualBox

Ticket #14319 (closed defect: worksforme)

Opened 4 years ago

Last modified 3 years ago

5.0.0 fails to start (Win7/32-bit)

Reported by: ColH Owned by:
Component: installer Version: VirtualBox 5.0.0
Keywords: Cc:
Guest type: all Host type: Windows

Description

Please see forum post  https://forums.virtualbox.org/viewtopic.php?f=6&t=69084 I've tried numerous routes to get VB to start up - the only success I've had was to set virtualbox.exe to Vista Compatibility mode - it would then start, and create a vm and virtual disk, but the vm will not start. I'm happy to try to analyse what's going on, if you can give some advise on how to get to the bottom of it (how can I trace what file/registry access is broken?)

Latest VboxSVC.log attached. Note however that the on-screen error is "Failed to create the VirtualBoxClient COM object. The application will now terminate. Callee RC: REGDB_E_CLASSNOTREG (0x80040154)"

Attachments

VBoxSVC.log Download (1.8 KB) - added by ColH 4 years ago.
MSI3eb19.zip Download (64.1 KB) - added by ColH 4 years ago.
Installer log
VBoxInstallLog_Uninst_1509080817.txt Download (349.5 KB) - added by ColH 4 years ago.
VBoxInstallLog_Inst_1509080821.txt Download (429.7 KB) - added by ColH 4 years ago.
snag-0003.jpg Download (30.5 KB) - added by EliasP 4 years ago.
VBoxHardening.log Download (256.0 KB) - added by EliasP 4 years ago.

Change History

comment:1 Changed 4 years ago by ColH

This may not be relevant at all but I've seen mentioned, in another ticket (12087), the registry key along the lines of "00020424-0000-0000-C000-000000000046". In a procmon trace I see do see for the VBoxSVC.exe process: "HKCU\Software\Classes\CLSID\{00020424-0000-0000-C000-000000000046}" giving a "Name Not Found" message. I *do* have that key in "HKCR\CLSID\", not in HKCU.

Version 0, edited 4 years ago by ColH (next)

Changed 4 years ago by ColH

Changed 4 years ago by ColH

Installer log

comment:2 Changed 4 years ago by frank

Any change with VBox 5.0.2?

comment:3 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

comment:4 Changed 4 years ago by ColH

  • Status changed from closed to reopened
  • Resolution fixed deleted

Sorry, have been away on holiday. No change with 5.0.2 - still the same error ("REGDB_E_CLASSNOTREG").

comment:5 Changed 4 years ago by frank

What happens if you completely uninstall VirtualBox, reboot the host and re-install VirtualBox?

comment:6 Changed 4 years ago by ColH

Tried that a few times with the previous version, but ok. What do I need to do to "completely uninstall" - just from Control Panel, or is there more I should clear out in registry etc? (Btw - is there a way to get email notifications when a reply is posted?)

comment:7 Changed 4 years ago by frank

Just complete uninstall from the control panel.

comment:8 Changed 4 years ago by VVP

It would be better if you run uninstall with logging (--logging) from the command line. You can run the same installer which you have used to install the current version from the command line with "--logging" option. Next, do the same for install process. And upload log files here. Maybe, there are some issues in uninstall/install process.

comment:9 Changed 4 years ago by ColH

Thanks - will do. Could you confirm exactly where/what I need to run to uninstall from the command line - I don't want to lose the log.

comment:10 Changed 4 years ago by ColH

And whether to open an Administrator command prompt or not.

comment:11 Changed 4 years ago by VVP

ColH, run the same installation executable file which you used to install and add "--logging" option. For example, you uses VirtualBox 5.0.0 r101573, so you run "VirtualBox-5.0.0-101573-Win.exe --logging". The installer will offer you two choices "repair" or "uninstall". click uninstall. Log file will be stored in the C:\Users\<user name>\AppData\Local\Temp\VirtualBox\ or similar path. There is no need to open command prompt as Administrator.

Changed 4 years ago by ColH

Changed 4 years ago by ColH

comment:12 Changed 4 years ago by ColH

Logs attached

comment:13 Changed 4 years ago by VVP

At first glance, both log files look normal.

comment:14 Changed 4 years ago by ColH

That's a shame! Do you know what (missing) registry entries etc might generate the error message? Or a way to more-in-depth debug the start-up?

comment:15 Changed 4 years ago by VVP

you wrote:"In a procmon trace I see do see for the VBoxSVC.exe process: "HKCU\Software\Classes\CLSID\{00020424-0000-0000-C000-000000000046}" "

can you provide more information from procmon? you can double click on this line in the procmon and a new window will be opened. There you will see 3 tabs "event", "process" and "stack". What is there?

comment:16 Changed 4 years ago by ColH

Not sure which would be the best line to examine. I'd like to just send the whole [filtered] log, but it's over the attachment size limit.

comment:17 Changed 4 years ago by simonemagnaschi

I have the same exact problem since today. Don't know why. It happened with 5.0.4 after a reboot and since then I uninstalled multiple times adn tried also with 5.0.2. No luck.

If I try to start VBoxSVC.exe from command line or GUI Windows 10 tells me that the file doesn't exist even if it's there and I can read its properties and so on. This happens as a local user or as an administrator. The only way I found to get VB to work in this state is the following:

  • Make a copy of VBoxSVC.exe with other name in the same directory (because, you know, file doesn't exist but it can be copied right? -_-)
  • Start VBoxSVC_Copy.exe
  • Start VirtualBox.exe

Then everything works.

Windows 10 makes me speechless.

comment:18 Changed 4 years ago by simonemagnaschi

Ok, after a lot of troubles I ended up resolving this. The problem lies on the fix that I had installed found here somewhere regarding early network windows 10 issue. The fix let windows 10 work ok with VBox. Since I upgraded to 5.0.4 I deleted the exe with the fix from my computer, and than started the problem (I couldn't relate the two since the problem rose on the next reboot happened days later). After running a search in regedit there was a key somewhere still pointing to the file that for some reason hijacked the VBoxSC.exe execution. Deleting the key everything started to work again.

comment:19 Changed 4 years ago by ColH

Hi, Any further suggestions to my issue?

comment:20 follow-up: ↓ 21 Changed 4 years ago by frank

Still relevant with VBox 5.0.14?

Changed 4 years ago by EliasP

comment:21 in reply to: ↑ 20 Changed 4 years ago by EliasP

Replying to frank:

Still relevant with VBox 5.0.14?

Yes, I installed version 5.0.14 and the problem persists. It started after I uninstalled and re-installed Microsoft Office 2010. I tried setting compatibility mode which starts VBox Manager but the VBox image does not start, even in headless mode.

Changed 4 years ago by EliasP

comment:22 Changed 4 years ago by frank

EliasP, the VBoxHardening.log file does not show a problem. The error message sounds more like the VBoxSVC service could not be started. Does it help if you do the following? Open a command line (cmd.exe) as Administrator:

cd \program files\oracle\virtualbox
vboxsvc /regserver

Then try to start VirtualBox

comment:23 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to worksforme

No response, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use