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.
0 kommentar(er)
