So really, only the first method should ever be used, there are other programs and tools that will work but there's no reliable methods that doesn't use tools!
If there's no Windows OEM key in the BIOS it will be empty and if you've reinstalled using a different key it will give you the wrong key! It is useful as a way to access the key that comes with the hardware on most newer OEM machines but is no substitute for actually checking what license key Windows actually use.Īnd the third method usually? sometimes? returns a "digital key" that's only valid for the specific install - there's no real use for this since it can't be used even on the same hardware after a reinstall! One other thing I would try, I sometime use a small dos program called runasTI (run as trusted installer), with which you can run a program as "trusted installer", very usefull, that saves me from changing security options in the registry adding administrators etc.The OA3xOriginalProductKey method returns the Windows OEM license key stored in the BIOS for pre-installed machines where they used that method to store it - most OEMs do this because this is the only way where they DON'T need to physically affix a sticker with the key on the machine which saves them time. This is the just the "run as administrator" icon I think, which is normal on a keygen. "Windows RS2 10 Build 1703-15063 Fast Ring" looks like INSIDER version no? maybe also try an "in place upgrade" with a regular version. Or maybe try booting and running the keygen in safe mode, if possible. Otherwise I would try to disable defender in local group policy (gpedit.msc), to make sure the service is not running. cmd might not have fully worked due to security settings/permissions on your host file. Maybe it's the recent R2R host thingy that prevent you from running it if it doesn't detect added addresses in your hosts file, R2R.
0 kommentar(er)
