Microsoft's Windows Media Creation tool only fo retail keys?

[BarkingGhostar]

So, I d/l the media creation tool from Microsoft's website and ran it. I selected the Windows 8.1 version, 64-bit that was installed on my HP Stream Mini. I have what I thought was the M$ Windows 8.1 product key on a small piece of literature, but I now think that is for the OneDrive product that came pre-installed.

No other documentation in the HP packaging has a M$ product key. I can only conclude either the M$ Media Creation tool disallows OEM keys, the key that I am using isn't for Windows, and maybe HP doesn't key such information to customers buying their product.

Anyone else have a clue since I do not? BTW, the ISO does not allow you to move forward with installation without successfully entering a product key. I guess this is how HP bends customers of the sofa for not willing to spend another $45 for HP recovery s/w.

 

[zokudu]

The key is in the UEFI.

https://github.com/christian-korneck/get_win8key

 

[BarkingGhostar]

Well, I actually installed BeLarc, which produced the key, but M$ is complaining the key provided does not match the Windows image being used. Is the tool I am using only for retail (not OEM)? Let me go try that get_win8key ...

 

[BarkingGhostar]

That tool produced the exact same key information. Still, no dice using it to load Win8.1 into a VM.

 

[Elixer]

Use the generic install key I told you about before...

 

[Mushkins]

As Elixer said, you have to use the generic install key. OEM copies of Windows 8/8.1 do not provide the end user with the software key or ask them to input the key, it is stored directly in the BIOS.

The generic key will install the OS, and when it goes to activate it will pull the actual OEM key from the BIOS automatically.

 

[BarkingGhostar]

Use the generic install key I told you about before...

Thanks for the reminder. It worked.

 

[VirtualLarry]

Hmm, I used the Windows 8.1 refresh media (pre-jan) for 8.1 x64, on a Lenovo IB i3 that originally shipped with Windows 8 64-bit pre-installed.

It booted and installed and activated fine, I never had to enter a product key.

 

[BarkingGhostar]

I wonder if when running the MCT if it uses the platform MCT is running on becomes the assumed target for the activity. I wonder because I ran MCT on the HP Stream Mini, which has the product key embedded in the BIOS, and as such it was expecting something else. The funny thing is that I wanted the ISO to test first in a VM, but not on the HP and rather on my i7 PC.

But I still find it strange. Is the version of Windows 8.1 that I have preinstalled on the HP Stream Mini meant only for system builders like HP/Dell, who are embedding keys in the BIOS? How are folks that build their own PCs and buying OEM versions of 8.1 doing this?

I guess this is all about my ignorance, once again.

 

[Dahak]

For the Win8 MCT, I was able to download the iso and use it on a HP laptop and it installed and activated fine.

and I did test it with another machine that did not have the key embedded and then it asked for the key

The only thing I did not try is creating the media from a machine that has the embedded key, the media I created where always from my custom built win8.1 machine

 

[BarkingGhostar]

Well now this is strange ... while using a generic key worked when testing in a VM (inside VirtualBox on LM17), it did not work natively with an erased Samsung SSD plugged into my i7 PC. I used Media creation Tool to prepare a USB flash drive, which booted fine, started the initial process, but at the time for key entry it wouldn't take anything I threw at it. I even tried the same key I successfully used in the VM test.

BTW, even the M$ technet website does not list a generic key for the Win8.1wBing. Only the Professional, Enterprise and non-multimedia versions. I guess the intent was generic versions only come on preinstalled systems and as such always have an embedded version. My only thoughts on the VM working is that the installer used the ISO file and not the USB drive.

Hmm, letting that thought come to the surface makes me want to go burn the ISO and give it a try ... brb

 

[Elixer]

Wait, where did you get the win 8.1+bing ISO from? Why don't you just get the win 8.1 pro (aka, the Windows 8.1 refresh media) from MS from that other link I gave in the other thread?
Then, when it pulls the OEM key from BIOS, it will set it to the correct version for your laptop.

 

[ArisVer]

It booted and installed and activated fine, I never had to enter a product key.

Did the same thing a week ago using the media creation tool. HP650 notebook.

 

[BarkingGhostar]

I guess I am confused. I got the vanilla Win8.1 (w/Bing) ISO from selecting it in the Media Creation Tool. I did not select the Pro version, because once it does try to activate it will not find what is needed from the embedded BIOS product key, which is the non-Pro version.

I'm now wondering what key I used in the first VM installed, because I tried to repeat my VM experiment using the keys on hand and they all failed, too. When I start the Win8.1 VM that got installed, it does say it is a version other than the vanilla version (not Pro/Enterprise).

Again, all the confusion. I do not want to go through all the testing using a Pro version only to implement on the HP Stream Mini as a fresh install only to have a failed activation attempt a week later leaving the system debilitated.

Has anyone witnessed a case of an unactivated Pro install resulting in use of an enbedded product key converting the operating system to a non-Pro state?

 

[BarkingGhostar]

I tried this and it seems to have worked. Doesn't suggest it would not work for any specific version of the Windows 8.1 tree of editions so I created the file and added it to the sources folder of the USB flash drive and I never got prompted for a key.