Using Windows 10 Appliance in Ubuntu Virtual Box 4.3.10

First Published: .

blog-carlesmateo-com-microsoft-edgeMicrosoft has released Windows 10, and with it the possibility to Download a Windows 10 Appliance to run under Virtual Box, VMWare player, HyperV (for windows), Parallels (Mac). Their idea is to allow you to test Microsoft Edge new browser in addition of being able to test the older browsers in older VM images.

I wanted to use Windows 10 to check compatibility with my messenger c-client.

Also I wanted to know how Java behaves.

The Windows 10 VM image will work for 90 days. You can download it from here (

Instructions are very precarious and they didn’t specify a minimum version, however if you use Virtual Box under Ubuntu 14.04, so Virtual Box 4.3.10, you’ll not be able to import the Appliance as you’ll get an error.

Update: Thanks to Razvan and Eric!, readers that reported that this also works for Mac OS 10.9.5. + Virtual Box 4.3.12 and VirtualBox 4.3.20 running under Windows 7 respectively.

‘Windows10_64’ is not a valid Guest OS type.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: VirtualBox
Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}


I was looking to find a solution and found no solution on the Internet, so I decided to give a chance and try to fix it by myself.

The error is: ‘Windows10_64’ is not a valid Guest OS type. so obviously, the Windows10_64 is not on the list of the VirtualBox yet, it is a pretty new release. Microsoft could had shipped it with OS Type Windows 64 Other, or Windows 8 64 bits, but they did’t. I wondered if I could edit the image to trick it to appear as a recognized image.

I edited the file (MSEdge – Win10.ova) with Bless Hex Editor, an hexadecimal editor.

I looked for the String “Windows10_64” and found two occurrences.

blog-carlesmateo-com-bless-hex-editor-searchingI had to replace the string and leave it with exact number of bytes it has, so the same length (do not insert additional bytes). I searched for the list of supported OSes and found that “WindowsXP_64” would be a perfect match. I replaced that 10 for XP twice.

blog-carlesmateo-com-bless-hex-editor-windows10_64-to-windowsXP_64Then tried to import the Appliance and it worked.

blog-carlesmateo-com-virtual-box-importing-windows10-appliance-ova-cutblog-carlesmateo-com-bless-applicance-settingsI tried to run it like that, but it froze on the boot, with the new blue logo of windows.

I figured out that Windows XP would probably not be the best similar architecture, so I edited the config and I set Windows 8.1 (64 bit). I also increased the RAM to 4096 MB and set a 32 MB memory for the video card.


Then I just started the VM and everything worked.


Ok, a funny note: Just started, it installed me an update without asking ;)

Views: 36,522 views

16 thoughts on “Using Windows 10 Appliance in Ubuntu Virtual Box 4.3.10

  1. brian

    I had the same problem when when I tried to double click on .ova file on CentOS 6 with VirtualBox 6.1.16. Using the command line worked for me without editing the .ova file : vboxmanage vboxmanage import MSEdge\ -\ Win10.ova

    If I list the OS types from the command line, Windows10_64 is a type: vboxmanage list ostypes

    I assume there is a bug in the GUI side of VirtualBox. Also though I have not tried it, the OS type appears to be able to be overwritten on the command line: OS type … change with “–vsys 0 –ostype “; use “list ostypes” to list all possible values

    1. Carles Mateo Post author

      Hey Brian, thanks for your message. I’m surprised and disappointed that after so long time this has not been fixed!.
      Thanks for your tip for Command Line!. That’s very convenient!.


  2. Ronald Toussaint

    Thanks, great tip!
    If you don’t want to use a hex editor, you can also do the following:

    sed -i -e ‘s/Windows10_64/WindowsXP_64/g’ edge.ova

    (where my virtual machine was renamed to edge.ova :-))

  3. Eric

    Thanks a lot for your post. Also works for VirtualBox 4.3.20 running under Winows 7. ;)
    (SysAdmins won’t update, because of reasons, thy say.)

Rules for writing a Comment

  1. Comments are moderated
  2. I don't publish Spam
  3. Comments with a fake email are not published
  4. Disrespectful comments are not published, even if they have a valid point
  5. Please try to read all the article before asking, as in many cases questions are already responded

Leave a Reply