ShowKeyPlus

  1.    #1101

    What do you mean SKP is reaching EOL, it hasn't been on the store for long.
      My ComputersSystem Spec

  2.    #1102

    Superfly said: View Post

    Oh BTW Happy belated birthday ..
    Thanks a lot Craig All the best to you and your loved ones mate!
      My ComputerSystem Spec

  3.    #1103

    Bree said: View Post
    I have some more feedback, though this seems to apply to just one machine.
    .
    Dunno bud, I'll see if I can replicate... what's with our Bucket ID?
      My ComputerSystem Spec

  4. Bree's Avatar
    Posts : 12,022
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #1104

    Superfly said: View Post
    Dunno bud, I'll see if I can replicate...
    Don't put too much effort into this, it seems to be a weird 'one-off' due to the convoluted history of this machine, most likely down to the emergency HDD to SSD swap.

    I have now used Macrium viBoot to run as VMs both the image I made from the failing HDD in order to migrate to the SSD and an image from a week ago before the HDD started to die. In both v1.1.11.0 installs and runs normally. Restored that latest image and it doesn't work on the real machine. I'll try the earlier image next.... Edit: no, that has the same problem. Next I'll try its 1809 image and upgrade to 1903 again...

    ...what's with our Bucket ID?
    Dunno, I'm just the messenger. Reliability history says the fault was reported....

    A fault bucket identification number is a number assigned by the system to identify specific types of errors, usually based on a specific application...The ID is what is sent to Microsoft when you send an error report.
    https://social.technet.microsoft.com...m=winserverNIS



    2nd Edit: the mystery deepens, any of this machine's 1809 images that I restore exhibit the same problem: both v1.1.11.0 and the v1.0.0.32639 preview now crash unless they are run as administrator, even though the preview ran correctly on this same 1809 image previously.

    I can eliminate the windows update to 1903 as the cause of this problem, as another x64 machine that was upgraded to 1903 exactly the same way is happy to run both v1.1.11.0 and v1.0.0.32639 normally. It can't be because I once had the old store app installed, then uninstalled it, as I also did that on the other working machine.

    That only leaves this machine's migration from HDD to SSD as the cause. I note that when I installed v1.1.11.0 on the other machine the progress bar said (briefly) towards the end of the install: 'restoring data'. I can only assume there's some lingering record of the original HDD somewhere that's causing a conflict(?).
    Last edited by Bree; 04 Jul 2019 at 09:45. Reason: further tests...
      My ComputersSystem Spec

  5. Cliff S's Avatar
    Posts : 22,423
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       #1105

    It updated today.
    Ooooooooh! Really nice animation Mr. J!
      My ComputersSystem Spec

  6.    #1106

    Cliff S said: View Post
    It updated today.
    Ooooooooh! Really nice animation Mr. J!
    OoooH indeed , blatantly ignoring the Accent gradient which is a direct descendant from SMACC which in turn is a direct descendant from you... Shame on you!
      My ComputerSystem Spec


  7. Cliff S's Avatar
    Posts : 22,423
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       #1107

    Superfly said: View Post
    OoooH indeed , blatantly ignoring the Accent gradient which is a direct descendant from SMACC which in turn is a direct descendant from you... Shame on you!

    Ummmm??? It could be, because, I'm just so used to it looking good now?
      My ComputersSystem Spec

  8. DooGie's Avatar
    Posts : 6,421
    Wndows 10 x64 Pro version19H2 18362.10015
       #1108

    This latest version looks good and up to now is working fine. I've not had time to try breaking it yet though
      My ComputerSystem Spec


  9. Posts : 2
    Windows 10 Pro x64
       #1109

    Superfly said: View Post
    Find your Windows product key with ShowKeyPlus.Applies to Windows 7, 8 and 10
    • If you purchased 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 purchased a new PC running Windows, the product key will be included in the firmware in the case of Windows 8 or 10 - or as an OEM marker, in the case of Windows Vista or Windows 7


    • Apart from the key, the associated Edition of each key is displayed below it.

    Attachment 36642
    • 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.
    Attachment 36643
    • In order to verify the edition your key is associated with, use the Check product key link to confirm.
    Attachment 72297
    • Hint: Click/tap ‘Version’ link to toggle between light and dark modes. NB Dark mode will not be saved as it supports Windows high contrast - it will adjust to the underlying system scheme if so selected ( Thanx Cliff S )

    Attachment 36645

    Download: ShowKeyPlus


    Attachment 230584 Attachment 142094

    ShowKeyPlus Awards
    Attachment 142095

    Note   Note
    The current version includes a routine that checks GitHub for newer versions. Some Anti-Malware applications may flag it as PUP. It's a false positive.AV's that have not white-listed it, may require that you create an exception in their settings.
    Virustotal results


    Code:
    Version history:
    
    Version 1.0.7060     
    Bugfixes: 
    
    • CLI mode support in WinPE
    • Windows 7 hive accessibility
    What's new:
    • The standard help switch in CLI mode (-h, /? etc)
    • Uses offreg.dll's (consistent with UWP version)
    • Saving key info from GUI
      • in WinPE saves directly to executable path
      • else expanded to include Word and Excel file types
    Version 1.0.6893 New features:
    • Added key checking support for new editions in October 2018 update
    • Over-ride the MAK key removal display ("BBBBB-BBBBB-BBBBB-BBBBB-BBBBB") with explanatory text.
    • 32-bit and 64-bit now have the same versioning with the architecture displayed with version build.
    Version 1.0.6594 Bug fix:
    • Windows 8 and Windows 10 key checking on Windows 7 32-bit installations.
    New features:
    • Added Windows build version and architecture per installation.
    Version 1.0.6477 Bug fix:
    • Added key checking support for new edition in Fall Creators Update: Windows 10 Professional Workstation
    Version 1.0.6371 Bug fix:
    • Background opacity on message-box pop-up
    Version 1.0.6320 Bug fix:
    • Suppress messagebox when in CLI mode
    New in this release:
    • Added key checking support for new editions in Creators Update: Windows EnterpriseG and Windows Cloud
    Version 1.0.6125 Bugfix:
    • 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 Windows 8 nor Windows 10 keys. It will report those keys as Invalid, but they should be checked on Win 7 64-bit or any Windows 8 or Windows 10 version.
    New in this release:
    • Exception wording added for valid keys with invalid configuration resulting in a null response for edition.
    • Cosmetic fixes.
    Version 1.0.6084 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.
    Usage:
    "[path]\ShowKeyPlus.exe" "[path][filename].txt" (or any text compatible extension, eg: .doc, .csv etc)
    • Implemented Accent colour as the base scheme.
    • Background changes to opaque when pop-up visible.
    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.
    New in this release:
    • Additional DPI scaling compatibility.
    Version 1.0.5815 Bug-fix:
    • Forward-navigation arrow displaying incorrectly.
    • Check version dialog was not returning to calling thread.
    • Windows 8 reporting duplicate installations.
    Update 01-Dec-2015: Version 1.0.5812 New in this release:
    • Automated discovery of pre-existing Windows installations (from Windows and Windows.old folders)
    • Last used theme gets saved for use the next time the application is launched.
    • Some GUI enhancements for DPI scaling.
    • Included a version check to alert of new releases
    Version 1.0.5730 New in this release:
    • Improved threading and exception handling modifications.
    • Changed to a modern user interface.
    Update 30-June-2015: Included non-native support for Window 8 and Windows 7 key checking (as the former has been removed from Windows 10.) NB: Windows 7 key checking is slow due to it having quite an extensive range. Update 08-June-2015:Bug fix - Windows Vista/7 marker was returned from the MSDM rather than SLIC table. Update 07-June-2015:Added Windows 7 support. SLIC and edition. Update 19-May-2015:Minor bug-fixesGUI improvements. Update 16-Apr-2015:Added Product key checker Update 15-Apr-2015:Added ability to retrieve key from backed-up windows image. This requires redirection to the offline \Windows\System32\config\SOFTWARE hive - it has no file extension. Update 17-Mar-2015:Added OEM edition retrieval.Original key and edition only appears after an upgrade (eg. Pro to WMC)
    **************************************************************************************************** ************
    Key types:
    OEM: DM = PC specific keys found embedded in the Microsoft Data Management (MSDM) table of the firmware of Windows 8 and Windows 10 factory installed PC's.
    OEM: SLP = System Locked Pre-installation key - Win Vista/7 manufacturer specific keys used to mass activate those installations. Activation is off-line with a SLIC table in the firmware and matching Certificate installed together with the key.
    OEM: COA = Certficate of Authenticity key found as a sticker attached to PC's factory installed with the above
    OEM:SLP method as a backup for on-line re-activation.
    OEM: NONSLP = Non-System Locked Pre-installation key a.k.a System Builder keys - available from re-sellers and acts as retail on-line activation keys but with an OEM EULA.
    Retail = Full Packaged Product (FPP) keys, available from a retail merchant or Microsoft on-line (NB: Windows 10 purchases from Microsoft Store are digital entitlement licences and use a generic key for installation.)
    Volume: MAK = Multiple Activation Key is a single key used to on-line activate a pre-determined number of Windows installations.
    Volume: GVLK = Group Volume License Key, is a generic key for editions of volume licence versions that activate off-line via a KMS server.
    WAU = Windows Anytime Upgrade - Retail key that comes at a reduced price to be used to upgrade an activated previous version of Windows. **************************************************************************************************** ***************
    Note   Note
    Should your key display as BBBBB-BBBBB-BBBBB-BBBBB-BBBBB, it is a placeholder Windows inserts after activating a MAK key. The reason being, these keys can have thousands of activations (for which companies pay huge amounts) and should someone steal one, they could sell that same key to thousands and each will activate as if part of a company network - it's thus a security feature specific to MAK's.

    **************************************************************************************************** ****************
    PS: Please see here regarding unblocking the .exe
    Hi
    i need help with finding my product key
    I have a HP DV7 and a HP DV6
    both came with windows 7
    i upgraded to windows 10 pro
    the HP DV7 is activated with windows keys digital license.
    i used ShowKeyPlus to check for the key and it shows a different key from the sticker on the back of the laptop.
    i Upgraded the HP DV6 laptop with the same windows setup to windows 10 pro. and its not activated.
    and the sticker at the back of the laptop is not clear.
    i used ShowKeyPlus to check for the key and it shows a different key from the sticker on the back of the laptop and its the same key comes up as in the HP DV7.
    Even others have got the same key its on the web.
    Windows10 Pro VK7JG-NPHTM-C97JM-9MPGT-3V66T

    if the original Key is saved in the firmware how can i get it.
      My ComputerSystem Spec

  10.    #1110

    Mine is the same, it just means that it has been merged with your Microsoft account or your PC's hardware into a digital license.
      My ComputersSystem Spec


 

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:05.
Find Us