locked
Asus laptop returned afer manufacture repair RRS feed

  • Question

  • My Asus K60IJ was recently returned to me from Asus with an unvalidated windows

     

     

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

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-QCPVQ-KHRB8-RMV82
    Windows Product Key Hash: +Rj3N34NLM2JqoBO/OzgzTZXgbY=
    Windows Product ID: 00359-OEM-8992687-00095
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {B5D34E7C-AAD5-4AB9-81BC-301D920EB64E}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7600.win7_rtm.090713-1255
    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)\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-->
    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>{B5D34E7C-AAD5-4AB9-81BC-301D920EB64E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-RMV82</PKey><PID>00359-OEM-8992687-00095</PID><PIDType>2</PIDType><SID>S-1-5-21-4070860634-2794675311-1628887733</SID><SYSTEM><Manufacturer>ASUSTeK Computer Inc.        </Manufacturer><Model>K60IJ               </Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>206    </Version><SMBIOSVersion major="2" minor="5"/><Date>20091203000000.000000+000</Date></BIOS><HWID>2ABA3607018400F8</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-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00178-926-800095-02-1033-7600.0000-0672011
    Installation ID: 103683498196204054231436883765894356030251548146571594
    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: RMV82
    License Status: Notification
    Notification Reason: 0xC004F057.
    Remaining Windows rearm count: 2
    Trusted time: 3/8/2011 3:19:26 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAEAAQABAAIAAAABAAAAAgABAAEA6GE+J3Ka0jOwEIaJlAmegxbr3g9Gyg==

    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            120309        APIC1811
      FACP            120309        FACP1811
      DBGP            120309        DBGP1811
      HPET            120309        OEMHPET
      BOOT            120309        BOOT1811
      MCFG            120309        OEMMCFG
      OEMX            120309        OEMX1811
      ECDT            120309        OEMECDT
      OEMB            120309        OEMB1811
      GSCI            120309        GMCHSCI
      SSDT            PmRef        CpuPm


    Tuesday, March 8, 2011 8:27 PM

Answers

  • Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)     COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer. It is a valid product key, but should only be used in limited situations (such as if the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)

     

       Your Windows is using an OEM SLP key, but (for whatever reason) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate. It is possible that Asus changed out the Motherboard and didn't add the correct Bios.

     

      To fix the issue, you will need to change out the OEM SLP key with the COA SLP key.  The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard.

     If this doesn't work, I recommend contacting Asus and ask them to fix what they have caused.

     

    Thank you,


    Darin MS
    Tuesday, March 8, 2011 8:47 PM

All replies

  • Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

    A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

     

    B)     COA SLP: This is the Product key that you see on the sticker on the side (or bottom) of your computer. It is a valid product key, but should only be used in limited situations (such as if the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone. (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer)

     

       Your Windows is using an OEM SLP key, but (for whatever reason) cannot see the OEM Bios Flag in the computer’s motherboard and is unable to Self-Activate. It is possible that Asus changed out the Motherboard and didn't add the correct Bios.

     

      To fix the issue, you will need to change out the OEM SLP key with the COA SLP key.  The normal way to do this is to click the ‘Start’ button, right-click ‘Computer’, select ‘Properties’ and then click ‘Change Product Key’ (located in the lower right-hand side of the window). Enter the COA SLP key and follow the instructions in the Change Product Key Wizard.

     If this doesn't work, I recommend contacting Asus and ask them to fix what they have caused.

     

    Thank you,


    Darin MS
    Tuesday, March 8, 2011 8:47 PM
  • Darin'

    Isn't the key used here the Dell OEM slp key? 

    I'm trying to learn about this and my first guess was a botched activation exploit.

    Tuesday, March 8, 2011 9:01 PM
    Answerer
  • Hi george1009,

      Yes, the key does appear to be a Dell key and it is possible that the issue could have been caused by a botched activation exploit or it could have been caused by using a Dell Recovery Disks without knowing it could cause a problem using a Dell disk in an Asus PC or it could have been caused by some other legitimate reason you or I haven't though of. 

      But whatever the ultimate cause of the issue was, that doesn't change how to resolve the issue.

      As long as you understand and issue and can provide a fix for that issue (and the fix results in a Genuine Windows) it doesn't really matter which of a number of possible causes actually resulted in a particular issue.

     

    Thanks,

     

     


    Darin MS
    Wednesday, March 9, 2011 10:01 PM
  • Thanks a lot Darin.  My biggest problem with my learning process is in composing responses as my obnoxious disorder wants to get in the way. I have started and then deleted several replies as when I reread them they sounded gruff.

    I appreciate the guidance.

    Wednesday, March 9, 2011 10:36 PM
    Answerer