locked
this is problem when i try to install windows live messenger 2011, RRS feed

  • Question

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-TMVMJ-BBMRX-3MBMV
    Windows Product Key Hash: 55n8g6xdzhe4AOWhmTzdzQoLfa4=
    Windows Product ID: 00426-292-0000007-85528
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {B0935A0B-3B37-4C67-B39E-3756868C9C4B}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000000
    Build lab: 7600.win7_rtm.090710-1945
    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: 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\es-ES\sppc.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\sppcext.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\slc.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\slcext.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\sppuinotify.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\slui.exe.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\sppcomapi.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\sppcommdlg.dll.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\es-ES\sppsvc.exe.mui[6.1.7264.0], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{B0935A0B-3B37-4C67-B39E-3756868C9C4B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-3MBMV</PKey><PID>00426-292-0000007-85528</PID><PIDType>5</PIDType><SID>S-1-5-21-3769083200-902367939-2397206963</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>P1.00</Version><SMBIOSVersion major="2" minor="5"/><Date>20091209000000.000000+000</Date></BIOS><HWID>A4BA3607018400F8</HWID><UserLCID>2C0A</UserLCID><SystemLCID>0C0A</SystemLCID><TimeZone>Hora estándar de Argentina(GMT-03: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-->
    Error de entrada: No se encuentra el archivo de comandos "C:\Windows\system32\slmgr.vbs".

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 1:4:2011 15:22
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Not Registered - 0x80070005
    HealthStatus Bitmask Output:


    HWID Data-->
    N/A, hr = 0x8007000d

    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            120909        APIC1838
      FACP            A M I         OEMFACP
      MCFG            120909        OEMMCFG
      OEMB            120909        OEMB1838
      AAFT            120909        OEMAAFT
      GSCI            120909        GMCHSCI
      SLIC            HPQOEM        SLIC-MPC


    Tuesday, February 1, 2011 1:48 PM

Answers

  • "dekk20" wrote in message news:389f00e2-c0e6-4e68-9df8-cb2915d5776d...
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-TMVMJ-BBMRX-3MBMV
    Windows Product Key Hash: 55n8g6xdzhe4AOWhmTzdzQoLfa4=
    Windows Product ID: 00426-292-0000007-85528
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001


     

    The Key in use here is a Default (Keyless Install) Key for Windows 7 Ultimate, which cannot be activated.
    Even if it wasn't, it would be highly unlikely to activate, as someone has installed a language pack using an old set of files.
    YOU need to uninstall the language pack, and then see whether that cures the problem - then activate your system with a proper Key for Windows 7 Ultimate.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, February 1, 2011 8:42 PM
    Tuesday, February 1, 2011 2:02 PM
    Moderator
  • Just a little more information:

    As Noel has described, you have 2 main issues

     

    1) The Product Key currently being used is called the Default Keyless Install key.  Windows can be installed without entering a Valid Product Key during the install process.  This is known as a Keyless Install.  When this is done, Windows still needs a key so it uses it's own Default Keyless Install key. The Keyless Install key acts like a Trial key and allows Windows to be used for 30 days before it requires a Valid Product Key be entered.

    So to resolve this issue, you need to change the Product Key to the Valid Product Key that came with the Windows 7 software.

     

    2) A old or (more likely) improperly installed Language Pack was installed in Windows.

      The proper way to install a Language Pack, with Windows Ultimate, is to go to Windows Update and select the language pack you want added and then Windows Update does the rest.

      However, in this case, it seems the Language Pack was installed using some other method that is not supported.  As Noel mentioned, to resolve this issue, you need to remove that Language Pack in whatever way it was originally installed.

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, February 1, 2011 8:42 PM
    Tuesday, February 1, 2011 8:41 PM

All replies

  • "dekk20" wrote in message news:389f00e2-c0e6-4e68-9df8-cb2915d5776d...
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-TMVMJ-BBMRX-3MBMV
    Windows Product Key Hash: 55n8g6xdzhe4AOWhmTzdzQoLfa4=
    Windows Product ID: 00426-292-0000007-85528
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001


     

    The Key in use here is a Default (Keyless Install) Key for Windows 7 Ultimate, which cannot be activated.
    Even if it wasn't, it would be highly unlikely to activate, as someone has installed a language pack using an old set of files.
    YOU need to uninstall the language pack, and then see whether that cures the problem - then activate your system with a proper Key for Windows 7 Ultimate.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, February 1, 2011 8:42 PM
    Tuesday, February 1, 2011 2:02 PM
    Moderator
  • Just a little more information:

    As Noel has described, you have 2 main issues

     

    1) The Product Key currently being used is called the Default Keyless Install key.  Windows can be installed without entering a Valid Product Key during the install process.  This is known as a Keyless Install.  When this is done, Windows still needs a key so it uses it's own Default Keyless Install key. The Keyless Install key acts like a Trial key and allows Windows to be used for 30 days before it requires a Valid Product Key be entered.

    So to resolve this issue, you need to change the Product Key to the Valid Product Key that came with the Windows 7 software.

     

    2) A old or (more likely) improperly installed Language Pack was installed in Windows.

      The proper way to install a Language Pack, with Windows Ultimate, is to go to Windows Update and select the language pack you want added and then Windows Update does the rest.

      However, in this case, it seems the Language Pack was installed using some other method that is not supported.  As Noel mentioned, to resolve this issue, you need to remove that Language Pack in whatever way it was originally installed.

     

    Thank you,


    Darin MS
    • Marked as answer by Darin Smith MS Tuesday, February 1, 2011 8:42 PM
    Tuesday, February 1, 2011 8:41 PM