Answered by:
You may be a victim of software counterfieting..

Question
-
I am being told that my copy of Windows XP Pro is not valid in my region when it is trying to be validated.
The COA sticker says OEM Software and there is no company name on it.
The WGA tells me that the COA on the sticker is different from the one on my PC but I know I entered the COA correctly when I installed it and it has been activated.
Whats going on?Sunday, June 28, 2009 6:50 PM
Answers
-
Hi brooklyn_uk,
If the Product Key being used is different then the one on your COA Sticker, then your first step in resolution is to reinstall using the proper key.
One of the most common causes of this is called the Repair Store scenerio. This is where a user take a computer to a repair shop (or has a friend repair their computer) and the repair tech needed to reinstall XP and instead of using the COA key they just downloaded a (non-genuine) key off the internet.
I don't know if this is how your XP got a bad key, but regardless of how it occured, the resolution is to get that good key back in XP. Unfortunatly the only way to replace in a COA key is to reinstall using that key. (there is a tool called the Product Key Update tool, but it seems to only work for retail keys).
Thank you,
Darin MS- Marked as answer by Darin Smith MS Wednesday, July 1, 2009 5:18 PM
Wednesday, July 1, 2009 5:18 PM -
Hello Brooklyn_uk,
The fact that the hologram is embedded in the CD is a plus, but looking at the last line of the setupp.ini file makes me think that your original XP was not genuine, either.
The PID=value for a genuine OEM CD will always end with the letters OEM. A value ending in "270" or any number 640 thru 649 indicates that the bits on the CD are volume licensing bits and not OEM or retail bits.
Please try this:
1. Use the Product Key Updater utility to change your PK from the "2487J-KWKMF-RPWBY" PK to the PK on the CoA ending in "F3BHT".
If the PK updater cannot make the change, change the PK following the Method 1 instructions in this MS KB article: http://support.microsoft.com/default.aspx/kb/328874
2. Once the PK has been changed to the F3BHT key, restart the computer and then rerun the mgadiag utility.
I have a hunch that the PK on the CoA is not genuine either, and after changing the PK and rerunning the mgadiag, if I am right the report will come up with Invalid PK.
If I am right and that happens, you should be able to send in you materials to see if you qualify for a free replacement from Microsoft, which can happen if MS deems the materials "high-quality" counterfeits.
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp- Marked as answer by Darin Smith MS Thursday, July 2, 2009 4:44 PM
Wednesday, July 1, 2009 6:25 PM -
Thanks all for your help.
I have changed the key to the one on the COA and it is now working. Cheers! :o)
- Marked as answer by brooklyn_uk Thursday, July 2, 2009 1:40 PM
Thursday, July 2, 2009 1:40 PM
All replies
-
I'm having this same problem. Any help that I can get will be great. How did you find out that your copy wasn't registered? I was trying to install DirectX for a computer game, restarted the system and poof it said that it suddenly wasn't valid.Sunday, June 28, 2009 9:57 PM
-
Hello brooklyn_uk,
In order to receive the best support, we request all users initially download and run the Genuine Diagnostics tool (MGADiag.exe) at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue", click the “Windows” tab, and click the "Copy" button then “Paste” the report into a reply message in this thread.
VintageRose713: Please create your own thread and include a Diagnostic Report.
Thank you,
Darin MSMonday, June 29, 2009 8:35 PM -
Here is the report.
Diagnostic Report (1.9.0006.1):
-----------------------------------------
WGA Data-->
Validation Status: Geographically blocked PID
Validation Code: 13
Online Validation Code: N/A
Cached Validation Code: N/A
Windows Product Key: *****-*****-2487J-KWKMF-RPWBY
Windows Product Key Hash: A6tqZpYlrSkfmUWcaNDswSdRpOo=
Windows Product ID: 55274-640-8834005-23771
Windows Product ID Type: 1
Windows License Type: Volume
Windows OS version: 5.1.2600.2.00010100.3.0.pro
ID: {F1E30001-A60D-44C0-8472-66B08C4A0B2C}(3)
Is Admin: Yes
TestCab: 0x0
WGA Version: Registered, 1.9.40.0
Signed By: Microsoft
Product Name: N/A
Architecture: N/A
Build lab: N/A
TTS Error: N/A
Validation Diagnostic: 025D1FF3-230-1
Resolution Status: N/AWgaER Data-->
ThreatID(s): N/A
Version: N/AWGA Notifications Data-->
Cached Result: 13
File Exists: Yes
Version: 1.9.40.0
WgaTray.exe Signed By: Microsoft
WgaLogon.dll Signed By: MicrosoftOGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
WGATray.exe Signed By: Microsoft
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: B4D0AA8B-543-80070002_025D1FF3-230-1Browser 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>{F1E30001-A60D-44C0-8472-66B08C4A0B2C}</UGUID><Version>1.9.0006.1</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-RPWBY</PKey><PID>55274-640-8834005-23771</PID><PIDType>1</PIDType><SID>S-1-5-21-515967899-115176313-839522115</SID><SYSTEM><Manufacturer>.</Manufacturer><Model>.</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="5"/><Date>20080219000000.000000+000</Date></BIOS><HWID>6A8138F701846079</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Licensing Data-->
N/AHWID Data-->
N/AOEM Activation 1.0 Data-->
BIOS string matches: N/A
Marker string from BIOS: N/A
Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005OEM Activation 2.0 Data-->
N/ATuesday, June 30, 2009 1:03 PM -
Hello brooklyn_uk,
Right now, your computer has a Volume Licensing edition of XP Pro installed (Line 10), and that installation was done with a now-geographically blocked Volume Licensing Key (VLK) (Line 2). VLKs are blocked by Microsoft at the request of the original key holder for such reasons as the key was lost, stolen, compromised, misused, or expired. Also, Microsoft may have blocked the key if it notices a pattern of misuse, i.e., more installations of XP using that key than authorized.
A geographically blocked key is blocked when it is detected in use outside of the worldwide geographic area(s) covered by its Volume Licensing Agreement. The particular Product Key you are using, is a widely used pirated key that comes up as very popular if you do a search for it on the internet.
As a rule, VL editions of XP should not be sold to individual consumers. Businesses, schools and governments normally use VL editions for flexibility in installing many computers. Additionally, VL editions are Upgrade licenses ONLY, and therefore cannot be used as the primary or base license for a computer. If you are an individual consumer using a privately owned computer, you certainly should not be using a Volume License.
This is why you were seeing the "software counterfeiting" messages on your computer, because the current installation of XP is an unauthorized installation. I would recommend contacting the person or company that sold you the software and demand the Genuine Microisoft Software that you paid for (or at the very least, a refund). I also recommend that you to file a piracy report by visiting http://www.microsoft.com/piracy .
Thank you,
Darin SM- Marked as answer by Darin Smith MS Tuesday, June 30, 2009 8:45 PM
- Unmarked as answer by brooklyn_uk Wednesday, July 1, 2009 10:16 AM
Tuesday, June 30, 2009 8:45 PM -
Hello brooklyn_uk,
Is your CoA for XP Home, Pro, or Media Center?
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxpWednesday, July 1, 2009 4:25 AM -
Hi Dan,
It's Pro, There is no computer makers name on it like Dell or Time etc. Just says Windows XP Professional, OEM software.
Darin, The shop I bought it from no longer exists so I cant exchange it or get a refund. So what now?
Wednesday, July 1, 2009 10:15 AM -
if i put up my Diagnostic reprt up would you take a look at mine too, as im sick of the black screen and no updates, i dont want to buy a new one cos it costs more than my comp is actually worth, i only really use it for my college work, i thought i picked up a bargain when i bought it, only to find out that my windows was a fake!Wednesday, July 1, 2009 11:16 AM
-
Hello brooklyn_uk,
Sorry for the repeated question about the CoA, as you had already posted that info in your first post.
OK, let's examine your materials.
Please visually check your CoA and compare the Product Key (PK) on the CoA with the last three sets shown by the mgadiag report, 2487J-KWKMF-RPWBY. Is your CoA showing the same or different last three? Note: DO NOT post the full PK printed on your CoA.
Did you receive a genuine hologrammed Microsoft CD with your purchase? If so, please closely examine the CD that came with your purchase:
1. Does the CD read "For distribution with a new PC only" in the upper left? Is the hologram of the CD embedded within the plastic of the CD, or is it a very thin label affixed to the top surface of the CD?
2. Pop the CD into a computer and navigate to the setupp.ini file within the \i386 folder. This is a small file with several lines of text and numbers in two sections. Please post the text of the second section of the file.
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxpWednesday, July 1, 2009 2:40 PM -
Hi insaniac,
Please start your own thread as described in the Forum Announcements.
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxpWednesday, July 1, 2009 2:40 PM -
Hi Dan,
Ok, the COA on the sticker does NOT match the one shown by the MGADIAG report as the last 5 letters/number on my sticker are: F3BHT
The CD has the hologram embedded in the plastic and is not a label and it says "For distribution with a new PC only" at the top left of it.The setupp.ini file text is as follows:
[Pid]
ExtraData=796674736977656D7A622E385892A4
Pid=55274270
Hope this helps.Wednesday, July 1, 2009 4:36 PM -
Hi brooklyn_uk,
If the Product Key being used is different then the one on your COA Sticker, then your first step in resolution is to reinstall using the proper key.
One of the most common causes of this is called the Repair Store scenerio. This is where a user take a computer to a repair shop (or has a friend repair their computer) and the repair tech needed to reinstall XP and instead of using the COA key they just downloaded a (non-genuine) key off the internet.
I don't know if this is how your XP got a bad key, but regardless of how it occured, the resolution is to get that good key back in XP. Unfortunatly the only way to replace in a COA key is to reinstall using that key. (there is a tool called the Product Key Update tool, but it seems to only work for retail keys).
Thank you,
Darin MS- Marked as answer by Darin Smith MS Wednesday, July 1, 2009 5:18 PM
Wednesday, July 1, 2009 5:18 PM -
Hello Brooklyn_uk,
The fact that the hologram is embedded in the CD is a plus, but looking at the last line of the setupp.ini file makes me think that your original XP was not genuine, either.
The PID=value for a genuine OEM CD will always end with the letters OEM. A value ending in "270" or any number 640 thru 649 indicates that the bits on the CD are volume licensing bits and not OEM or retail bits.
Please try this:
1. Use the Product Key Updater utility to change your PK from the "2487J-KWKMF-RPWBY" PK to the PK on the CoA ending in "F3BHT".
If the PK updater cannot make the change, change the PK following the Method 1 instructions in this MS KB article: http://support.microsoft.com/default.aspx/kb/328874
2. Once the PK has been changed to the F3BHT key, restart the computer and then rerun the mgadiag utility.
I have a hunch that the PK on the CoA is not genuine either, and after changing the PK and rerunning the mgadiag, if I am right the report will come up with Invalid PK.
If I am right and that happens, you should be able to send in you materials to see if you qualify for a free replacement from Microsoft, which can happen if MS deems the materials "high-quality" counterfeits.
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp- Marked as answer by Darin Smith MS Thursday, July 2, 2009 4:44 PM
Wednesday, July 1, 2009 6:25 PM -
Thanks all for your help.
I have changed the key to the one on the COA and it is now working. Cheers! :o)
- Marked as answer by brooklyn_uk Thursday, July 2, 2009 1:40 PM
Thursday, July 2, 2009 1:40 PM -
Hello brooklyn_uk,
Could you post a fresh mgadiag report? Thanks!
Also, how did you change the key? Did you use the method in the MS KB or did you use the Product Key Updater utility?
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxpFriday, July 3, 2009 7:04 AM -
I got the same thing popped up this morning, unreal - everything is legit, activd online twice, did the phone thing too.... nothing works - aero is disabled and i can't set any theme.... not only that but after running xp for 4+ years w/o a BSOD I have been getting Vista BSOD's 2-3 times a week since I finally installed it 2 months ago. This is really frustrating to say the least.Here's my diag info, any help would be appreciated.Diagnostic Report (1.9.0006.1):-----------------------------------------WGA Data-->Validation Status: GenuineValidation Code: 0Online Validation Code: 0x0Cached Validation Code: 0x0Windows Product Key: *****-*****-GHXYJ-9PXXK-D9Y9BWindows Product Key Hash: ehB+jVEmrIKDkCA6iBnA4dQjLc4=Windows Product ID: 89580-447-3992982-71190Windows Product ID Type: 5Windows License Type: RetailWindows OS version: 6.0.6002.2.00010100.2.0.001ID: {AEDA349C-07E7-4985-9626-F828E4B72D1F}(1)Is Admin: YesTestCab: 0x0WGA Version: Registered, 1.9.9.1Signed By: MicrosoftProduct Name: Windows Vista (TM) UltimateArchitecture: 0x00000000Build lab: 6002.lh_sp2rtm.090410-1830TTS Error:Validation Diagnostic:Resolution Status: N/AWgaER Data-->ThreatID(s): N/A, hr = 0x80070002Version: 6.0.6001.18152WGA Notifications Data-->Cached Result: N/A, hr = 0x80070002File Exists: NoVersion: N/A, hr = 0x80070002WgaTray.exe Signed By: N/A, hr = 0x80070002WgaLogon.dll Signed By: N/A, hr = 0x80070002OGA Notifications Data-->Cached Result: N/A, hr = 0x80070002Version: N/A, hr = 0x80070002WGATray.exe Signed By: N/A, hr = 0x80070002OGAAddin.dll Signed By: N/A, hr = 0x80070002OGA Data-->Office Status: 109 N/AOGA Version: N/A, 0x80070002Signed By: N/A, hr = 0x80070002Office 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/AUser Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)Default Browser: C:\Users\Swiss\AppData\Local\Google\Chrome\Application\chrome.exeDownload signed ActiveX controls: PromptDownload unsigned ActiveX controls: DisabledRun ActiveX controls and plug-ins: AllowedInitialize and script ActiveX controls not marked as safe: DisabledAllow scripting of Internet Explorer Webbrowser control: DisabledActive scripting: AllowedScript ActiveX controls marked as safe for scripting: AllowedFile Scan Data-->Other data-->Office Details: <GenuineResults><MachineData><UGUID>{AEDA349C-07E7-4985-9626-F828E4B72D1F}</UGUID><Version>1.9.0006.1</Version><OS>6.0.6002.2.00010100.2.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-D9Y9B</PKey><PID>89580-447-3992982-71190</PID><PIDType>5</PIDType><SID>S-1-5-21-77591784-3493532525-1299214947</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>ASUS M2N32-SLI DELUXE ACPI BIOS Revision 2205</Version><SMBIOSVersion major="2" minor="4"/><Date>20090302000000.000000+000</Date></BIOS><HWID>AD323507018400FA</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/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Spsys.log Content: 0x80070002Licensing Data-->Software licensing service version: 6.0.6002.18005Name: Windows(TM) Vista, Ultimate editionDescription: Windows Operating System - Vista, RETAIL channelActivation ID: 30fab9cc-8614-4339-989f-7ce61fb7a5c4Application ID: 55c92734-d682-4d71-983e-d6ec3f16059fExtended PID: 89580-00142-447-399298-00-1033-6002.0000-1842009Installation ID: 012110483174569341488755060053530956187244944380456422Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475Partial Product Key: D9Y9BLicense Status: LicensedHWID Data-->HWID Hash Current: OgAAAAMAAwABAAEAAwABAAAAAgABAAEAeqiWsm7FkXv6aKw73M2SAB62POCN75r18vRiG67drFaOLg==OEM Activation 1.0 Data-->N/AOEM Activation 2.0 Data-->BIOS valid for OA 2.0: yes, but no SLIC tableWindows marker version: N/AOEMID and OEMTableID Consistent: N/ABIOS Information:ACPI Table Name OEMID Value OEMTableID ValueAPIC Nvidia ASUSACPIFACP Nvidia ASUSACPIHPET Nvidia ASUSACPIMCFG Nvidia ASUSACPISSDT PTLTD POWERNOWFriday, July 3, 2009 6:10 PM
-
Hello Swiss Cheese,
Please post to the Vista forum--this is the XP forum.
For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxpFriday, July 3, 2009 6:17 PM