Windows 10: Can't activate clean install of latest Insider Preview under Orcale VB


  1. Posts : 4,999
    Windows 10 Pro X64 15063.138
       02 Oct 2016 #1

    Can't activate clean install of latest Insider Preview under Orcale VB


    The Windows 10 Insider Preview I had was at 14393 Anniversary level. It got hosed so I decided to do a clean install of the latest 14396 version. Installed fine but won't activate. Says previous installed OS was not activated.

    This is a clean install to a newly defined Oracle VirtualBox VM.

    Any way to get this activated now?
      My ComputersSystem Spec


  2. Posts : 8,169
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       02 Oct 2016 #2

    I have the same issue with 2 in VMWare. Nothing to base this on, but in VMs there really is no hardware profile. Everything is virtualized. I haven't called MS yet. You can try to click on the 'Troubleshoot' option and then click on I changed the hardware. It should take you to your MS account and if the VM is listed there sometimes you can select it and activate.
      My ComputersSystem Spec

  3.    03 Oct 2016 #3

    I have clean installed 1607 in VBox, VMware and Hyper-V and it activated fine in all cases. How did you do it? You need to use the same Virtual machine and just create a new disk or wipe the existing disk the same as you would on a real PC. If you make a new VM it will not activate Windows will see new hardware. If you have done this you should be able to update the new VM with old UUID if you have a backup.

    essenbe said: View Post
    I have the same issue with 2 in VMWare. Nothing to base this on, but in VMs there really is no hardware profile.
    Actually there is...

    In virtualbox it is in <VM name>.vbox xml style file, right at the top, called MachineUUID:

    Code:
    <?xml version="1.0"?>
    <!--
    ** DO NOT EDIT THIS FILE.
    ** If you make changes to this file while any VirtualBox related application
    ** is running, your changes will be overwritten later, without taking effect.
    ** Use VBoxManage or the VirtualBox Manager GUI to make changes.
    -->
    <VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.15-windows">
      <Machine uuid="{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" name="Windows" OSType="Windows10_64" snapshotFolder="Snapshots" lastStateChange="2015-09-02T17:04:02Z">
        <MediaRegistry>
          <HardDisks>
    In VMWare it is in a (text not xml) file called <VM Name>.vmx. The machine UUID is based on one or both of these (I'm not sure which so I copy both).
    Code:
    uuid.bios = "xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx"
    uuid.location = "xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx"
    In Hyper-V it is stored in in a more obscure manner

    In all cases it is easier to just move/copy the whole directories (in the case of hyper-v export and import) but with VBox and VMware you can make a new VM, copy the UUID from a backup of a existing activated VM and it will activate. It may not activate on different hardware as the CPU name is passed through direct to the VM. This would be the same as changing you CPU on real hardware.

    It is worth noting no hypervisor will allow you to have duplicate machines with the same UUID. While you could probably run the same machine on two separate hosts at the same time this would be in violation of EULA and your key might get blocked.
      My ComputerSystem Spec


  4. Posts : 8,169
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       03 Oct 2016 #4

    Thanks, that's good info. Very much appreciated.
      My ComputersSystem Spec


  5. Posts : 21,809
    Dual boot - Win 10 Pro & Win 10 Insider (and a sprinkling of VMs)
       04 Oct 2016 #5

    This may have no bearing, but in 14926 there was an Oracle VB known issue.

    From Feedback:

    Oracle VM VirtualBox will crash on launch after upgrading to this build.

    I can't find in any feedback release notes for 14931 or 14936 where the issue was addressed or fixed.

    Again, may have nothing to do with this, but it's coincidental. Maybe a lingering bug.
      My ComputersSystem Spec

  6.    04 Oct 2016 #6

    The key is in the migration of the virtual machine. As long as it does not require conversion between file formats (say, .vdhx to .vdh, etc.) there is no change in the virtual hardware and activation should hold. However, once the virtual mobo changes reactivation requires a new license. A hardware "profile" is no longer used. It is the unique identifiers of the hardware, such as the mobo serial number, etc. that is used at the time the device (virtual or physical) is registered as a Windows 10 device on Microsoft's servers.
      My ComputerSystem Spec


  7. Posts : 4,999
    Windows 10 Pro X64 15063.138
    Thread Starter
       06 Oct 2016 #7

    I deleted everything and started from scratch. I also changed the name and I think (not sure) I switched from 64 to 32 bit.
    Self inflicted wound I suspect.

    Essenbe, I tried the changed hardware route but nothing was shown that I could slick on to activate.

    Can you use a Win 7 or 8 key to activate a IP build?
      My ComputersSystem Spec

  8.    06 Oct 2016 #8

    Ztruker said: View Post
    I deleted everything and started from scratch. I also changed the name and I think (not sure) I switched from 64 to 32 bit.
    Self inflicted wound I suspect.

    Essenbe, I tried the changed hardware route but nothing was shown that I could slick on to activate.

    Can you use a Win 7 or 8 key to activate a IP build?
    The same license is for either 32bit or 64bit so changing bitness doesn't matter. You cannot use a Win 7 or 8 key now to confirm a Windows 10 license. That ended on July 29th. Please understand that no part of activation is based in the software with Windows 10. The issue is the virtual motherboard. Windows 10 activates and activation is maintained by the licensing software by contacting Microsoft's servers with the hardware identifiers (such as serial numbers) and the servers responding with confirmation that the device is a registered Windows 10 device. When you switch virtualization providers the hardware identifiers change because each provider uses its own virtualized hardware (the virtual machine manager provides this at the time you create the vm) with its own set of hardware identifiers so Microsoft's servers can no longer find a registration file that matches your VM and the licensing software deactivates Windows. The way to reactivate is to enter an available product key.
      My ComputerSystem Spec


  9. Posts : 4,999
    Windows 10 Pro X64 15063.138
    Thread Starter
       06 Oct 2016 #9

    I'll see if I can scrounge up another key then.

    Thanks all
      My ComputersSystem Spec


 

Related Threads
Solved Clean install Windows 10 says insider preview in Windows Updates and Activation
Admin please delete this post
I am now running Win 10 build 11099.rs1_release.160109-1156 I am having a few problems with "Sleep" (takes 30 seconds before icons are usable) and "Windows Store" downloads don't always work. ie ABC NEWS (installs but won't open. I have been an...
If I understood this : 37447 clearly, then does it mean that Windows will activate itself from some Windows activation servers that are somehow written into my hardware even if I do a clean install deleting everything in my Windows partition? ...
clean install *HOW TO ACTIVATE in Windows Updates and Activation
Hello. I have just completed a clean install of windows 10 (the upgrade from windows 7 failed 5 times) and I cant work out how to activate my copy. I reserved my copy on windows 7 but it is now asking for a serial key? This is my main PC and I...
Am currently using Windows 10 Insider Preview. Build 10074 shows on right side of screen. Have updated Windows through settings. Am I using the latest build?
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:44.
Find Us