August 17, 2015 11:17 am

Windows 10 virtual machines now available on Microsoft Edge Dev

Today, we have updated the Microsoft Edge Dev site with major fixes and new features, including Windows 10 virtual machines with Microsoft Edge and a faster, clearer platform roadmap. With these features, we are excited to remove the “Beta” tag from Microsoft Edge Dev, and will be redirecting to our new home.

Test your site in Microsoft Edge with free Windows 10 virtual machines

Windows 10 virtual machines are now available with the latest updates to Microsoft Edge and the underlying web platform. With this release, we have automated the process we use to create the virtual machines, so future updates will be available more quickly as the platform is updated. By popular demand, we’ll also be supporting new formats for VMs, starting with Vagrant boxes (with VirtualBox) and QEMU. You can expect to see these starting in the coming weeks. We are also continuing to work on making Microsoft Edge available via Azure RemoteApp and will provide further updates as we make progress.

Bug fixes and improvements

This release includes substantial improvements to accessibility, including improved markup to make the site and tools work better with assistive technologies. We have also updated the Frequently Asked Questions page for the Windows 10 launch and included some new answers to common questions. Finally, many of our older Test Drive demos have been moved to our GitHub repository, including classics like Fishbowl and MazeSolver. We plan to move these to our new Test Drive site in the future, but for now you can experiment with the open-sourced copies on GitHub.

As always, we hope these changes are useful, and encourage you to try the new features out and share your feedback! We’re always listening on @MSEdgeDev on Twitter and in the comments below.

Antón Molleda, Program Manager, Microsoft Edge

Updated June 28, 2016 4:49 pm

Join the conversation

  1. Awesome work guys! Glad to hear you’ve automated the VM creation process and that Vagrant is still on the roadmap!

  2. Awesome! It’s so nice to have the Windows 10 VMs available now. I tried the VirtualBox out last night on my Ubuntu machine. I was quite pleased that the latest 5.0.2 Guest Additions were already installed for VirtualBox. But I noticed no sound device was installed by default. My only real problem was that the vmdk file was only allocated to a virtual 40GB and I extended it manually using VirtualBox’s clonehd command and then extended the volume logically using the Disk Manager. On most days, 40 GB would be more than enough but it’s really not once you install SQL Server 2014 Express with SP1 and Visual Studio 2015 Community edition. It would be nice to have instructions available for others who might decide they need more logical disk space. But what a great VM to make available! Thank you.

  3. Why is there a difference in host OS? Aren’t VM’s supposed to be identical for any host OS? What’s the difference between, say, Virtualbox/Windows images, and Virtualbox/Linux images? And why is that difference there?

  4. First start of virtual Microsoft Edge.Win10.For.Windows for HyperV under Hyper-V 2012 R2 I can see Windows Licence is expiring. When I try activet I get Error code:0xC004F009 – The Software Licencing Service reported that grace period expired. With version for VMware ESXI I don’t have a problem. 90 day period start.

  5. Having trouble with the MSEdge on Win10 VM. I have downloaded it twice over the past few days, and got different size files both times. When I unpack them with 7-zip, I get two errors, but do get the OVA file. When I try to import the OVA, I get about 25% through, and then get a message about “compressed image is corrupted”. What size zip file should I see after download? Is there any way to verify the downloaded zip file? Thanks.

          • Thanks. I guess the 3rd time is a charm. File size matched and was able to import the VM. When I start the VM, I receive this error: “VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.” Any comments?
            Also, in the VM configuration, Basic tab of the General section, the Version is Windows 7(32-bit). Is this correct?

  6. Hi,
    I’ve downloaded the Edge-Win10 Vmware image and have a few issues. When I first launch Edge, I’m told that a newer version is available, which I’ve downloaded but then doesn’t boot properly? It also seems that the ‘newer’ version is an older date so it this correct? No problem, I’ve just used the one available on the site and ignored the message built into the VM.

    Secondly, and more importantly is the ‘know issue’ that you cannot activate the OS. You state that this doesn’t affect the usability, but it does because the OS will shut down every hour, which is infuriating. Can you fix this please?


  7. As a note, the virtualbox appliances have audio disabled on them, you may want to set that to “Intel HD Audio” for future builds.

  8. Why are you not updating the VMs? Latest Edge is 25.10586.63.0 while the VMs are still on 20.10240.16384.0 from August 2015.

    • Thank you for providing these VMs, it really makes supporting IE and Edge much easier. Is there any hope for another VM that has the second (or latest stable) release of Edge? The current Win10 / Edge VM comes with Edge version “20.10240”. I tried using Windows Update inside the VM to get version “25.10586” which has been out since November 5th. Windows Update installed a few updates, but nothing for Edge. It now says that everything is up to date even though Edge is still at version “20.10240”. Also I tried opting in to Insider Updates and tried the process all over and still there is no update for Edge. Thank you for your help!

      This is where I am seeing the versions and release history for Edge. I’ve seen actual devices running the “25.10586” version of Edge, but the VM doesn’t seem to have it available.