Update to Version 1.0.6084
Version check returning null error
System.NullReferenceException: Object reference not set to an instance of an object.
at ShowKey.frmKeyInfo.bgwVersion_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
Product key checking referencing incorrect dll. on Windows 32-bit versions
NB: Windows 7 32-bit still does not support key checking of Win 8 / Win 10 keys. It will report those keys as Invalid, but they should be checked on Win 7 64-bit or any Win 8 or Win 10 version.
(Seems to be kernel calls to the superceded pidgen.dll that fails. Works with Win 8 and Win 10 32-bit, however.)
Exception wording added for valid keys with invalid configuration resulting in a null response for edition.
Update to Version 1.0.5835.
New in this release:
Retrieve Windows 8 and Windows 10 key editions on Windows 7 installations.
Use CLI to generate a text file of installed, original and OEM key(s) and their editions, silently.
"[path]ShowKeyPlus.exe" "[path][filename].txt" (or any text compatible extension, eg: .doc, .csv etc)
Implemented Accent colour as the base colour scheme.
Background changes to opaque when pop-up visible.
Find your Windows product key with ShowKeyPlus.
Applies to Windows 7, 8 and 10
Your product key depends on the type of Windows version you bought:
• If you bought Windows from an authorized retailer, the product key will only show as the Installed key. This applies to OEM System Builder keys as well.
• If you upgraded Windows, the Original key will be the key installed prior to the upgrade. NB if you upgrade to Windows 10 for free, you'll receive a unique ‘digital entitlement’ instead of a product key. The key displayed will be a generic key in that case.
• If you bought a new PC running Windows, the product key will be pre–installed on your PC and the key will be included in the firmware in the case of Windows 8 or 10 - or as an OEM marker, in the case of previous versions. The OEM key will display the key in the case of the former, or whether your PC was built for Windows Vista or Windows 7.
• Apart from the key, the associated Edition of each key is displayed below it.
• Should you have a backup which includes a Windows folder, the key from that installation (as well as the previously installed key, if that installation was an upgrade), can be retrieved using the Retrieve key from backup link.
In order to verify the edition your key is associated with, use the Check product key link to confirm the edition to which that key is associated.
Update to Version 1.0.5730.
Automated discovery of pre-existing Windows installations (from Windows and Windows.old folders) that are in their default locations (root drives). It supports Windows XP through Windows 10 key retrieval. The forward-arrow located upper right navigates to each of those.
NB: Should the Windows installation not be in the default location, "Retrieve key from backup" should still be used.
Last used theme (Dark mode can be set by clicking "version") gets saved for use the next time the application is launched.
Some GUI enhancements for DPI scaling.
Includes a version check to alert of new releases.
Update to Version: 1.0.5812
Bug-fix: Forward-navigation arrow displaying incorrectly.
Bug-fix: Check version dialog was not returning to calling thread.
Update to Version: 1.0.5814.
Bug-fix: Windows 8 reporting duplicate installations.
Update to Version 1.0.5815.
New in this release:
Bug fix: In WinPESE, automated discovery would crash if no existing Windows installations (from Windows and Windows.old folders) found. Option included to re-direct to "Retrieve key from backup" instead for a user initiated search.
OEM description was not displaying for the associated key.
Bug fix: Some motherboards (eg. Gigabyte) have a pre-installed MSDM table in the firmware without an OEM key embedded. Exception caught if key not present.
Additional DPI scaling compatibilty.