Copy of Windows not genuine Build 6002 (Presario)

All replies

• 

  

  0

  Sign in to vote

  The problem appears to be in the Licensing Store - please try the following.....

   

  Recreate the Licensing Store with the correct data.

   

  1) Open an Internet Browser window.

  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 slsvc (it may ask you if you are sure, select yes)

  6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing

  7) Type: rename tokens.dat tokens.bar

  8) Type: cd %windir%\system32

  9) Type: net start slsvc

  10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)

  11) Restart your computer twice. 

   

  You may be asked to enter your COA Key and/or Activate. – if asked for the Key, use the one on your COA sticker on the machine’s case (you may need to activate by telephone).  

   

  Once complete, run another MGADiag report and post back with the results.     

  ---

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

  Sunday, December 2, 2012 10:43 AM

  Reply

  |

  Quote

  Moderator
• 

  

  0

  Sign in to vote

  Hi.

  I did the above and when prompted to enter in the product key, I entered the one on the sticker. I get a message telling me that the product key is invalid. However, when I enter in the product key I got from the Belarc audit (the product key I underlined below), it accepts the key to a certain point. It still gives me an error code, although this time the error code was 0xc004F063, rather than the above error code. I tried the above instructions twice and got the same result.
  

  Diagnostic Report (1.9.0019.0):
  -----------------------------------------
  WGA Data-->
  Validation Status: Invalid License
  Validation Code: 50
  
  Cached Validation Code: N/A, hr = 0xc004f012
  Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
  Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
  Windows Product ID: 89578-OEM-7332157-00061
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.0.6002.2.00010300.2.0.003
  ID: {539C52FD-C80B-4048-9C7C-62329BCF01D7}(3)
  Is Admin: No
  TestCab: 0x0
  WGA Version: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000000
  Build lab: 6002.vistasp2_gdr.120824-0336
  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: 109 N/A
  OGA Version: N/A, 0x80070002
  Signed By: N/A, hr = 0x80070002
  Office Diagnostics: B4D0AA8B-604-645_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\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>{539C52FD-C80B-4048-9C7C-62329BCF01D7}</UGUID><Version>1.9.0019.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-1906398355-2470999302-1086257551</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>Compaq Presario CQ50 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.07</Version><SMBIOSVersion major="2" minor="4"/><Date>20080626000000.000000+000</Date></BIOS><HWID>DB303507018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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-->
  Software licensing service version: 6.0.6002.18005
  Name: Windows(TM) Vista, HomePremium edition
  Description: Windows Operating System - Vista, OEM_SLP channel
  Activation ID: bffdc375-bbd5-499d-8ef1-4f37b61c895f
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 89578-00146-321-500061-02-1033-6002.0000-3372012
  Installation ID: 010830631513288636232186004544338725608766594273600812
  Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
  Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
  Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
  Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
  Partial Product Key: WQD8Q
  License Status: Notification
  Notification Reason: 0xC004F063.
  
  Windows Activation Technologies-->
  N/A
  
  HWID Data-->
  HWID Hash Current: OAAAAAEABAABAAEAAQACAAAAAwABAAEAJJT2/yaeILUe8paSVhD0RhSW8vSCMuC2jNzomKxWfig=
  
  OEM Activation 1.0 Data-->
  N/A
  
  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes
  Windows marker version: 0x20000
  OEMID and OEMTableID Consistent: yes
  BIOS Information:
    ACPI Table Name    OEMID Value    OEMTableID Value
    APIC            HPQOEM        SLIC-MPC
    FACP            HPQOEM        SLIC-MPC
    HPET            HPQOEM        SLIC-MPC
    BOOT            HPQOEM        SLIC-MPC
    MCFG            HPQOEM        SLIC-MPC
    SLIC            HPQOEM        SLIC-MPC
    SSDT            HPQOEM         SLIC-MP
  
  

  Sunday, December 2, 2012 6:28 PM

  Reply

  |

  Quote
• 

  

  0

  Sign in to vote

  You MUST use the Key from the COA sticker - assuming it's for Vista Home Premium.

  If you get an Invalid Key message, it's usually because you've miscopied it from the sticker -

   0xC004F050 usually means that you've misread a character - either C/G/6 or B/8 or Y/V are the most common.

   

  Note that the following characters cannot be used - A E I L N O S U Z 1 0 - so don't bother trying unless you like the noise it makes :)

  an O/0 is almost always a Q

  ---

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

  Sunday, December 2, 2012 8:26 PM

  Reply

  |

  Quote

  Moderator
• 

  

  0

  Sign in to vote

  Hi:

  For the life of me, I can't seem the get the code right. I've tried every variation reasonable, but it seems like 3 of the 5 groups have a character that seems hard to read, and when I try to enter any possible letter/number it can be, in conjunction with doing the same for other characters in the other groups, it still comes back invalid. I've used a magnifying lens and blacklight/negative to try to decipher the outline, but nothing still.
  

  Is there any other way I can resolve this issue? Would it be possible to attach an image of the 2-3 groups that are giving me trouble to get help trying to figure it out? Or is there another way to fix this?

  Thanks for your help!

  Kal

  Sunday, December 2, 2012 10:32 PM

  Reply

  |

  Quote
• 

  

  1

  Sign in to vote

  Your problem is that for some reason, the system is unable to properly read the SLIC table in the BIOS, which is required to be able to self-activate the OEM_SLP Key with which the computer came installed.

   

  The normal solution is to change the Key to the one on your COA sticker - but you say that you are unable to read the Key there.

   

  In such circumstances, the only things you can do are

   

  1) recreate the Licensing Store - in case it's a minor software problem causing the misread

  2) try updating the BIOS to the latest available Vista-compliant one, from the manufacturer's website

  3) Contact the manufacturer direct, and see if they can provide assistance to correct the SLIC table

  4) a reformat and reinstall using the manufacturer's recovery media

  5) purchase a new license for Windows (or a new computer)

     

  In your case, you've done #1 - #2 and #3 aren't relevant.

  This leaves you with #4 and #5

   

   

  There *may* be an alternative solution though, if you are patient and persistent.

  Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key is blocked (they should then ask for confirmation of your Product Key). Explain to them your problem, that you need to change the Key to the one on your sticker, but that the sticker is unreadable (could they please supply a replacement Key?). Hopefully they will ask for documentary proof of the sticker, in the form of an email with a picture of the affected sticker - and you can proceed from there.

  Sometimes it takes two or three calls before you get an operator who actually knows and uses this procedure - but I know that it can and does happen.

  ---

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

  • Proposed as answer by Noel D PatonEditor Saturday, December 8, 2012 8:20 AM

  Sunday, December 2, 2012 10:46 PM

  Reply

  |

  Quote

  Moderator
• 

  

  0

  Sign in to vote

  Thank you so much for your help. I tried step 2 to no avail (the last update was 2009, if that's relevant). Do you know how I can go about doing step 1? If that doesn't work, I'll be trying the other steps

  Thanks again for your help.

  Sunday, December 2, 2012 11:34 PM

  Reply

  |

  Quote
• 

  

  1

  Sign in to vote

  You've already tried step 1 - and it failed to resolve the problem

  Your only options are #4 and 5 - and trying operator assistance to acquire a new Key

  ---

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

  Tuesday, December 4, 2012 10:40 AM

  Reply

  |

  Quote

  Moderator