I updated to 6.1.6 from 6.1.x this week and after the update VBox fails to open. I have tried everything however the only solution thus far has been to reinstall 5.2.x .
Windows 10 (Current)
Launch error:
Completely failed to instantiate CLSID_VirtualBox: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D. Result Code: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D (0x8007041D) Component: VirtualBoxClientWrap Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}
A couple of points:
1. Was using a new AV software. Uninstalled it and reinstalled VBox, no luck.
2. Was recently trying to run alongside Hyper-V. Hyper-V had been uninstalled and this error was never present while attempting this.
Repairs attempted:
1. Reinstall 6.1.6, 6.0.18, and finally 5.2.40. Vbox launches with 5.2 but errors the same on 6.0 and 6.1. Installed as admin and converted standard user to admin. Install completes successfully on all versions.
2. Delete .VirtualBox folder form EVERY PROFILE.
3. Manually delete every VBOX or VIRTUALBOX registry key.
4. Attempt to manually start vbox service present in 6.1.
5. Disable firewall and Windows Defender.
6. Update from functional 5.2.40 version.
7. Search for similar issues on the forum...
If anyone has another suggestion I would appreciate it very much.
Unable to start after update to 6.1.6. Only fix is ver 5.2.
Re: Unable to start after update to 6.1.6. Only fix is ver 5.2.
I'm having the same issue here, looks like the VBoxSDS.exe service fails to start, It's probably buried in the registry somewhere, no one around here to help though.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Unable to start after update to 6.1.6. Only fix is ver 5.2.
@IamUSER, sorry we missed this one.
Googling
"Completely failed to instantiate CLSID_VirtualBox" site:forums.virtualbox.org
shows that Virtualbox may not have been installed properly, or that the account you are using might be bunged up. Other suggestions can be found. Unfortunately we can't figure it out from here except to suggest web-searching the error and see what has worked for others.
@bnbx, also try the suggested search. If you have trouble, please start a new topic.
Googling
"Completely failed to instantiate CLSID_VirtualBox" site:forums.virtualbox.org
shows that Virtualbox may not have been installed properly, or that the account you are using might be bunged up. Other suggestions can be found. Unfortunately we can't figure it out from here except to suggest web-searching the error and see what has worked for others.
@bnbx, also try the suggested search. If you have trouble, please start a new topic.
Re: Unable to start after update to 6.1.6. Only fix is ver 5.2.
Thanks for the reply. I googled my tail off looking for ideas unfortunately the final resort was a Windows 10 Refresh. On the bright side I can run VBox and Hyoer-V together. Very poor performance but one step closer to awesomeness! Reinstallation did not work. Clearing out all the VM's and the .virtualbox folders, etc... Reregistered the service too! This was one of the hardest to solve issues I've ever found with any software. Good thing I was ready to reinstall EVERYTHING lol.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Unable to start after update to 6.1.6. Only fix is ver 5.2.
Sorry we couldn't give you more help. Glad you're up and running!