Docker quick start treminal fails to start on Windows 10 with VBoxManage.exe error

[Napas]

I get this error:

Starting "default"... (default) Check network to re-create if needed... Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed: VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\napas\.docker\machine\machines\default\default\Logs\VBoxHardening.log VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine Looks like something went wrong in step ´Checking status on default´... Press any key to continue...

Log:

VBoxHardening.txt

E:\sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

[dbashyal]

I am also getting error "Looks like something went wrong in step ´Looking for vboxmanage.exe´... Press any key to continue..." when I click on "Docker Quickstart Terminal" on desktop. Win 7/64bits.

I am installing first time to learn docker. Never tried before. So a fix/help would be appreciated.

cmd-install.txt
VBoxHardening.txt
kinetic.txt

[dbashyal]

all good after following this article - http://stackoverflow.com/a/33733486/534525

Uninstall VB and reinstall like this:

c:\downloads\VirtualBox-5.0.11-104101-Win.exe -msiparams NETWORKTYPE=NDIS5

[warpdesign]

@dbashyal Uninstalling VB and reinstalling like this didn't fix it for me. Still getting the same error message.

[aliskov]

@warpdesign Not sure if this will work on W10, but I'm assuming it will. And it's a temp fix.

Locate Users/your_user_name/Documents/.docker/

Delete everything in that folder. Uninstall the toolbox and then reinstall. It fixed it for me. W7 Pro.

[warpdesign]

@aliskov tried that, but no luck again.

Here is what I'm getting:

(default) Check network to re-create if needed...
Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 255 (0xff)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

I guess I'll have to wait to use docker on Windows (10).

[Codesleuth]

Is this really an issue with Windows 10? I would expect far more reports of this. I get the following now:

Starting "default"...
(default) Check network to re-create if needed...
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 255 (0xff)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Looks like something went wrong in step ´Checking status on default´... Press any key to continue...

If I try reinstall Virtual Box, I get the following message popup:

---------------------------
Error Renaming Connection
---------------------------
Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

I think there's an issue with VB not Docker.

[Codesleuth]

Seems to be working following these steps: A connection with the name you specified already exists

[LeandroHotmail]

Dear all, I was with the same error, after install the VB 5.1 the Docker Tools (Kitematic) create the local Container in the VB without any problems and still with the VM created before.

[psi09]

May be u guys have installed the VBOX and docker installation in the different location..check that..would help..

[VedAustin]

I uninstalled VirtualBox and docker and reinstalled docker. Basically I allowed docker to install whatever version of virtual box they had by default - removes any compatability issues b/w virtual box installs downloaded separately from docker's own virtual box installs.

[marcosalberto]

Install Virtual Box with below command solves to me.

VirtualBox-5.0.11-104101-Win.exe -msiparams NETWORKTYPE=NDIS5

There is this option on Docker Toolbox too.

[motatoes]

Well, I had the same error on Windows 10 but I managed to fix it by following the steps bellow:

• I reinstalled docker toolbox from the .exe and made sure that the checkbox "Install VirtualBox with NDIS5 driver" was checked

• I rebooted my machine

• I went to C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv and then right-clicked on VBoxDrv.inf and clicked install

• I opened command prompt with admin rights and then typed in sc start vboxdrv, which outputted:

  SERVICE_NAME: vboxdrv
  TYPE : 1 KERNEL_DRIVER
  STATE : 4 RUNNING
  (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
  WIN32_EXIT_CODE : 0 (0x0)
  SERVICE_EXIT_CODE : 0 (0x0)
  CHECKPOINT : 0x0
  WAIT_HINT : 0x0
  PID : 0
  FLAGS :

Then I launched docker toolbox and it worked!

[kphaser]

I had the same issues as many of you on Win10. I had a previous installation of Oracle VirtualBox on my machine with an old image attached. Uninstalled the VirtualBox and Docker Toolbox and reinstalled Docker Toolbox with defaults. No issues after that!

[marcosalberto]

It's not about this repository, but i installed the latest version of Docker for Windows and worked without problems.

[damtur]

See #487

(I've had run it from command line and NOT by double-clicking the shortcut and it worked)

[fresheneesz]

I'm on windows 8.1 with a fresh install of windows. I installed docker-toolbox and tried running the quickstart terminal. It failed to find bash (duh, its windows). So I install cygwin, but then I get this "something went wrong" 'looking for vboxmanage.exe'. I don't have any previous installation of virtualbox.

[LosFuegos]

For some reason, VirtualBox never installed during the docker install. So I found it.
.../Docker Toolbox\installers\virtualbox\virtualbox.msi
Now I'm up and running.

[szwalkowski]

For me, same error was caused by "cd " in my bash.bashrc ;)
I would rather leave it there tho :(
So someone might use this as a fix. Took this idea from here: http://stackoverflow.com/questions/39373217/docker-looks-something-went-wrong-in-step-looking-for-vboxmanage-exe

[danio]

For me, the virtualbox imager had got damaged in a previous start, so I deleted the VM from VirtualBox manager, and then re-ran Docker quick start terminal

[siripuramrk]

Same problem.
Previously it was running fine with docker v1.12.
I got this problem from upgrading/installing docker toolbox v1.13.

Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed: xxx ......

Any suggestion in fixing?

[bitman]

This worked for me:-

http://stackoverflow.com/questions/34003096/docker-quickstart-terminal-fails-to-start-virtualbox-vm-in-windows-10

[Violet-Bora-Lee]

I've tried all the ways above.
If u couldn't find a way to solve Error: Details: code E_FAIL (0x80004005), try this.

1. Delete Docker Toolbox, Virtual Box
2. Delete everything in the folder, Users/your_user_name/Documents/.docker/ (@aliskov commented)
3. Restart your system
4. Install Docker Toolbox in ADMIN MODE!! <-- this is the way I found!!

[chuck-park]

In my case, removing the docker image of Virtualbox worked. Try removing that, restart the docker-quickstart-terminal.

[msly]

I solved by change VM_STATUS="$(${DOCKER_MACHINE} status ${VM} 2>&1)" to VM_STATUS="$(${DOCKER_MACHINE} status ${VM})" in the file \Docker Toolbox\start.sh,

[dangnguy]

I had similar issues on Windows 7. The only way to resolve for me was to uninstall VirtualBox and Docker Toolbox. Then reinstalled Docker Toolbox taking all defaults.

[jimmy17x]

For me there was no need to re install anything - i just followed the step here to install require driver -
https://stackoverflow.com/a/33733454/2442565

[bytemaestro]

Had to install the version before the hardening checking was being done 4.3.12 and earlier...... only installation of virtual box 4.3.12 worked for me. hopefully we be solution in future versions.

[MaxPeal]

#689 mybe a fix for that?

[ishangajera-crest]

Uninstalling Virtual Box and Reinstalling fixed it for me.

The difference I noticed is when I was getting error while starting the docker quickstart terminal, it wasn't asking for UAC permissions popup required by Virtual Box. I think this might have happened due to windows update or anti virus. Not sure though!

[zhmore]

Just goto you docker installtation directory, double click start.sh. Then it work...
Hope sovle you problem!

[Mickey-Hope]

If you get this message: Looks like something went wrong in step ´Looking for vboxmanage.exe´... Press any key to continue..." when you click on "Docker Quickstart Terminal", try the following.

1. Open Windows Settings and search for "View advanced system settings".
2. Click on "Environment variables...".
3. Locate VBOX_MSI_INSTALL_PATH and make sure you have a backslash () at the end of the path. E.g. D:\Program Files\Oracle\VirtualBox\ and not D:\Program Files\Oracle\VirtualBox
4. Then click "OK" and try run "Docker Quickstart Terminal" again.

This solution fixed it for me (Win 10). If you still got the same error message, you could try removing MSI from the variable. That is, VBOX_INSTALL_PATH

[lucacanella]

Solved on Windows 7 by setting DOCKER_TOOLBOX_INSTALL_PATH variable to "C:\Program Files\Docker Toolbox\" (or whatever your toolbox install path is). Don't know if this is a general fix.
In example this worked by opening a new cmd window and setting this variable:
set DOCKER_TOOLBOX_INSTALL_PATH=C:\Program Files\Docker Toolbox\
then starting toolbox from that same cmd window:
"C:\Program Files\Git\bin\bash.exe" --login -i "C:\Program Files\Docker Toolbox\start.sh"
Setting the variable at system level solved for me.

[blakehawkins]

I've just hit this on windows 7. I closed the window and then waited for VBoxHeadless.exe to start up before trying again - then problem solved.

[LIsmooth]

I got this error in my Win10 too, and I suppose it's because of the Git I have installed before. So I uninstalled all the related software(Virtual Box/Git/Docker ToolBox) and reinstall Docker ToolBox once again, and this problem disappeared!

[pipeacosta]

Hi,

In my case (Windows 10) I had an old installation of Virtual Box, and even though I uninstalled it, I kept experiencing this issue. I solved it by completely uninstalling Virtual Box, i.e. removing the .VirtualBox folder from C:\Users\MyUserName.

Best.

[maximilientoumi]

I reinstalled docker toolbox from scratch and made sure that the checkbox "Install VirtualBox with NDIS5 driver" was checked
and run it everything working well know

for windows 10 user running docker on virtualbox make sure to check the default machine's ip by running docker-machine ip cause the localhost here is not 127.0.0.1 but the ip address of your docker-machine
hope this help:)

[jigneshcitrusbug]

Run DockerToolbox as a administrator
Work for me
#Window 10 home

[praveenpetfect]

am getting this message in Docker Quickstart Terminal. "looks like something went wrong in step 'setting env'... Press any key to continue..". am using windows7. please help me.

[bhargavb7]

Is this really an issue with Windows 10? I would expect far more reports of this. I get the following now:

Starting "default"...
(default) Check network to re-create if needed...
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm default --type headless failed:
VBoxManage.exe: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 255 (0xff)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Looks like something went wrong in step ´Checking status on default´... Press any key to continue...

If I try reinstall Virtual Box, I get the following message popup:

---------------------------
Error Renaming Connection
---------------------------
Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

I think there's an issue with VB not Docker.

were you able to resolve the error

[ScarletMcLearn]

Same thing with me!

Why doesn't Docker release an updated version for W10 Home edition?

[fredericfaure]

With a clean install of oracle virtual box I did not have the problem.

[khorramk]

i was having the same issue. running the docker toolbox desktop app as administrator worked for me.

[signed-log]

Same thing with me!

Why doesn't Docker release an updated version for W10 Home edition?

Because of the lack on Hyper-V support on Home

[signed-log]

i was having the same issue. running the docker toolbox desktop app as administrator worked for me.

Not working

[CorentinJ]

Of all the steps above, the one that made a difference was actually rebooting my computer 😅

[RealNameHidden]

@warpdesign Not sure if this will work on W10, but I'm assuming it will. And it's a temp fix.

Locate Users/your_user_name/Documents/.docker/

Delete everything in that folder. Uninstall the toolbox and then reinstall. It fixed it for me. W7 Pro.

Thank you

[BobbyZ04]

May be u guys have installed the VBOX and docker installation in the different location..check that..would help..

So if they are already in different location, how can I do to fix it? add path or something else?

[lticoeadmin]

This solution worked for me on Windows 10.

1 - Open Windows Network Connections
2 - Right click on VirtualBox Host only adapter that created
3 - Choose properties
4 - Check "VirtualBox NDIS6 Bridged Networking driver"
5 - disable and Enable the adapter

Restart the system and relaunch docker quickstart terminal

[swilliams-alison]

friends ... i just re-installed VirtualBox [ Version 5.2.4 r119785 (Qt5.6.2) ] and the problem just went away ... :-)

VB 5.2.34 worked for me

[2258324319]

it's the problem of virtualBox!!!! I remember that my teacher once sent me an VirtualBox which was avaliable,so I find it and reinstall the toolBox without choosing VirtualBox of itself,and it now goes well...perfect

[AndreLuisGO]

After several reinstallations, I got it working by:

1 - Uninstall everything.
2 - Restart your PC (very important).
3 - Install VirtualBox (and if needed, reinstall the microsoft KM-TEST network adapter driver
4 - Restart your PC
5 - Install Docker Toolbox
6 - Restart your PC
7 - Run docker terminal in admin mode.

[mpuczynski]

There is something wrong with the bash.exe included in with the package.
The command testing the status of > docker-machine status default
fails, and the code: $( set -e ; docker-machine status default ) triggers the error handler....
However the same script run in the environment of parallel install of GIT runs smoothly.
So, I replaced the original command in the desktop shortcut for "Docker Quickstart Terminal" to:
"C:\Program Files\Git\git-bash.exe" "C:\Program Files\Docker Toolbox\start.sh"
and it starts smoothly....
BTW. I have VirtualBox upgraded to latest version (6.1.4) and docker-toolbox is also brand-new.

[gbengafagbola]

I had similar issue also, but I deleted the .Virtualbox folder & .docker folder in my user directory, then ran the app and it worked

[sreetejarusum]

This happens when the user connects to some sort of secured networks using VPN, TLS machine certs gets messed up, upon restarting machine and regenerating TLS machine certs, docker toolbox is configured to use the default machine with IP 192.168.XX.XX