ShowKeyPlus


  1. Posts : 11,062
    Windows 10 Pro version 22H2 0n one desktop and running Window 11 Pro 22H2 on unsupported desktop
       #531

    Hmmmm... the only time it will not display is if an aborted instance is still running in memory - it uses Mutex - but that is just by the way - it should launch from a fresh startup

    (I'm saving up to give you a visit down-under to sort this out...)
    Ok mate I will delete all downloads and try again but hey it sin't earth shattering stuff and I do appreciate the help.

    Oh the visit you won't be disappointed
      My Computer


  2. Posts : 3,453
    Thread Starter
       #532

    ICIT2LOL said:
    Ok mate I will delete all downloads and try again but hey it sin't earth shattering stuff and I do appreciate the help.

    Oh the visit you won't be disappointed
    LOL... OK buddy... Keep the beer on ice!
      My Computer


  3. Posts : 11,062
    Windows 10 Pro version 22H2 0n one desktop and running Window 11 Pro 22H2 on unsupported desktop
       #533

    LOL... OK buddy... Keep the beer on ice!
    Is there any other way LOL!!
      My Computer


  4. Posts : 15,426
    Windows10
       #534

    ICIT2LOL said:
    LOL... OK buddy... Keep the beer on ice!


    Is there any other way LOL!!
    From CAMRA - "Cask conditioned beer must be stored in a temperature controlled cellar at between 11°C and 13°C (52-55°F), ideally at 12°C (54°F)."

    Of course if you mean that fizzy chemical colourless stuff.......
      My Computer


  5. Posts : 27,157
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #535

    cereberus said:
    From CAMRA - "Cask conditioned beer must be stored in a temperature controlled cellar at between 11°C and 13°C (52-55°F), ideally at 12°C (54°F)."

    Of course if you mean that fizzy chemical colourless stuff.......
    Here in Germany in the summer we just go to a Bier Kellar:)
      My Computers


  6. Posts : 1,983
    Windows 10 x86 14383 Insider Pro and Core 10240
       #536

    Just released Windows developer virtual machines September 2016 build - Windows 10 Forums

    Just got this running as a native boot VHD, so I was curious about the key it used since slmgr looked like this:
    ShowKeyPlus-2016_10_03_18_12_411.png

    I ran ShowKeyPlus, and got this error each time, and now, the fifth time, when I wanted a screenshot - no error!!!, but this was the text I saved from the error dialog:

    Code:
    See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
    
    
    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
       at ShowKey.frmKeyInfo.bgwVersion_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
    
    
    
    
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    ----------------------------------------
    ShowKeyPlus
        Assembly Version: 1.0.6084.20018
        Win32 Version: 1.0.6084.20018
        CodeBase: file:///C:/Users/MSUSER/Downloads/ShowKeyPlus/ShowKeyPlus.exe
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1586.0 built by: NETFXREL2
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    
    
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    
    
    For example:
    
    
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    
    
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    A thought is that the CU Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194496), may have fixed the error??!
    Beyond that, Showkey produced a result as expected:
    ShowKeyPlus-2016_10_03_18_20_491.png
      My Computers


  7. Posts : 3,453
    Thread Starter
       #537

    Thanx Faf,

    I managed to replicate it and made some changes - reverted to the old (version 5835) way in fact.

    Posted an update for testing. Releases · Superfly-Inc/ShowKeyPlus · GitHub
      My Computer


  8. Posts : 14
    Windows 10
       #538

    Superfly said:
    Technically, that should not be happening... why it affects that thread execution is a mystery TBH, that method has a catch-all exception and should just continue execution...
    I have found that error occurs randomly on my testing at runtime.. cannot replicate it in IDE tho' - so can't debug ... really weird?
    Can't you create a really verbose version that logs everything for debugging purposes? That way you can run it till it crashes at random, and hopefully the log should help you track down what exception condition you've missed.

    Edit: I see now you've posted a new version. Will give that a go and report back.

    Bugfix:
    System.NullReferenceException: Object reference not set to an instance of an object.
    at ShowKey.frmKeyInfo.bgwVersion_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
    It can be replicated in builds 6112/6115 by attempting launching a second instance immediately as the first one is initialising (i.e before the background worker completes)
    Just for the record, I never launched multiple instances of the program and it still crashed during the update check. Is this exception you've fixed different and the update-related one is still present?
      My Computer


  9. Posts : 13,847
    Win10 Version 22H2 Pro and Home, Win11 Pro and Home
       #539

    cereberus said:
    Hi C,

    Here is an odd one - I am running 10 pro Insider in hyper-v unactivated. and I wanted to get the generic key (to tell somebody how to upgrade to pro without reinstalling), and got the following. The host OS is Windows Pro N, although PC was originally 8 Core (normal) with a bios embedded 8 key.

    I was surprised to see the Vista message.

    Rgds

    M.

    Attachment 103686
    A late posting but I have a Dell Inspiron 530S that has the Vista COA sticker with Product Key that I first Upgraded to Win7 Pro then put it in the Technical Preview program [now is the Insider Preview] that displays that same message in ShowKey.
      My Computers


  10. Posts : 11,062
    Windows 10 Pro version 22H2 0n one desktop and running Window 11 Pro 22H2 on unsupported desktop
       #540

    Superfly said:
    Thanx Faf,

    I managed to replicate it and made some changes - reverted to the old (version 5835) way in fact.

    Posted an update for testing. Releases · Superfly-Inc/ShowKeyPlus · GitHub
    Spot on Craig on my main machine - desktop and so quick really impressed with the work you have put into this
    John
      My Computer


 

  Related Discussions
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 21:16.
Find Us




Windows 10 Forums