I cross-referenced this to make sure it works and found that it did match what was returned by ospp.vbs. Produkey will also do the same for Office and return the entire key, not just the last 5. The '/dstatus' switch will return the last 5 characters of an installed Office key, and the '/dstatusall' switch will return license info for all Office products found on the computer. If you're looking for a Microsoft Office install key, there's a script included with installed versions of office in the install folder called 'ospp.vbs', which does similar tasks for Office licensing as what slmgr.vbs does for the Windows OS.

Beware that Produkey will get flagged by Windows Defender and probably other AV software (definitely by Bitdefender as well) as a 'hacktool' and you likely won't be able to run it unless you have all anti-malware software disabled. I was able to cross-reference its result for Windows 10 key with that of slmgr to verify they return the same key, except Produkey shows you the whole installed key, not just the last 5 characters. I haven't tested that yet.ĮDIT: Nirsoft's Produkey also works correctly. It definitely works with retail Win 10 keys and maybe with returning original Win 7 keys used to upgrade to 10. I had come across this months ago and somehow didn't make the connection until just a few minutes ago that this method actually it will give you the correct retail key, or at least enough to cross-reference it with records of purchased keys. I just (re-)discovered that you can get the last 5 digits of the Windows product key using 'slmgr.vbs /dlv'. It appears that the key that shows up using the various tools to pull it from the registry is an entirely different key than what is used to activate the computer in the first place, which is throwing a monkeywrench in my documentation process.ĭoes anyone know if there's a way to pull the original key out of the system, and also which key I should use for transfer down the line? I wised up last year and started documenting it as I build, but I have a few that I did not do that for. Those keys I want to track and document for reuse. I build most of my workstations, and I started buying retail keys (digital downloads) a few years ago so I could transfer them to new computers as I upgrade over time. Most are Win 7 OEM keys upgraded to W10 and can't be reused, so those are easy because they all show the same generic key. I'm trying to document all our Windows 10 license keys, using a script I found here Get Windows Product Key - TechNet ScriptCenter Opens a new window (which is awesome, btw). I am doing documentation of various aspects of our systems, much of which I should have kept up on already.thus putting me in the position of having to ask this question.

Win 10 retail license