Windows 7 won't activate.


  1. Posts : 2
    Windows 7 Pro x64 SP1
       #1

    Windows 7 won't activate.


    Hi all. My problem started with inaccurate pc time and date. I tried all the usual options but to no avail, including connecting my original C. drive HDD and in the end, went the option of changing the cmos battery.
    Big mistake.
    Nothing would boot after that, including my original C. drive HDD that I'd used to clone my C. drive SSD from 12 months ago.
    Finally I disconnected all but the original HDD and tried to repair using my original Win 7Pro installation disc, but "computer says no". So I 'bit the bullet' and did a complete re-install from my installation disc 2 days ago and now I can't activate it.
    I had a look here for some answers and ended up downloading and running the 'Microsoft Genuine Advantage Diagnostic Tool', pressed the copy button and the following is the validation info.

    Diagnostic Report (1.9.0027.0):-----------------------------------------Windows Validation Data-->Validation Code: 50Cached Online Validation Code: N/A, hr = 0xc004f012Windows Product Key: *****-*****-9QK9C-MBG9X-KDDRFWindows Product Key Hash: J6zmDqn7z0Xutt3VnlNl+evRewQ=Windows Product ID: 00371-OEM-9044837-03600Windows Product ID Type: 3Windows License Type: OEM System BuilderWindows OS version: 6.1.7601.2.00010100.1.0.048ID: {9BEDF26F-6D38-4C8E-AF71-80C085AE0107}(1)Is Admin: YesTestCab: 0x0LegitcheckControl ActiveX: N/A, hr = 0x80070002Signed By: N/A, hr = 0x80070002Product Name: Windows 7 ProfessionalArchitecture: 0x00000009Build lab: 7601.win7sp1_rtm.101119-1850TTS Error: Validation Diagnostic: Resolution Status: N/AVista WgaER Data-->ThreatID(s): N/A, hr = 0x80070002Version: N/A, hr = 0x80070002Windows XP Notifications Data-->Cached Result: N/A, hr = 0x80070002File Exists: NoVersion: N/A, hr = 0x80070002WgaTray.exe Signed By: N/A, hr = 0x80070002WgaLogon.dll Signed By: N/A, hr = 0x80070002OGA Notifications Data-->Cached Result: N/A, hr = 0x80070002Version: N/A, hr = 0x80070002OGAExec.exe Signed By: N/A, hr = 0x80070002OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->Office Status: 100 GenuineMicrosoft Office Standard Edition 2003 - 100 GenuineOGA Version: N/A, 0x80070002Signed By: N/A, hr = 0x80070002Office 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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-8009_E2AD56EA-766-2f0d_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005Browser Data-->Proxy settings: N/AUser Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exeDownload signed ActiveX controls: PromptDownload unsigned ActiveX controls: DisabledRun ActiveX controls and plug-ins: AllowedInitialize and script ActiveX controls not marked as safe: DisabledAllow scripting of Internet Explorer Webbrowser control: DisabledActive scripting: AllowedScript ActiveX controls marked as safe for scripting: AllowedFile Scan Data-->File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]Other data-->Office Details: <GenuineResults><MachineData><UGUID>{9BEDF26F-6D38-4C8E-AF71-80C085AE0107}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-KDDRF</PKey><PID>00371-OEM-9044837-03600</PID><PIDType>3</PIDType><SID>S-1-5-21-495371184-2406540928-1450183666</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P2.10</Version><SMBIOSVersion major="2" minor="7"/><Date>20130712000000.000000+000</Date></BIOS><HWID>D9BE3607018400FE</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Tasmania Standard Time(GMT+10: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="{91120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>7335C7A6643A86A</Val><Hash>qiWxpyXfnQg7aGC8WVYTiaYtUg8=</Hash><Pid>70141-053-0032691-56983</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> Spsys.log Content: 0x80070002Licensing Data-->Software licensing service version: 6.1.7601.17514Name: Windows(R) 7, Professional editionDescription: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channelActivation ID: e120e868-3df2-464a-95a0-b52fa5ada4bfApplication ID: 55c92734-d682-4d71-983e-d6ec3f16059fExtended PID: 00371-00180-448-303600-02-3081-7601.0000-3402022Installation ID: 000493370014488482681804485956740760951251950534564824Processor Certificate URL: Bing Certificate URL: Bing License URL: Bing Key Certificate URL: Bing Product Key: KDDRFLicense Status: NotificationNotification Reason: 0xC004F009 (grace time expired).Remaining Windows rearm count: 3Trusted time: 6/12/2022 7:47:05 PMWindows Activation Technologies-->HrOffline: 0x00000000HrOnline: N/AHealthStatus: 0x0000000000000000Event Time Stamp: N/AActiveX: Not Registered - 0x80040154Admin Service: Not Registered - 0x80040154HealthStatus Bitmask Output:HWID Data-->HWID Hash Current: MAAAAAEAAgABAAEAAAADAAAAAQABAAEAHKImUX0iEsLo7eZ0OkM89uiC/EW54i5zOEM Activation 1.0 Data-->N/AOEM Activation 2.0 Data-->BIOS valid for OA 2.0: yes, but no SLIC tableWindows marker version: N/AOEMID and OEMTableID Consistent: N/ABIOS 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 FPDT ALASKA A M I SSDT Intel_ AoacTabl AAFT ALASKA OEMAAFT SSDT Intel_ AoacTabl SSDT Intel_ AoacTabl SSDT Intel_ AoacTabl BGRT ALASKA A M I


    Any help appreciated.
      My Computer


  2. Posts : 6,946
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #2

    Hi Brozza,

    Something really odd here
    Your system is still "registering" the fact that the time is incorrect AFTER the re-install,
    Extended PID: 00371-00180-448-303600-02-3081-7601.0000-3402022
    0xC004F009 (grace time expired)
    at the same time its also showing the correct time
    Trusted time: 6/12/2022 7:47:05 PM

    1)
    please confirm BIOS date is correct, and the latest version is installed
    2)
    Your re-install used the "American" time style format ie MM/DD/YY
    this would give your OS a June install date and cause this error
    3)
    If my last statement is correct please follow this tutorial, for an easy fix
    www.sevenforums.com/tutorials/165472-product-key-number-uninstall-deactivate-windows.html&sa=U&ved=2ahUKEwiqgcWJhOX7AhX8XqQEHSozD0sQFnoECAAQAg&usg=AOvVaw0weMqP3ZjKRo5wPYuXozzt

    after running the command please REBOOT X2

    then re-input the key
      My Computer


  3. Posts : 144
    Windows 7 Home Premium
       #3

    Brozza said:
    Any help appreciated.
    Install KB3138612, KB4474419, KB4490628.

    Microsoft Update Catalog
      My Computer


  4. Posts : 6,946
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #4

    nothing todo with windows updates.... might be usefull, but doubt it

    grace time is a standard 90 days, even WITHOUT a product key and by using slmgr/rearm, and he is showing 3 still available

    NOT 1 of them changes the OS install date
    Last edited by torchwood; 06 Dec 2022 at 17:53.
      My Computer


  5. Posts : 144
    Windows 7 Home Premium
       #5

    I may be wrong, but a fresh installation of Windows 7 is pretty much impaired without them. No Windows Update, no Definition Updates for Defender or MSE. So maybe no activation either.
      My Computer


  6. Posts : 6,946
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #6

    I dont doubt that, but the errors are NOT related to WU, but the date of the OS installation which the MGAdiag reports as being older than the 90 day grace period. Which we know is wrong

    SLUI changes, ie Activation, have never been updated by any WU, apart from KB971033
    (which was introduced to combat illegal/non-genuine installs)
      My Computer


  7. Posts : 2
    Windows 7 Pro x64 SP1
    Thread Starter
       #7

    Windows 7 now activated


    Thanks to all for the suggestions.
    I ended up finding another 'phone number to call for activation help and it worked fine, (I'd previously only tried the first of 2 numbers presented, which was non active). I still haven't rectified the problem of my C drive SSD not being bootable but will try a disc repair with the installation disc again.
      My Computer


 

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

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