Vagrant image can't be used non-interactively (Microsoft Edge on Win 10 Stable,14.14393)

By design Issue #8671134


Simon B.
Aug 27, 2016
This issue is public.
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

I’m trying to use the vagrant image provided here:
on OS X. When using vagrant up, the startup gets stuck at:

==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: WinRM address:
    default: WinRM username: IEUser
    default: WinRM execution_time_limit: PT2H
    default: WinRM transport: negotiate

Accessing the image via the VirtualBox GUI, it appears that WinRM is running, but blocked by the firewall. Running winrm quickconfig -q I get the following message:

WinRM firewall exception will not work since one of the network connection types on this machine is set to public. Change the network connection type to either Domain or Private and try again.

The situation can be remedied by running winrm quickconfig -force as an administrator (or, presumably, by changing the network type as suggested), but this can’t be done without manual intervention, and so it is not possible to perform vagrant provisioning entirely from a script.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To to “Praveen B.”

      Changed Assigned To from “Praveen B.” to “Ping D.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Ping D.” to “Hossam F.”

    • @Simon, I created a Vagrantfile able to change network category (private) and activate WinRM automatically.

      See for more details.

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “By design”

    • Does the change of status mean that this is not going to be fixed?

    • I release a new version of Vagrantfile. It’s able to change network category.


    • Hello,

      Thank you for providing this information about the issue. This is blocked by the Firewall because the connection is Public. Changing the connection to Private or Domain will cause it to not be blocked by Firewall. Please update this case if you can provide new information for us to consider.

      Best Wishes,
      The MS Edge Team

    • please connect with Microsoft windows 10

    • please connect me with Microsoft windows 10

    • Hello all,

      This issue has been fixed or there are working versions of Windows 10 using hyper-V and virtualBox.  You can use an External Switch type as well.

      Here is one such example:

      • If using hyper-V, set the default provider permanently for your account using an Admin PowerShell
        [Environment]::SetEnvironmentVariable("VAGRANT_DEFAULT_PROVIDER", "hyperv", “User”)
      • I used git bash (ran as Admin as well)
        vagrant init gusztavvargadr/w10e
        vagrant up
      • Open Hyper-V Manager and connect to the instance

      @ Jennifer, the Windows 10 support is at the following URL:


    • Forgot to mention that this will setup an evaluation version of Windows 10.  Version 15063.674.

    • I also assumed that hyper-V is installed and functional.  This requires Windows 10 Pro and requires checking a box.  :-D

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

    Sign in