Windows 10: Windows 10 on VirtualBox

I have installed my retail copy of Windows 10 on my main desktop. But before I did this I did the upgrade from Windows 8.1 and then converted the install.esd file into an iso.

How can I activate this virtualbox copy? I thought it would have accepted the key from Windows 8.1?

:)

 

Check your PC - indicates Windows 10 can't be installed because of VirtualBox Graphics Adapter for Windows 8

Those links do not address the reported issue - they apply only to actual hardware, not to VirtualBox. The problem is that the Windows 10 compatibility appraiser does not recognize the VirtualBox display adapter as being compatible with Windows 10. In
fact, it is compatible - numerous people are running Windows 10 Technical Preview in VirtualBox using that configuration. Microsoft needs to update the appraiser application to recognize that the VirtualBox display adapter actually is compatible with Windows
10. For reference, VirtualBox reports its display adapter to Windows as follows:

Manufacturer: InnoTek Systemberatung

Model: VirtualBox Graphics Adapter for Windows 8

Device ID: 80EE-BEEF

Subvendor: 0000

Driver Version: 4.3.28.0

Until Microsoft updates the Compatibility Appraiser to recognize this device as being compatible with Windows 10, there is nothing a user can do to reserve Windows 10 for a Windows system running in VirtualBox. Users will be able to install Windows 10 after
it is released, but they won't be able to reserve it in advance unless Microsoft adds the above adapter to its list of Windows 10 compatible devices.

 

Virtual Box error in windows10

Why does virtualbox only have 32-bit option, no 64-bit option on Windows 10 ?
VirtualBox 5.0.24 for Windows hosts x86/amd64

 

Hello Nick,

I'm afraid that the VM is considered a separate PC, and is why the registered activation of the free Windows 10 for your main desktop was not used to activate the VM. *Sad

 

Anything I can do? I seem to remember back in Windows 7 you could extend the unactivated period.

 

You could try to activate by phone, but I'm not sure how that works without a product key.

 

If I can get through to an actual person perhaps I can explain the situation.

 

That part might be more fun.

 

If you have an old Technical Preview ESD version like 10074*, in the sources folder it contains a pid.txt file, which you can edit to remove the installation code and then enter the proper activation code: 6P99N-YF42M-TPGBG-9VMJP-YKHCF

It activates on installation, the several times I have tried it, then upgrade directly using the Media Creation Tool etc.

* download esd:
Code: http://b1.download.windowsupdate.co...66F18800CFAC91EF0C329DF10F0299B4D.esd[/quote] You don't need an MSA for this, just a local account.

 

Thanks for the idea but the reason why I'm doing this is to test out the latest insider builds.

 

I installed 10120 in VBox a couple of days ago and activated it with the generic key. I then upgraded to 10240 RTM and is was fully activated with no expiry.

I then joined the insider preview and upgraded to 10525 and then 10528. After 10240 you get an expiry of June 15 next year.

My VBox also works fine when running on OSX host - not just a valid Windows 10 host (which I have). I've also tested Hyper-V and VMWare and all get activated OK if you upgrade from 10120 with no underlying OS.

Quite possibly they will get turned off at some point but for testing new builds it works fine. I'm sure another build will turn up before next June anyway.

 

Once you have upgraded to the activated RTM, you can set your preference to receive insider builds, fast or slow ring, and sign in with a MSA. Then you should be able to join in with the latest insider builds, starting with the upgrade to 10532. Otherwise you will need an activated win7 or 8 on your VM to upgrade from.

It would be best to take a snapshot of the RTM before joining insider, so you can go back to scratch if something inevitably fails.

 

I know that is the theory but it not what happens to me. If I make clean install of a new VM it is automatically activated. Because my underlying system is activated? Who knows.

 

As you say, who knows. Is it because that instance of a Virtualization host has already had an activated Win 10, and is therefore registered with Microsoft for Win 10 activation?
Perhaps windows 10 is not yet enforcing this:

- because users are, for the present, or perhaps for the month after installation, considered as "Insiders", or as running Windows 10 as trial software?