Vagrant image fails to "vagrant up", when using ssh to configure it

Site Outreach Issue #13592617


David L.
Sep 5, 2017
This issue is public.
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

The Vagrant vm box, "Microsoft/EdgeOnWindows10", fails to successfully initialize, after a “vagrant up” command is issued. The VM appears to get created, and will launch, however it appears to fail when creating a “/vagrant” directory, on the guest OS.

This has the end effect of “vagrant up” returning an exit code of 1, indicating that an error occurred. This prevents accurate, scriptable detection of the VM being booted, successfully.

Here is the Vagrantfile that is being used:

Vagrant.configure("2") do |config| = "Microsoft/EdgeOnWindows10"
  config.ssh.password = "Passw0rd!"
  config.ssh.username = "IEUser"

Here is the result of running “vagrant up” on the machine, via a host machine running macOS 10.12.6:

davidl@Wart ~/Documents/Code/vagrant_test/windows_2 $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'Microsoft/EdgeOnWindows10'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: windows_2_default_1504648551856_22808
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address:
    default: SSH username: IEUser
    default: SSH auth method: password
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: Guest Additions Version: 5.0.2
    default: VirtualBox Version: 5.1
==> default: Mounting shared folders...
    default: /vagrant => /Users/davidl/Documents/Code/vagrant_test/windows_2
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p /vagrant

Stdout from the command:

Stderr from the command:

davidl@Wart ~/Documents/Code/vagrant_test/windows_2 $ echo $?
davidl@Wart ~/Documents/Code/vagrant_test/windows_2 $


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • I’m getting the same issue. It seems like this has been reported before on I’ve tried configuring the box’s winrm settings but that also times out.

        config.vm.guest = :windows
        config.vm.communicator = "winrm"
        config.winrm.username = "IEUser"
        config.winrm.password = "Passw0rd!"
    • Microsoft Edge Team

      Changed Assigned To to “”

      Changed Assigned To to “Anton M.”

      Changed Status to “Site Outreach”

    • Do you mind testing with the latest available version (17134) and if you keep having problems please open an issue in where we have the scripts used for creating the VMs.


    You need to sign in to your Microsoft account to add a comment.

    Sign in