How to Find Your Original Windows 10 Product Key

taparb

TS Rookie
Hi,

I signed because I just want to say thank you... the suggested script works well for me (saved to "vbs")
again, thank you
 

allen80602

TS Rookie
So, here's the situation: I "won" a retired laptop (Dell E7450, originally delivered with Windows 8.1 Pro) from work. So, the ownership has changed from my company to me. So, I took it home and started it up. The laptop now has Windows 10 Pro installed but not activated. Was able to find the Windows UEFI/BIOS key using the above script (wmic path softwarelicensingservice get OA3xOriginalProductKey) - worked great! Thanks! Now, since I was curious, I clicked "Troubleshoot" in the activation screen and after a bit, it was activated- to my surprise. Now, I was able to determine what type of license it had: Volume KMS Client license. I'm not sure of the exact path of the activation, but my thinking is that it's not going to fly with my company that I activated on their volume license. The plan was to buy a retail (used) copy of Windows 8.1 and install it. Is that possible after using the slmgr uninstall commands above??
 

allen80602

TS Rookie
Thanks cliffordcooley for the response. Personal preference: I won't ever move to Windows 10 on my systems. My ultimate OS installs will be Linux running a retail version of Windows 8.1 Pro in a VM.
 

cliffordcooley

TS Redneck
I must have misunderstood then. It looked as if you tried to upgrade to Windows 10. And when you did, you noticed it was a volume license for your company.

If Windows 8.1 is all you want. Did the Notebook come preinstalled with 8.1? Or was 8.1 a volume license as well? If the Notebook had its own independent license you should be able to get that license activated again. If not you will need to find another license.

Does the Notebook have an OEM sticker on the bottom? Sometimes it will be located in the battery compartment.

If all else fails. You might can get a resolution by calling Dell Help Support.
 

p51d007

TS Evangelist
Thank you for the article.

"now manufacturers are storing this license within the machine's UEFI/BIOS and the information is automatically retrieved and applied when reinstalling the operating system. Certainly a better approach overall."

I strongly disagree. If the motherboard has to be replaced, you are screwed and have to buy yet another license (especially if you bought 3rd-party in replacing oem). Microsoft is really cashing in on this. No doubt in their plan. Finding the key like this is a big help.

I didn't. I was quite SURPRISED how easy it was. My lappy, under warranty had go back, and they replaced the motherboard. It came back, with windows home. I had paid for the upgrade.
With the machine still "fresh out of the box", nothing of mine was installed, went to the MS site, got online with a "chat agent", and after allowing him to remote in, I had pro back in about 20 minutes.
After disconnecting, I dumped the remote program, cleaned out the registry and checked to make sure there wasn't anything left. But, the chat agent even sent me an email with the key for this pro update that will work with my laptop, just in case I need to install it again.
 

rdpage1

TS Rookie
Do we have any information on how an OEM key can be recovered via the UEFI/BIOS on Windows Server 2016 or 2019? Are the Command Prompt or Powershell scripts the same?
 

Apogee777

TS Enthusiast
Product Key from Bios, use CMD or Powershell and copy/paste:
wmic path softwarelicensingservice get OA3xOriginalProductKey
 

captaincranky

TechSpot Addict
I just keep the original Windows boxes, with the product key still on them. Each box and disc, are keyed to the machines on which they are installed.

Have I been going about this all wrong? :rolleyes:

Oh wait, I don't have anything later than Windows 7. My bad.

Is the Win 10 download still burnable as an ISO file? If so, not my bad.

This tool "SIW" (once free, now unfortunately only free to try), used to easily pickup the Windows license key. https://www.techspot.com/downloads/155-siw-system-info.html
 
Last edited:

jasonbrown1965

TS Rookie
I'm missing some critical info....
Me too, like what are you actually asking?

And what did you use to check that there was no product key?

Seems unlikely. Unless someone installed some kind of spyware blocker, but even then MS has myriad ways of checking authentication. Be interesting to know more details.
 

Bullwinkle M

TS Maniac
Me too, like what are you actually asking?

And what did you use to check that there was no product key?

Seems unlikely. Unless someone installed some kind of spyware blocker, but even then MS has myriad ways of checking authentication. Be interesting to know more details.
I was asking why anybody in their right mind would pay to activate a Spyware Platform

If you really want spyware and malware, Windows 10 works without activation
 

WindowPain

TS Rookie
None of the methods described in the section titled "Find your key from inside Windows" work for my Windows 10 installation. They all yield the result: BBBBB-BBBBB-BBBBB-BBBBB-BBBBB!
This whole activation paradigm is as clear as mud and this article does nothing to clear it up.
 

jobeard

TS Ambassador
Hmm; Sorry to hear that, but it works well on Win/7. If your failure is on Win/10 ... you can thank Microsoft.
 

cliffordcooley

TS Redneck
None of the methods described in the section titled "Find your key from inside Windows" work for my Windows 10 installation. They all yield the result: BBBBB-BBBBB-BBBBB-BBBBB-BBBBB!
This whole activation paradigm is as clear as mud and this article does nothing to clear it up.
HaHaHa! Another fail! That software is not as magical as you think. And, BTW, I detest SW vendors who bait you as those guys do.
If you are having issues extracting the Activation Key with ALL the above mentioned methods. I would question the validity of your installed operating system.
 

jobeard

TS Ambassador
If you are having issues extracting the Activation Key with ALL the above mentioned methods. I would question the validity of your installed operating system.
I was thinking the same thing -- are the Microsoft.NET Framework NGEN services installed and enabled? You need v4.0.30319