none
Win7 Ultimate 32bit lost activation RRS feed

  • Question

  • Windows 7 Ultimate 32bit
    running in a Virtualbox VM
    has been installed, activated and running there for >10 years
    original MS full retail license bought from Amazon (if I remember correctly), which was an official MS retailer back then

    The OS was last updated 2019/12/30.
    Rebooted today and the OS reported to be not activated.
    Online activation and phone activation with the genuine key failed. The key is reported to be blocked.

    Anybody have an idea what the problem is?
    I guess it is not really the license, but some other problem.

    Monday, March 30, 2020 3:44 PM

Answers

  • The problem is you have a stolen OEM SLP product key that originally belonged to a computer manufacturer.  It will not activate anymore since it was discovered to be stolen.

    Carey Frisch

    Thursday, April 16, 2020 6:24 AM
    Moderator

All replies

  • And the same issue with a
    Windows Vista Ultimate 32bit

    Note that I also have 64bit versions of Win 7 Ultimate and Vista Ultimate and these 64bit versions do not show the problem.

    Monday, March 30, 2020 4:24 PM
  • The problem is you have a stolen OEM SLP product key that originally belonged to a computer manufacturer.  It will not activate anymore since it was discovered to be stolen.

    Carey Frisch

    Thursday, April 16, 2020 6:24 AM
    Moderator
  • Who discovered how that it was stolen? I seriously doubt that anybody discovered anything here.

    This looks like an error in the license server:

    • Only 32bit-versions of Win7 and Vista affected
    • Problem appears just after Win7 went out of service.
    • The systems ran without license problems for > 10 years.

    Probably some old script is running wild and bouncing on certain 32bit-versions.

    As I already wrote: These are retail box-versions bought from an official Microsoft retailer. If product keys tell something different, it must have been a production error in the first charges. Who can tell after >10 years?

    So, is anybody at Microsoft looking into the problem?
    Is there some instance where these type of problems can be addressed to?
    Or do I have to proceed with legal charges against Microsoft?

    Sunday, April 19, 2020 8:37 AM
  • To be able to PROPERLY diagnose the problem, we need the FULL output from the MGADiag tool

    Please follow this tutorial and post an MGADiag report - then we can see what the problem is.

     

    http://www.sevenforums.com/windows-updates-activation/234159-windows-genuine-activation-issue-posting-instructions.html

     

     Ignore errors produced when clicking on the Copy button - they simply mean that the tool could not create the backup files for some reason. The data is still copied to the clipboard for pasting to your response.

     

    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine (or inside the battery compartment), but do NOT quote the Key on the sticker!

    https://www.microsoft.com/en-gb/howtotell/Hardware.aspx#PCPurchase 


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, May 1, 2020 7:06 AM
    Moderator
  • FYI: OEM SLP versions of Microsoft Windows are not retail versions.  Like I pointed out before, you have a stolen counterfeit version that will never activate.

    Carey Frisch

    Friday, June 19, 2020 9:37 PM
    Moderator
  • Carey - FYI, it can be quite legitimate to use a COA SLP Product Key to activate a VM - the installed Key is NOT an OEM_SLP Key.

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.


    Wednesday, July 29, 2020 3:31 PM
    Moderator
  • So, dear moderators and Microsoft experts, here's the next bite:

    Today the same problem appeared with a Windows Server 2008 Enterprise 32-bit VM installation. System was last updated successfully on 05/19/2020. Booted the server today and it claims "this copy of Windows is not genuine".

    Again, I have a Windows Server 2008 Enterprise 64-bit VM that does NOT show the problem.

    So, we have now 32-bit versions of Windows 7, Windows Vista, and Windows Server 2008 Enterprise, all running into the same problem, while the respective 64-bit versions that I am running do not show the problem.

    And you guys want to keep telling me that exactly and only the 32-bit versions of these OSs are counterfeit? And purely by chance the 64-bit versions are not counterfeit? Should I laugh about this?

    I am telling you: This is a problem with your licensing server. For some unknown reason it is bouncing on 32-bit versions of out-of-service Windows OSs. How many more cases do you need before you start analyzing the problem on YOUR side?

    Thursday, July 30, 2020 8:12 PM
  • Please post an MGADiag report - then we have a chance of seeing what the problem is!


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, July 31, 2020 6:28 AM
    Moderator
  • Below is the MGADiag report for the Windows 2008 Server 32bit that shows the problem.

    I currently do not have the COA sticker at hand. It is stored somewhere in our archive. I will search for it next time I am there. Hopefully I will find it - must have been some 12 years ago when it was stored there. Anyway, as I wrote before: All of the Operating Systems that show the problem where bought from (then) official Microsoft retailers. The 32bit and 64bit versions of each OS were bought at the same time from the same dealer, respectively. They had been installed, successfully activated, and running for many years in these VMs.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-PRRJ2-9PTY9-DCM9Y
    Windows Product Key Hash: PTwsxqDiiy/bCVG1HyAohBvmCLA=
    Windows Product ID: 92516-083-1906714-76840
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6003.2.00030012.2.0.010
    ID: {CE63BCD2-E8B4-480C-98CA-E2E4E6AE7D0D}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Server (R) 2008 Enterprise
    Architecture: 0x00000000
    Build lab: 6003.vistasp2_ldr_escrow.191230-1836
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Disabled
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Disabled
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Disabled
    Script ActiveX controls marked as safe for scripting: Disabled

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{CE63BCD2-E8B4-480C-98CA-E2E4E6AE7D0D}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6003.2.00030012.2.0.010</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-DCM9Y</PKey><PID>92516-083-1906714-76840</PID><PIDType>5</PIDType><SID>S-1-5-21-3568200914-3129994351-1314908015</SID><SYSTEM><Manufacturer>innotek GmbH</Manufacturer><Model>VirtualBox</Model></SYSTEM><BIOS><Manufacturer>innotek GmbH</Manufacturer><Version>VirtualBox</Version><SMBIOSVersion major="2" minor="5"/><Date>20061201000000.000000+000</Date></BIOS><HWID>F5303507018400FE</HWID><UserLCID>0407</UserLCID><SystemLCID>0407</SystemLCID><TimeZone>Mitteleuropäische Zeit(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Softwarelizenzierungsdienst-Version: 6.0.6002.18005
    Name: Windows Server(R), ServerEnterprise edition
    Beschreibung: Windows Operating System - Windows Server(R), RETAIL channel
    Aktivierungs-ID: 32b40e5e-0c6d-4c6f-ab12-a031933fd2c6
    Anwendungs-ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Erweiterte PID: 92516-00152-083-190671-00-1031-6001.0000-2112015
    Installations-ID: 011601221434919984933592035683724895620970798465918855
    Prozessorzertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=48189
    Computerzertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=48190
    Lizenz-URL verwenden: http://go.microsoft.com/fwlink/?LinkID=48192
    Product Key-Zertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=48191
    Teil-Product Key: DCM9Y
    Lizenzstatus: Benachrichtigung
    Benachrichtigungsgrund: 0xC004F00F.

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: MgAAAAEAAgABAAEAAgABAAAAAgABAAEAJJSI8ryt/tsGDNizdujy9BRYdvmawaxWYkE=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      FACP            VBOX          VBOXFACP
      SSDT            VBOX          VBOXCPUT


    Friday, July 31, 2020 9:21 AM
  • In this instance, the system has determined that the hardware has changed, and the system hash is now beyond the allowed tolerance.

    Telephone activation should work, assuming that is the only problem.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, July 31, 2020 9:43 AM
    Moderator
  • Looking back at your original post, there are a number of possible scenarios - all of which have the same potential cure...

    The most likely scenario is that something failed, and gave a Not Genuine result flag - someone then decided to reinput a key that was handy - which turned out to be a COA_SLP Key (possibly off the machine's COA sticker?). Since this Key had already been allocated by the Activation servers a number of times, they automatically blocked it.

    MS will NEVER re-activate blocked Keys. They MAY issue a new Key - but I doubt they will do this for an out-of-life OS.

    This leaves you with the option of inputting a valid Key  - either using the Change Product Key link at the bottom of the System properties page, or the /ipk switch on the script. So long as the new Key is a valid Retail one that isn't in use elsewhere, it should activate without a problem.

      

     

    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, July 31, 2020 9:58 AM
    Moderator