Registered just for this, unfortunately while it generates an OEM ID, it doesn't generate the OEMID used by Metro. ie: it outputs ARCSYS on an Acer laptop but Metro uses A009 as the OEMID (discovered this by printing out args.bi details in the WinStore.js file)
Just to be clear for me. Newbie at this sorry. If I want to extract the key from my new desktop HP bios running 8. I run the tool and click on the MSDM key box correct? Which key though do I actually use for the clean install of 8.1 activation wise? The one that first comes up? Or the one by checking the box? P.S. Would this tool still work at extracting the bios key with 8.1 as well?
MSDM = Your manufacter Retail key. So you just need to reinstall the OS (needs to be the same version) and use this key.
I think my new machine is coming with 8. I would say 99% sure. I have the leaked iso of 8.1 along with generic 8.1 key to allow the install. Activation wise. That is when I would put in the key from the MSDM result right? Sorry if going around in circles.
Provided you use the correct SKU (Core, CoreSL, CoreCS or Pro), the OEMM key should work for activation.
I asked a fellow HP owner about the sku. Same model as mine practically. They said the sku was Windows Standard Core. So, guess I am good to go as I have the leaked 8.1 iso. When you say it should work. Has anyone had trouble with this regarding 8.1?
With the Product Key Viewer it is not possible to view the VLK of MAK of Windows 8.1 Enterprise. Will this be added to the application, or has some other utility been developed for this purpose?
Till now it might be the "normal way", but I am interested to know if there are plans to develop a tool with which it IS possible to reveal the key in stead of "BBBBB-BBBBB-..."!
I have used the key viewer from this thread and RW Everything. Both programs show the same key. I decided to check the key by trying to download the Windows 8.1 ISO from MSFT and they request you input your valid Product Key to continue. When I put the key in that was shown by RW and the Product Key viewer on this thread, MSFT says it is invalid. I'm not sure why it would be invalid unless there is something I'm missing.