locked
Windows 7 Professional appears Genuine but requires frequent activation/validation RRS feed

  • Question

  • I am running Windows 7 Professional SP1, 64 bit OS on a home-built PC - an upgrade from Vista 32 bit OS.

    My problem is that every few days (ranging from 2 to 14 so far), the Windows Activation status changes from 'activated' to 'needs activation, x days left to activate' where x has a maximum value of 3 (I've never seen it bigger than that).

    I can click the link and it activates OK. I have also activated by telephone. I can also 'validate' my installation via the microsoft site 'http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation'. Any of these methods results in my installation being recognised as 'Genuine' and the status goes back to 'activated'

    Running the MGADiagnostic tool, it always says the installation is genuine - regardless of what it says in the 'Control Panel -> System and Security -> System'

    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    However, whenever the status changes so that activation is required, the MGADiagnostic tool indicates that the 'HWID Hash Current' has changed - but I haven't changed any of the hardware.

    I've run Kaspersky anti-virus since first installation, and haven't had any virus reports - I've run out of ideas!

    PS: My W7 ISO image is valid and my key was purchased from a reputable vendor.

    Saturday, December 24, 2011 9:17 AM

Answers

  • No further reply from the Original Poster.

    Issue is assumed to be resolved.
    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, January 3, 2012 10:37 PM
    Tuesday, January 3, 2012 10:37 PM

All replies

  • "a965_2011" wrote in message news:13ac4c4d-a717-4f3e-87b1-057f270f2e5d...

    I am running Windows 7 Professional SP1, 64 bit OS on a home-built PC - an upgrade from Vista 32 bit OS.

    My problem is that every few days (ranging from 2 to 14 so far), the Windows Activation status changes from 'activated' to 'needs activation, x days left to activate' where x has a maximum value of 3 (I've never seen it bigger than that).

    I can click the link and it activates OK. I have also activated by telephone. I can also 'validate' my installation via the microsoft site 'http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation'. Any of these methods results in my installation being recognised as 'Genuine' and the status goes back to 'activated'

    Running the MGADiagnostic tool, it always says the installation is genuine - regardless of what it says in the 'Control Panel -> System and Security -> System'

    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    However, whenever the status changes so that activation is required, the MGADiagnostic tool indicates that the 'HWID Hash Current' has changed - but I haven't changed any of the hardware.

    I've run Kaspersky anti-virus since first installation, and haven't had any virus reports - I've run out of ideas!

    PS: My W7 ISO image is valid and my key was purchased from a reputable vendor.

    A couple of points.
    1 – without an MGADiag report we’re guessing
    2 – you cannot buy just a Key. If you did, then it’s a counterfeit, or MSDN Key, or has been shared around, which is why it’s failing validation,
     
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
      - **in your own thread**, please
     
    Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine, but do NOT quote the Key on the sticker!
    http://www.microsoft.com/howtotell/content.aspx?pg=coa
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, December 24, 2011 9:27 AM
    Moderator
  • OK, Maybe you can help me. Here is what you have asked for.

     

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 0x8004FE21

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-*****-*****-C8H26

    Windows Product Key Hash: /cCt81DWQp+tC20RGQ5joEW8qCU=

    Windows Product ID: 55041-091-8902324-86631

    Windows Product ID Type: 6

    Windows License Type: Volume MAK

    Windows OS version: 6.1.7601.2.00010100.1.0.048

    ID: {A4E1E22E-3C04-4B3D-A43A-C72FB00847BC}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110622-1506

    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:\Users\hans\AppData\Local\Google\Chrome\Application\chrome.exe

    Download signed ActiveX controls: Prompt

    Download unsigned ActiveX controls: Disabled

    Run ActiveX controls and plug-ins: Allowed

    Initialize and script ActiveX controls not marked as safe: Disabled

    Allow scripting of Internet Explorer Webbrowser control: Disabled

    Active scripting: Allowed

    Script ActiveX controls marked as safe for scripting: Allowed

     

    File Scan Data-->

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003

    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100

    File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{A4E1E22E-3C04-4B3D-A43A-C72FB00847BC}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-091-8902324-86631</PID><PIDType>6</PIDType><SID>S-1-5-21-3949010992-477547852-3739269824</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1850</Version><SMBIOSVersion major="2" minor="6"/><Date>20110627000000.000000+000</Date></BIOS><HWID>1E2D3B07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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-->

    Input Error: There is no script engine for file extension ".vbs".

     

    Windows Activation Technologies-->

    HrOffline: 0x8004FE21

    HrOnline: N/A

    HealthStatus: 0x000000000001EFF0

    Event Time Stamp: 12:25:2011 00:29

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

    Tampered File: %systemroot%\system32\sppobjs.dll

    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui

    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui

    Tampered File: %systemroot%\system32\sppwinob.dll

    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui

    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui

    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui

    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration

    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui

    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui

    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui

    Tampered File: %systemroot%\system32\drivers\spsys.sys

     

     

    HWID Data-->

    HWID Hash Current: PgAAAAEAAQABAAEABAADAAAABQABAAEAHKKelTAFIM3ewn7MrIveiDC6MAcUCJSIF/OAHNBrjKByir5BLnM=

     

    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

      APIC ALASKA A M I

      FACP ALASKA A M I

      HPET ALASKA A M I

      MCFG ALASKA A M I

      SSDT AMICPU PROC

     

    Sunday, December 25, 2011 12:34 AM
  • Click Start, type 'cmd' in the Search/Run box, and right click on the CMD icon at the top of the results pane.  Select Run as Administrator.  When the cmd window opens type 'sfc /scannow' at the prompt and hit Enter.  When the scan completes close the cmd window.  Rerun the MGADiag tool and post the report as before.

    You are using a volume license key.  KMS (Key Management Service) keys need to be activated on the organization's servers which issued the key.  Activation needs to be renewed at least once every 180 days.  You need to contact your organization's program manager if you need instructions.  The TechNet page describing volume license key requirements is at

    http://technet.microsoft.com/en-us/library/ff793434.aspx


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Sunday, December 25, 2011 12:59 AM
    Answerer
  • OK - I successfully validated the installation on 22nd Dec (via the Microsoft site 'http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation'). I looked at the status again today (27th Dec) and had 1 day left to activate.  I ran the MGA tool then sucessfully re-activated via the Microsoft site above.

    The only difference between the MGA results on 27th and 22nd December (apart from timestamp information, and the indication I had 1 day left to activate) was that the HWID Hash Current had changed

    ========== Here's what a comparison between the MGA outputs looks like in MS Word =================

    HWID Hash Current: <del datetime="2011-12-27T07:54" cite="mailto:David">MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8xLWyPQ=</del><ins datetime="2011-12-27T07:54" cite="mailto:David">NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8yeUEtbI9A==</ins>

    ==========

    ... and here's the output from the MGA tool on 27th Dec, before I validated the installation:

    Diagnostic Report (1.9.0019.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Genuine

    Validation Code: 0

     

    Cached Validation Code: 0x0

    Windows Product Key: *****-*****-K78R7-H6J9K-YGXX8

    Windows Product Key Hash: mFr54pUn0F2jN6kYt2QhF0xKmX4=

    Windows Product ID: 00371-177-9123321-85168

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7601.2.00010100.1.0.048

    ID: {E778AAD0-2B57-4A83-9B9B-A3B120CFC503}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110622-1506

    TTS Error:

    Validation Diagnostic:

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: N/A, hr = 0x80070002

     

    WGA 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: 100 Genuine

    Microsoft Office Enterprise 2007 - 100 Genuine

    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 (x86)\Mozilla Firefox\firefox.exe

    Download signed ActiveX controls: Prompt

    Download unsigned ActiveX controls: Disabled

    Run ActiveX controls and plug-ins: Allowed

    Initialize and script ActiveX controls not marked as safe: Disabled

    Allow scripting of Internet Explorer Webbrowser control: Disabled

    Active scripting: Allowed

    Script ActiveX controls marked as safe for scripting: Allowed

     

    File Scan Data-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{E778AAD0-2B57-4A83-9B9B-A3B120CFC503}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-YGXX8</PKey><PID>00371-177-9123321-85168</PID><PIDType>5</PIDType><SID>S-1-5-21-765618363-3102659786-3780502038</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA69VM-S2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20080303000000.000000+000</Date></BIOS><HWID>D5E03A07018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>7313746F547D6D2</Val><Hash>HNQbkFwtHneZ9i/jRi7uJ3uVV5g=</Hash><Pid>81599-873-8310097-65482</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Activation ID: e838d943-63ed-4a0b-9fb1-47152908acc9

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00371-00170-177-912332-00-2057-7601.0000-2942011

    Installation ID: 020303436520702826587813339592917201953990807220588253

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340

    Partial Product Key: YGXX8

    License Status: Additional grace period (KMS license expired or hardware out of tolerance)

    Time remaining: 1500 minute(s) (1 day(s))

    Remaining Windows rearm count: 3

    Trusted time: 27/12/2011 07:44:06

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: 0x00000000

    HealthStatus: PASS

    Event Time Stamp: 12:22:2011 22:08

    WAT Activex: Registered

    WAT Admin Service: Registered

     

    HWID Data-->

    HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8xLWyPQ=

     

    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

      APIC                                    GBT                        GBTUACPI

      FACP                                   GBT                        GBTUACPI

      HPET                                    GBT                        GBTUACPI

      MCFG                                 GBT                        GBTUACPI

      SSDT                                    PTLTD                    POWERNOW

     

     

     

     

    <ins datetime="2011-12-27T07:54" cite="mailto:David"></ins>

    Tuesday, December 27, 2011 8:14 AM
  • "a965_2011" wrote in message news:2f5ad13e-b061-467a-a10a-10ab2c30172a...

    OK - I successfully validated the installation on 22nd Dec (via the Microsoft site 'http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation'). I looked at the status again today (27th Dec) and had 1 day left to activate.  I ran the MGA tool then sucessfully re-activated via the Microsoft site above.

    The only difference between the MGA results on 27th and 22nd December (apart from timestamp information, and the indication I had 1 day left to activate) was that the HWID Hash Current had changed

    ========== Here's what a comparison between the MGA outputs looks like in MS Word =================

    HWID Hash Current: <del datetime="2011-12-27T07:54" cite="mailto:David">MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8xLWyPQ=</del><ins datetime="2011-12-27T07:54" cite="mailto:David">NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8yeUEtbI9A==</ins>

    ==========

    ... and here's the output from the MGA tool on 27th Dec, before I validated the installation:

    Diagnostic Report (1.9.0019.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Genuine

    Validation Code: 0

     

    Cached Validation Code: 0x0

    Windows Product Key: *****-*****-K78R7-H6J9K-YGXX8

    Windows Product Key Hash: mFr54pUn0F2jN6kYt2QhF0xKmX4=

    Windows Product ID: 00371-177-9123321-85168

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7601.2.00010100.1.0.048

     

     

    OGA Data-->

    Office Status: 100 Genuine

    Microsoft Office Enterprise 2007 - 100 Genuine

     

    Other data-->

    SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA69VM-S2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20080303000000.000000+000</Date></BIOS

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Partial Product Key: YGXX8

    License Status: Additional grace period (KMS license expired or hardware out of tolerance)

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes, but no SLIC table

     

     
    You need to use telephone activation – the system thinks that your hardware has changed since the last successful activation, and requires physical confirmation.
    telephone activation.
    Click on the Start button
    in the Search box, type
    SLUI 4
    and hit the Enter key
    follow the instructions - but when asked which service you require by the telephone ansafone, do NOT reply - this should force an operator to respond, who can deal with you.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, December 27, 2011 9:27 AM
    Moderator
  • I activated by telephone yesterday with no problems - helpful person, but couldn't provide any info on why my system keeps losing track of its activation status and pointed me at Microsoft technical support.

    Starting up today, it's back to '3 days left to activate' and the HWID has changed in the MGA output (ironically, back to the value it had on 22 Dec).

    I successfully validated via the Microsoft site (http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation), and activation status has gone back to 'activated'.

    However, I really don't understand why the software keeps thinking the HWID is changing (when no HW changes have been made). Anyone got any ideas? Does anyone know the structure of the HWID (i.e. which bytes are generated from which items of hardware) - I could at least then determine which bits of HW Windows thinks are changing.

    Wednesday, December 28, 2011 8:21 AM
  • "a965_2011" wrote in message news:b22173cd-94a0-4768-bd2c-39348ece1e88...

    I activated by telephone yesterday with no problems - helpful person, but couldn't provide any info on why my system keeps losing track of its activation status and pointed me at Microsoft technical support.

    Starting up today, it's back to '3 days left to activate' and the HWID has changed in the MGA output (ironically, back to the value it had on 22 Dec).

    I successfully validated via the Microsoft site (http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation), and activation status has gone back to 'activated'.

    However, I really don't understand why the software keeps thinking the HWID is changing (when no HW changes have been made). Anyone got any ideas? Does anyone know the structure of the HWID (i.e. which bytes are generated from which items of hardware) - I could at least then determine which bits of HW Windows thinks are changing.

    That’s really strange – please post another MGADiag report so we can take a look.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, December 28, 2011 8:30 AM
    Moderator
  • Here we go ...

    ====================

    Diagnostic Report (1.9.0019.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Genuine

    Validation Code: 0

     

    Cached Validation Code: 0x0

    Windows Product Key: *****-*****-K78R7-H6J9K-YGXX8

    Windows Product Key Hash: mFr54pUn0F2jN6kYt2QhF0xKmX4=

    Windows Product ID: 00371-177-9123321-85168

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7601.2.00010100.1.0.048

    ID: {E778AAD0-2B57-4A83-9B9B-A3B120CFC503}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110622-1506

    TTS Error:

    Validation Diagnostic:

    Resolution Status: N/A

     

    WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: N/A, hr = 0x80070002

     

    WGA 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: 100 Genuine

    Microsoft Office Enterprise 2007 - 100 Genuine

    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 (x86)\Mozilla Firefox\firefox.exe

    Download signed ActiveX controls: Prompt

    Download unsigned ActiveX controls: Disabled

    Run ActiveX controls and plug-ins: Allowed

    Initialize and script ActiveX controls not marked as safe: Disabled

    Allow scripting of Internet Explorer Webbrowser control: Disabled

    Active scripting: Allowed

    Script ActiveX controls marked as safe for scripting: Allowed

     

    File Scan Data-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{E778AAD0-2B57-4A83-9B9B-A3B120CFC503}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-YGXX8</PKey><PID>00371-177-9123321-85168</PID><PIDType>5</PIDType><SID>S-1-5-21-765618363-3102659786-3780502038</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA69VM-S2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20080303000000.000000+000</Date></BIOS><HWID>D5E03A07018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>7313746F547D6D2</Val><Hash>HNQbkFwtHneZ9i/jRi7uJ3uVV5g=</Hash><Pid>81599-873-8310097-65482</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Activation ID: e838d943-63ed-4a0b-9fb1-47152908acc9

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00371-00170-177-912332-00-2057-7601.0000-2942011

    Installation ID: 020303436520702826587813339592917201953990807220588253

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340

    Partial Product Key: YGXX8

    License Status: Additional grace period (KMS license expired or hardware out of tolerance)

    Time remaining: 4320 minute(s) (3 day(s))

    Remaining Windows rearm count: 3

    Trusted time: 28/12/2011 07:27:18

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: 0x00000000

    HealthStatus: PASS

    Event Time Stamp: 12:27:2011 07:47

    WAT Activex: Registered

    WAT Admin Service: Registered

     

    HWID Data-->

    HWID Hash Current: NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8yeUEtbI9A==

     

    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

      APIC                                    GBT                        GBTUACPI

      FACP                                   GBT                        GBTUACPI

      HPET                                    GBT                        GBTUACPI

      MCFG                                 GBT                        GBTUACPI

      SSDT                                    PTLTD                    POWERNOW

     

     

    Wednesday, December 28, 2011 2:09 PM
  • "a965_2011" wrote in message news:a66a7e84-622c-4f5c-bcd8-77a9bc7599c5...

    Here we go ...

    ====================

    Diagnostic Report (1.9.0019.0):

    -----------------------------------------

     

     
    You’re using an old copy of MGADiag again. please delete your current version
    Please use the latest version – from http://go.microsoft.com/fwlink/?linkid=52012
    and post a new report.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, December 29, 2011 1:05 PM
    Moderator
  • No further reply from the Original Poster.

    Issue is assumed to be resolved.
    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, January 3, 2012 10:37 PM
    Tuesday, January 3, 2012 10:37 PM
  • I haven't had much time since Christmas to look at this - I just keep re-activating Windows. However, it's starting to get even more regular now and just validating via the Microsoft validation site (http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation) doesn't always work and I've had to re-enter my product key a couple of times to get back to active/genuine status.

    Here's my latest MGADiag output from MGADiag verison 1.9.0027.0 (it still all seems to be pointing at HWIDs changing)

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 0

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-K78R7-H6J9K-YGXX8

    Windows Product Key Hash: mFr54pUn0F2jN6kYt2QhF0xKmX4=

    Windows Product ID: 00371-177-9123321-85168

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7601.2.00010100.1.0.048

    ID: {E778AAD0-2B57-4A83-9B9B-A3B120CFC503}(3)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Professional

    Architecture: 0x00000009

    Build lab: 7601.win7sp1_gdr.110622-1506

    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: 100 Genuine

    Microsoft Office Enterprise 2007 - 100 Genuine

    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 (x86)\Mozilla Firefox\firefox.exe

    Download signed ActiveX controls: Prompt

    Download unsigned ActiveX controls: Disabled

    Run ActiveX controls and plug-ins: Allowed

    Initialize and script ActiveX controls not marked as safe: Disabled

    Allow scripting of Internet Explorer Webbrowser control: Disabled

    Active scripting: Allowed

    Script ActiveX controls marked as safe for scripting: Allowed

     

    File Scan Data-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{E778AAD0-2B57-4A83-9B9B-A3B120CFC503}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-YGXX8</PKey><PID>00371-177-9123321-85168</PID><PIDType>5</PIDType><SID>S-1-5-21-765618363-3102659786-3780502038</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA69VM-S2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20080303000000.000000+000</Date></BIOS><HWID>D5E03A07018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>7313746F547D6D2</Val><Hash>HNQbkFwtHneZ9i/jRi7uJ3uVV5g=</Hash><Pid>81599-873-8310097-65482</Pid><PidType>1</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Activation ID: e838d943-63ed-4a0b-9fb1-47152908acc9

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00371-00170-177-912332-00-2057-7601.0000-0332012

    Installation ID: 013790078530007711543130947601512885433925046540865592

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340

    Partial Product Key: YGXX8

    License Status: Additional grace period (KMS license expired or hardware out of tolerance)

    Time remaining: 2760 minute(s) (1 day(s))

    Remaining Windows rearm count: 3

    Trusted time: 04/02/2012 09:30:20

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: 0x00000000

    HealthStatus: 0x0000000000000000

    Event Time Stamp: 2:4:2012 09:15

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

     

     

    HWID Data-->

    HWID Hash Current: NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzruJEklZCmPKlS+9Q2Yj1k8yeUEtbI9A==

     

    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

      APIC                                    GBT                        GBTUACPI

      FACP                                   GBT                        GBTUACPI

      HPET                                    GBT                        GBTUACPI

      MCFG                                 GBT                        GBTUACPI

      SSDT                                    PTLTD                    POWERNOW

     

     

    Saturday, February 4, 2012 9:36 AM
  • "a965_2011" wrote in message news:e93437b6-e991-4238-b77f-50fe714b6be3...

    I haven't had much time since Christmas to look at this - I just keep re-activating Windows. However, it's starting to get even more regular now and just validating via the Microsoft validation site (http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation) doesn't always work and I've had to re-enter my product key a couple of times to get back to active/genuine status.

    Here's my latest MGADiag output from MGADiag verison 1.9.0027.0 (it still all seems to be pointing at HWIDs changing)

    Diagnostic Report (1.9.0027.0):

    -----------------------------------------

    Windows Validation Data-->

     

    Validation Code: 0

    Cached Online Validation Code: 0x0

    Windows Product Key: *****-*****-K78R7-H6J9K-YGXX8

    Windows Product Key Hash: mFr54pUn0F2jN6kYt2QhF0xKmX4=

    Windows Product ID: 00371-177-9123321-85168

    Windows Product ID Type: 5

    Windows License Type: Retail

     

     

    File Scan Data-->

     

    Other data-->

    Office Details: <GenuineResults><MachineData><UGUID>{E778AAD0-2B57-4A83-9B9B-A3B120CFC503}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-YGXX8</PKey><PID>00371-177-9123321-85168</PID><PIDType>5</PIDType><SID>S-1-5-21-765618363-3102659786-3780502038</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-MA69VM-S2</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20080303000000.000000+000</Date></BIOS

     

     

    Licensing Data-->

    Software licensing service version: 6.1.7601.17514

     

    Name: Windows(R) 7, Professional edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Partial Product Key: YGXX8

    License Status: Additional grace period (KMS license expired or hardware out of tolerance)

    Time remaining: 2760 minute(s) (1 day(s))

    Remaining Windows rearm count: 3

    Trusted time: 04/02/2012 09:30:20

     

     

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes, but no SLIC table

     

     

    Assuming that you aren’t in fact changing hardware or drivers, I can think of one scenario that may cause this problem – it the vendor had sold the same license multiple times (which means that others will be having the same problem!) Who was the vendor?
     
     
    Darin may be able to check the Key and see what the history is like from an Activation POV
     
    The two latest reports show the change in HWID....
    HWID Hash Current: NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzruJEklZCmPKlS
    HWID Hash Current: NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8yeUEtbI9A==
     
    Comparing that with your earlier ones...

    MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8xLWyPQ=

    NAAAAAEABAABAAEAAAADAAAAAQABAAEAJJT2nQzrJJWQpjypuJFS+9Q2Yj1k8yeUEtbI9A==

    ==========

    Unfortunately I have no idea of the significance, and I suspect that the Hash is a one-way one, so specifics cannot be read from it even by MS.
     
    One thing that *will* have changed regularly throughout this period is your AV.
    I wonder if this is some strange effect of that?
    What other AV’s have EVER been installed on this machine (since the last reformat/reinstall)?
    You’re running Kaspersky, currently – have you upgraded the version-wise at all?
    It may be worth uninstalling it completely, running the removal tool, and then installing MSE for a few days to see if the problem goes away.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, February 4, 2012 10:56 AM
    Moderator
  • >Who was the vendor?

    I got the software from Software4Students - http://www.software4students.co.uk/

    It was provided as a download from their site and they sent me the key. I validated the md5 hash of the iso which I dowloaded and that looked OK compared with references on the internet.

    I've only ever used Kaspersky AV on this particular machine. I'm a bit reluctant to go through the hassle of removing it - as I mentioned earlier, I'm pretty busy at the moment.

    Do you know if I am likely to 'run out' of activation attempts at some point?

    Thanks.

    Saturday, February 4, 2012 1:41 PM
  • They should certainly be OK - they are certainly a genuine company, and acknowledged as such by MS.

    (IIRC the download actually was from Digital River??)

    You will eventually have problems  with activation unless you find the cause - you'll have to use telephone activation, and explain to an opertor the problem at some point. (point them at this thread if you get the chance)

    I'd suggest trying validation first and seeing what that has to say (if you get nothing useful off the main validation page, use the Diagnostics page at www.microsoft.com/genuine/validate )

    Sorry I can't be any more help.

     

    You're not using any kind of Registry Cleaner or system optimiser are you?

    Any  maintenance that gets done maybe just before the problem rears its ugly head??

    (clutching at 'usual suspects' and other straws, here :) )

     

     

     


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, February 4, 2012 3:08 PM
    Moderator
  • :-(

    Nope, I don't have any registry cleaning or system optimisation going on (at least that I would have put in place myself - I don't know what Windows might be doing automatically...

    Saturday, February 4, 2012 4:13 PM
  • Here's something I noticed ...

    Right at the end of the BIOS output at bootup there's a message:

    "Verifying DMI pool data ...."

    but sometimes (I don't know why) the message is:

    "Verifying DMI pool data .... Update success!"

    Just wondering if this could be interpreted by Windows as a 'hardware change' which triggers the 'needs activation' ???

    I also don't know what triggers the "Update success!" :-(

    Monday, April 16, 2012 9:32 PM
  • No.  DMI is the Desktop Management Interface which is just a layer between the BIOS and your computer's components.  When the computer BIOS is "Verifying DMI pool data" it is simply checking that the table of data it sends to the operating system is ok.  "Update success" has nothing to do with updating the BIOS or Windows.  It is just updating the table.  If the check failed you would likely have a shutdown.

    It has been a couple of months since the last postings so please provide another MGADiag report so we can see the current situation.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Monday, April 16, 2012 9:44 PM
    Answerer
  • Hmmm...

    I pursued this a bit.

    If I leave the PSU switch at the back of the computer on, there doesn't seem to be any problem with activation changing over shutdowns and reboots.

    However, if I turn everything off at the PSU or the power socket and then back on the following happens:

    when I boot I get the "Verifying DMI pool data .... " message (but no 'Update success')
    Windows comes up and everything is fine
    When I run MGA tool the Installation ID and HWID Hash have both changed from before the reboot.

    When I reboot NEXT (without turning off at the PSU) I get the "Verifying DMI pool data .... Update success!" message from the BIOS and when Windows comes up it needs activating (but running MGA tool shows the Installation ID and HWID Hash don't change from before the reboot).

    This behaviour is 100% consistent. I usually switch the computer off at the wall every night which explains why I keep getting requests to (re)activate!

    I don't know how to fix it though! Could it be a CMOS/batttery problem?

    Wednesday, April 18, 2012 9:56 PM
  • "a965_2011" wrote in message news:b1949314-e066-4020-a068-d2b2186a5fe1...

     

    I don't know how to fix it though! Could it be a CMOS/batttery problem?

     
     
    Certainly, the CMOS battery could well be the cause of the problem - especially if the system is spotting a date-change and flagging non-genuine because of that, before the system gets a chance to update the clock.
     
    Since it's a desktop, changing the CMOS battery is a 5-minute job, and costs less than a pound (I bought a pack of four recently for £1 in a store in Rhyl).
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, April 18, 2012 10:11 PM
    Moderator
  • Probably a good guess.  The computer retains a hardware list in CMOS for comparision at the next startup.  If a new device is detected on startup a change in the list is how plug-n-play knows to install a device driver.

    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Wednesday, April 18, 2012 10:13 PM
    Answerer
  • Wednesday, April 18, 2012 10:16 PM
    Moderator
  • OK - took out the CMOS battery, let the CMOS clear for 5 minutes, put a new battery in, same situation:

    1. switch off a the PSU (or wall socket)
    2. Switch back on and turn on - get a 'Verifying DMI pool data' message from the BIOS (but no 'Update success' message)
    3. Windows 7 boots, and looking in Computer->Properties says it is activated and genuine
    4. Shutdown but do NOT switch off at PSU or the wall
    5. Reboot - get a 'Verifying DMI pool data' message from the BIOS - AND and 'Update success' message
    6. Windows boots and looking in Computer->Properties it says it needs to be activated
    7.  Go to Windows validation URL (http://windows.microsoft.com/en-GB/windows/help/genuine/what-is-validation) and validate - says everything is OK and it's all back to normal.

    ???

    Running the MGA tools shows that the 'HWID Hash Current' changes as does the 'Installation ID' - these changes appear to be tied together i.e when one changes, the other changes too.

    I have made no hardware changes (!)

    Note that when running this test a number of times, I don't get purely random HWIDs and Installation IDs - there appears to be a set of 4 HW/Installation ID pairs  which occur in an apparently random order.

    I'm wondering now if this is a hardware issue.

    Saturday, April 21, 2012 7:45 PM
  • Did you replace the battery with a new one? (pointless exercise otherwise)

    It certainly appears to be a hardware problem - probably related to detection of 'peripherals' (NIC most often, or on-board graphics)

    what happens if you disable the NIC? does the ID change to the same extent? (is the graphics onboard, or on a card?)


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Saturday, April 21, 2012 8:01 PM
    Moderator
  • It could also be device drivers, which sometimes look to the activation technology like hardware changes.  Update your drivers one by one to see if that changes anything.

    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

    Saturday, April 21, 2012 11:28 PM
    Answerer
  • Firstly, thanks very much for your prompt responses - they're much appreciated.

    I took my PCIe graphics card out last night and ran with the onboard graphics - made no difference to the activiation issue, behaviour was still the same as in my last post, so I just put my card back in.

    I haven't tried updating all my drivers, but I must admit I'm beginning to lose the will on this one now ... :-(

    What gets me is that although in Computer->Properties it mights say "Activate windows ...", if I go to the Microsoft _validation_ site, it's quite happy to say my Windows installation is valid and my system is updated somehow so that I don't need to actually reactivate. The only times I've ever had to type in my product code again is when I've failed to go to the validation site before my 'x days to activate' have expired.

    Makes me think I should just write a startup script that runs in background and visits the Microsoft validation site at bootup ... (!)

    Sunday, April 22, 2012 8:54 AM
  • "a965_2011" wrote in message news:9dcc184d-f821-475f-9972-9e339fefd403...

     

    Makes me think I should just write a startup script that runs in background and visits the Microsoft validation site at bootup ... (!)

     
     
    That may not be such a bad idea :)

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Sunday, April 22, 2012 11:04 AM
    Moderator
  • The startup script seems to be working so far.

    One other thing I found:

    https://forums.virtualbox.org/viewtopic.php?f=2&t=22653&start=30#p106403

    Sounds like changes to the System UUID in the DMI data may cause Windows to think reactivation is needed.

    I downloaded a tool called CPU-Z (http://www.cpuid.com/softwares/cpu-z.html) which provides information on the DMI contents.

    Whenever the BIOS reports 'Update success!', and I then run CPU-Z after Windows boots, the DMI System UUID has changed :-(

    (and similarly, it doesn't change if I don't get the 'Update success!' message from the BIOS.

    Don't know what causes the System UUID to change though.

    Wednesday, May 2, 2012 2:42 PM
  • "a965_2011" wrote in message news:b1e9d184-b93c-4509-963f-19cbdaf952fd...

    The startup script seems to be working so far.

    One other thing I found:

    https://forums.virtualbox.org/viewtopic.php?f=2&t=22653&start=30#p106403

    Sounds like changes to the System UUID in the DMI data may cause Windows to think reactivation is needed.

    I downloaded a tool called CPU-Z (http://www.cpuid.com/softwares/cpu-z.html) which provides information on the DMI contents.

    Whenever the BIOS reports 'Update success!', and I then run CPU-Z after Windows boots, the DMI System UUID has changed :-(

    (and similarly, it doesn't change if I don't get the 'Update success!' message from the BIOS.

    Don't know what causes the System UUID to change though.

    The things I can think of (apart from failing CMOS) relate to storage devices, mostly - either boot order itself, or attaching USB devices which may affect boot order.
    I'd check that.
     
    Thanks for coming back with your results!
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, May 2, 2012 2:52 PM
    Moderator