locked
Can't Validate my authentic Install of Win7 Pro After PC Repairs RRS feed

  • Question

  • Hello!

    I have a 2-year old HP Probook 4420s which originally came with the 32-bit version of Win7 Pro. Recently, after some necessary cooling system repairs, my repair tech decided to "upgrade" my 32-bit system to 64-bit. So far, things are running smoothly, except for the fact that I've found my OS somehow "can't" now be validated (as it was before). Now, I'm no "techie," but I've tried several remedies, including the 3 given below which I found in reply to another user with a possibly similar problem:

    ~ ~ ~ ~ ~ ~

    Darin Smith MS

    Hello EndlessCT9A,

    First off, try these alternate steps to change the product key

    Click the Start button
    Type: slui.exe 3 and hit the Enter key
    Type in the Product key from the sticker on your computer
    Click the Next button.
    You will be asked if want to Activate, click ok
    It will attempt to Activate by the internet and will return an Invalid Key error (this is ok, continue to step 7)
    Click the Start button
    Type: slui.exe 4 and hit the Enter key
    Select your location in the drop down menu and click the Next button
    The next screen provides the number to call to Activate by Phone

    If that doesn't work, try these steps that will recreate Windows 7's Licensing Store.  When it recreates the file, Windows will need to repopulate it with Licensing Information so will ask you to enter the Product Key and to Activate (use the Activate by Phone method)

    1) Open an Internet Browser
    2) Type %windir%\system32 into the browser address bar.
    3) Find the file CMD.exe
    4) Right-Click on CMD.exe and select 'Run as Administrator'
    5) Type: net stop sppsvc  (it may ask you if you are sure, select yes)
    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    7) Type: rename tokens.dat tokens.bar
    8) Type: slui
    9) After a couple of seconds Windows Activation dialog will appear. You may be asked to re-activate and/or re-enter your product key.

    Lastly, if neither set of steps resolves the problem, download and run the Genuine Diagnostics tool (MGADiag.exe) at this link [REDACTED]. Click "Continue", click the "Copy" button then “Paste” the report into a reply message in this thread.

    Thank you, Darin MS
    ~ ~ ~ ~ ~ ~ ~

    With the first method, I get: 'Windows cannot access the specific device, path, or file. You may not have the appropriate permissions to access them.' With the second method, I get: 'Access denied' at step #8.

    I suspect that it's my little un-requested 64-bit "upgrade" which is at fault...but, I'm really hoping I don't have to go back to the dude who did it & wait another week for him to switch me back to 32-bit. (Please, please, please!) Following is the resulting info from my own MGADiag.exe check. I hope this aids some brilliant tech-geek in helping me resolve this problem (you know we need you guys so much!):

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-BDTBP-W8DRT-2KPK9
    Windows Product Key Hash: sVdJ9xtugE4tuNf/F/d6pTn1tnc=
    Windows Product ID: 00371-OEM-9307612-42272
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {50F09C07-F198-42BB-8F5A-375453C3F429}(1)
    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.130318-1533
    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 (x86)\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\sppcomapi.dll[6.1.7600.16384], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16384], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16384], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{50F09C07-F198-42BB-8F5A-375453C3F429}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-2KPK9</PKey><PID>00371-OEM-9307612-42272</PID><PIDType>8</PIDType><SID>S-1-5-21-1656980118-148375190-1499391892</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP ProBook 4420s</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68AHH Ver. F.20</Version><SMBIOSVersion major="2" minor="6"/><Date>20110909000000.000000+000</Date></BIOS><HWID>FE6E3F07018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1124, 5) (null): 0xC004F012

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 5:7:2013 18:42
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Not Registered - 0x80070005
    HealthStatus Bitmask Output:

    HWID Data-->
    HWID Hash Current: MAAAAAEAAgABAAEAAAABAAAAAwABAAEAJJTqwXhAZjaIgijSbKVE/N5/XEYIsFxd

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC HPQOEM 1423    
      FACP HPQOEM 1423    
      HPET HPQOEM 1423    
      MCFG HPQOEM 1423    
      ASF! HPQOEM 1423    
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SLIC HPQOEM SLIC-MPC
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
    • Edited by ibc_w Wednesday, May 8, 2013 5:11 AM
    Wednesday, May 8, 2013 5:08 AM

Answers

  • The basic problem is the File errors

    File Scan Data-->
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16384], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16384], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16384], Hr = 0x800b0100

    Please run a full CHKDSK and SFC scan....

     

    Click on Start > All Programs > Accessories

    Right-click on the Command Prompt entry

    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

     

    At the Command prompt, type

     

    CHKDSK C: /R

     

    and hit the Enter key.

    You will be told that the drive is locked,

    and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

     

    The CHKDSK will take a few hours depending on the size of the drive, so be patient!

     

    After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

    then run the SFC.

     

    SFC -System File Checker - Instructions

    Click on Start > All Programs > Accessories

    Right-click on the Command Prompt entry

    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

     

    At the Command prompt, type

     

    SFC /SCANNOW

     

    and hit the Enter key

     

    Wait for the scan to finish - make a note of any error messages - and then reboot.

     

     

    Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your SkyDrive Public folder (http://skydrive.live.com ) and post a link to it so that I can take a look.

     

    Post a new MGADiag report with details of any error messages encountered.


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

    Wednesday, May 8, 2013 6:37 AM
    Moderator