Answered by:
I don't have Windows Genuine, Help! What Now?

Question
-
So I had Windows Vista Home Premium installed on my computer from the place where I bought it (Office Depot) and recently my computer got a bad virus to I called a professional business to get it fixed. Since Windows came installed I didn't' have the original installation disk so they guy who fixed my computer said he would have to take it back to his office where he had a Windows instillation disk that he could install. I got my computer back and everything looked fine, I noticed no differences in the Windows version I had before and the one I have now. About 2 weeks have gone by and suddenly out of nowhere these messages are popping up telling me my product key is not valid, I may be a victim of Windows counterfeiting, ect. When I follow the step provided by the pop-ups to get this whole thing sorted out I never get anywhere. I have tried to validate if I truly have a counterfeit version of Windows through the Windows Genuine website but it always says that it can't determine if it is genuine or not. What should I do? Any advice is greatly appreciated as I don't know where to turn.Thursday, March 12, 2009 9:59 PM
Answers
-
Hi again k_laneaux,
Computers, which are built by large manufactures that come with Vista Pre-Installed, come with two (2) Product Keys:
A) OEM SLP: This key comes pre-installed in Vista, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key (at the factory) Vista looks at the motherboard and sees the special instructions 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. 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 Vista is using an OEM SLP key, but (for whatever reason) cannot see the special instructions in the computer’s motherboard and is unable to Self-Activate.
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.
Alternate steps to change the product key
1) Click the Start button
2) Type: slui.exe 3 and hit the Enter key
3) Type in the Product key from the sticker on your computer
4) Click the Next button.
5) You will be asked if want to Activate, click ok
6) It will attempt to Activate by the internet and will return an Invalid Key error (this is ok, continue to step 7)
7) Click the Start button
8) Type: slui.exe 4 and hit the Enter key
9) Select your location in the drop down menu and click the Next button
10) The next screen provides the number to call to Activate by Phone
NOTE: when you call that number, you will first hear an Automated Voice. If the Automated Voice gives you an option to talk to a Live Activation Rep, select that option. If not, do not enter any numbers. This should force the Automated Voice to transfer you to a Live Activation Rep. Trying to Activate thru the Automated Voice will not work, in your case, only thru the Live Activation Rep will your Activation be successful.
Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.- Marked as answer by Darin Smith MS Friday, March 13, 2009 12:28 AM
Friday, March 13, 2009 12:09 AM
All replies
-
I have the same problem. Seems like microsoft have really cocked up. I know at least 15 people that I work with who have who have had the same problem since they installed an update that was put out some time this week.Thursday, March 12, 2009 10:26 PM
-
Drivesmooth said:
I have the same problem. Seems like microsoft have really cocked up. I know at least 15 people that I work with who have who have had the same problem since they installed an update that was put out some time this week.
Wow, really? Alright, that makes me feel better. I have had this terrible run at bad luck lately so at least I know it isn't just me. Any clue on what to do or where to go from here?Thursday, March 12, 2009 10:49 PM -
Haven't got a clue :( my sister's just rang me saying she's having the same problem with hers! 3 updates released sometime this week are causing it. Her one had a cycle of installing updates, then turn it on again and those 3 updates are still trying to install and that cycle. I had that same cycle until it's finally decided to pack up. She managed to fix it by using system restore through safe mode on bootup, to before the terrible update installed itself, only restore checkpoint i have however is from when the update had finished installing, no previous, so I'm stuck.Thursday, March 12, 2009 11:09 PM
-
Hi k_laneaux, and Drivesmooth
No, they are not the same issue.
From k_laneaux's post, it sounds like he needs to change his product key to the key on the COA sticker on the side of bottom of his computer.
From Drivesmooth's thread, it sounds like a Mod_auth issue (nothing to do with the product key)
Unfortunatly, I can not be sure of the exact problem/fix for either of your issues without seeing your respective Diagnostic Reports.
k_laneaux please post your report in this thread and Drivesmooth, post your in your own thread.
To generate a Diagnostic Report, download and run the Genuine Diagnostics tool at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue", click the Windows tab, click the "Copy" button, then paste the report into a response message in your respective threads.
Thanks,
Darin MS
Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.Thursday, March 12, 2009 11:35 PM -
Ok, here is my report. I have to leave to go to run a few errands, but I will be back in a few hours. Any help or anything you notice in the report, if you could tell me, would be greatly appreciated. I will try and be back asap. Thanks.
Diagnostic Report (1.9.0006.1):
-----------------------------------------
WGA Data-->
Validation Status: Invalid License
Validation Code: 50
Online Validation Code: 0xc004c533
Cached Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-F4GJK-KG77H-B9HD2
Windows Product Key Hash: iJAth4TbScMi8HdcPurlASXdEkw=
Windows Product ID: 89578-OEM-7332157-00204
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.0.6001.2.00010300.1.0.003
ID: {C262E77F-D5E6-4A25-9FDF-7E1B6CC05AA0}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.9.9.1
Signed By: Microsoft
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000000
Build lab: 6001.vistasp1_gdr.080917-1612
TTS Error:
Validation Diagnostic:
Resolution Status: N/AWgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: 6.0.6002.16398WGA 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 = 0x80070002OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGATray.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA 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-3Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 7.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: AllowedFile Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{C262E77F-D5E6-4A25-9FDF-7E1B6CC05AA0}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-B9HD2</PKey><PID>89578-OEM-7332157-00204</PID><PIDType>2</PIDType><SID>S-1-5-21-3565459510-2142673076-3969170815</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv9000 (GA355UA#ABA) </Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>F.3D </Version><SMBIOSVersion major="2" minor="4"/><Date>20071122000000.000000+000</Date></BIOS><HWID>7B313507018400EE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07: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.6001.18000
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-500204-02-1033-6000.0000-0482009
Installation ID: 004624617701096372494545930851358306426792966262085711
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: B9HD2
License Status: Notification
Notification Reason: 0xC004F032.HWID Data-->
HWID Hash Current: OgAAAAEABgABAAEAAQABAAAAAwABAAEAnJ8aRhTBWtlqWWIeCuXUVEgkonC83/L04gyCaNxTrFb6/A==OEM Activation 1.0 Data-->
N/AOEM 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 HP APIC
FACP HP MCP51M
HPET PTLTD HPETTBL
BOOT HP $SBFTBL$
MCFG HP MCFG
SSDT PTLTD POWERNOW
SLIC HPQOEM SLIC-MPC
Thursday, March 12, 2009 11:53 PM -
Hi again k_laneaux,
Computers, which are built by large manufactures that come with Vista Pre-Installed, come with two (2) Product Keys:
A) OEM SLP: This key comes pre-installed in Vista, when it comes from the Factory. This key is geared to work with the special instructions found only on that Manufacturer's computer hardware. So when Vista was installed using the OEM SLP key (at the factory) Vista looks at the motherboard and sees the special instructions 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. 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 Vista is using an OEM SLP key, but (for whatever reason) cannot see the special instructions in the computer’s motherboard and is unable to Self-Activate.
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.
Alternate steps to change the product key
1) Click the Start button
2) Type: slui.exe 3 and hit the Enter key
3) Type in the Product key from the sticker on your computer
4) Click the Next button.
5) You will be asked if want to Activate, click ok
6) It will attempt to Activate by the internet and will return an Invalid Key error (this is ok, continue to step 7)
7) Click the Start button
8) Type: slui.exe 4 and hit the Enter key
9) Select your location in the drop down menu and click the Next button
10) The next screen provides the number to call to Activate by Phone
NOTE: when you call that number, you will first hear an Automated Voice. If the Automated Voice gives you an option to talk to a Live Activation Rep, select that option. If not, do not enter any numbers. This should force the Automated Voice to transfer you to a Live Activation Rep. Trying to Activate thru the Automated Voice will not work, in your case, only thru the Live Activation Rep will your Activation be successful.
Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.- Marked as answer by Darin Smith MS Friday, March 13, 2009 12:28 AM
Friday, March 13, 2009 12:09 AM -
Hey, thank you for the information. I followed the steps shown to activiate my product key on the bottom of my computer and the process was successful with a message somewhere along the lines of "activation successful". But there is still a small message on the bottom right corner of my desktop that says "This copy of Windows is not genuine". So what is the deal? Anybody know? Do I have to restart my computer?Friday, March 13, 2009 9:30 PM
-
Hi k_laneaux,
Yes, that's my fault. In my resolution steps, I forgot to include the steps to reboot. It can sometimes take up to two reboots to get all of Vista's systems set back to a Genuine state.
Sorry about that, but I'm glad the issue is resolved,
Darin MS
Attention All Forum Users: Please Do Not post your issue in someone else's Thread...Create your own. If any post fixes your issue, please click the "Post was Helpful" button for that post. This will help us showcase the threads that best help our customers.Friday, March 13, 2009 11:03 PM