Windows install bypass the Edition selection when it finds that key in BIOS storage, the workaround for this is to edit one of the file on the install media which forces it to always ask. OTOH this stored BIOS license key can be a problem if you're trying to do a clean install of a DIFFERENT edition of Windows (like Pro while the machine came with Home). If it does have the stored key it goes up to 100%. So you might as well use the most well-known one, Magical Jelly Bean KeyFinder.Īnd in my experience Microsoft will 99 times out of 100 automatically detect and apply the correct key (as long as you select the right Windows Edition) even when doing clean installs on existing hardware even if you don't use a MS account for login and it doesn't have a BIOS stored license key. 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! The program is simple to use and is now completely stable.įor this early a version, version 1, the program shows real promise and I hope to see the dev continue to improve on the list of found serial numbers.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. While that may not seem like a large number you have to realize that there is no real standard for how a program stores and checks the serial. I looked at the list and it appears that a number of the possibles are the correct codes. It found 20 confirmed licenses and 92 possibles. The program itself does the job it claims to do. I know the dev put in a lot of time fixing a problem that was effecting a handful of users. I have to say it is rare these days to find this level of support. Today I received a new version to download which fixed the problem. And not all people running the program had the problem. ![]() Seems that I was a member of a select group of 5 people having this problem. ![]() ![]() The problem only occurred when scanning the plist file for my weather program, Seasonality. Over the course of a few emails he sent me debug versions and I sent back the reports. I found out it was a happening only when doing a deep scan, which is the default, and emailed the developer. When I installed it and ran it for the first time it crashed partway through the scan. I purchased the program on a recent promo as the price was right.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |