Solved Win 7 Prof not genuine and cannot enter genuine OEM product key

[ToddB]

Okay just ran the regenerator and have the following:

30 days to activate. activate windows now. (with a set of car keys)

then

A product ID and a link to change the product key.

SO should I just enter my product key at this point?

 

[NoelDP]

Registry 'Cleaners' should more properly be descibed as registry 'destroyers' - and WiseFixer is renowned for removing the registry keys relating to teh Software Protection Service in Win 7.
The fact that it does so may be because older versions are being used - but the fact remains that ALL registry 'cleaners' are dangerous in their effects on the system, since they cannot be aware of system updates etc. until well after teh fact - and running a cleaner designed for XP on a WIn 7 system is tantamoount to manslughter, if not murder.

The Software Protection service in Win 7 runs at all times (although it may be in 'sleep' mode most of the time' - other parts of the system check to see that it does so, and then scream blue murder if it isn't.

 

[Darryl Licht]

Okay just ran the regenerator and have the following:

30 days to activate. activate windows now. (with a set of car keys)

then

A product ID and a link to change the product key.

SO should I just enter my product key at this point?

Did you reboot after running, or???

 

[NoelDP]

Okay just ran the regenerator and have the following:

30 days to activate. activate windows now. (with a set of car keys)

then

A product ID and a link to change the product key.

SO should I just enter my product key at this point?

NO!!!
First tell use what the COA sticker on your machine states - we do not need to know the Key itself - just the Version and Edition of WIndows for which it's valid.

 

[ToddB]

Yes it rebooted after the regenerator ran.

 

[Darryl Licht]

Registry 'Cleaners' should more properly be descibed as registry 'destroyers' - and WiseFixer is renowned for removing the registry keys relating to teh Software Protection Service in Win 7.
The fact that it does so may be because older versions are being used - but the fact remains that ALL registry 'cleaners' are dangerous in their effects on the system, since they cannot be aware of system updates etc. until well after teh fact - and running a cleaner designed for XP on a WIn 7 system is tantamoount to manslughter, if not murder.

I agree!!! Especially considering I already said that (more or less) earlier above... Do you enjoy repeating me that much? LOL!:mad2:

 

[Darryl Licht]

Yes it rebooted after the regenerator ran.

Now make sure you are connected to Internet and yes, activate! <-- using the "valid" key per MS support! As validity may still be in question...

 

[NoelDP]

MS Support are only able to issue Retail keys - therefore the Key in the report is NOT one issued by MS Support.

 

[ToddB]

GOOD! (I think-I hope) It is showing as "Windows is Activated".

I have also produced a MiDiag report below for review:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-TTQMJ-B8YKD-WJK9W
Windows Product Key Hash: BSCKoqC/pSOt649oZ9n8lV4S1yQ=
Windows Product ID: 00371-OEM-9303974-25341
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {3E224A09-7487-4E7E-A37E-0F8A9F32C8A4}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.110622-1506
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\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>{3E224A09-7487-4E7E-A37E-0F8A9F32C8A4}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WJK9W</PKey><PID>00371-OEM-9303974-25341</PID><PIDType>8</PIDType><SID>S-1-5-21-2115973165-3535713010-224503217</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Precision M6300 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A13</Version><SMBIOSVersion major="2" minor="4"/><Date>20100104000000.000000+000</Date></BIOS><HWID>722B3107018400F8</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>DELL </OEMID><OEMTableID>M08 </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.1.7601.17514
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: da22eadd-46dc-4056-a287-f5041c852470
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00186-039-725341-02-1033-7601.0000-3422011
Installation ID: 016205460276816644702611690485856003645625755173940051
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: WJK9W
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 12/8/2011 3:38:01 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: NAAAAAEABQABAAEAAAABAAAAAgABAAEA6GGWEPh9RoP8kMaD1G1C/Mi2PrdCjlpg2P5Gyg==
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL M08
FACP DELL M08
HPET DELL M08
MCFG DELL M08
ASF! DELL M08
TCPA
SLIC DELL M08
SSDT PmRef CpuPm

 

[NoelDP]

You still haven't answered the question about what's on your COA sticker

That said, the report looks good, but you need to go to the Validation center to cleare the obvious remaining error message....
Cached Online Validation Code: N/A, hr = 0xc004f012
Once there - www.microsoft.com/genuine/validate
you should, if all's well, be offered MSE and IE9 (you don't need to take them)

If not, please post a new MGADiag report.

 

[ToddB]

That is what I got and I am sorry about the COA question. My COA sticker has:

Windows 7 Pro OA with a product key that is different from the one the ebay folks sent me via email. It is a thin label and per an earlier post someone said it was for a "newer" Dell machine than mine. Not knowing much about COA labels I get the impression it is for a newer dell than the one I have and heaven knows where it came from.

I ran one last report and it is below:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-TTQMJ-B8YKD-WJK9W
Windows Product Key Hash: BSCKoqC/pSOt649oZ9n8lV4S1yQ=
Windows Product ID: 00371-OEM-9303974-25341
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {3E224A09-7487-4E7E-A37E-0F8A9F32C8A4}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.110622-1506
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-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{3E224A09-7487-4E7E-A37E-0F8A9F32C8A4}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WJK9W</PKey><PID>00371-OEM-9303974-25341</PID><PIDType>8</PIDType><SID>S-1-5-21-2115973165-3535713010-224503217</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Precision M6300 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A13</Version><SMBIOSVersion major="2" minor="4"/><Date>20100104000000.000000+000</Date></BIOS><HWID>722B3107018400F8</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>DELL </OEMID><OEMTableID>M08 </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.1.7601.17514
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: da22eadd-46dc-4056-a287-f5041c852470
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00186-039-725341-02-1033-7601.0000-3422011
Installation ID: 016205460276816644702611690485856003645625755173940051
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: WJK9W
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 12/8/2011 3:58:37 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
 
HWID Data-->
HWID Hash Current: NAAAAAEABQABAAEAAAABAAAAAgABAAEA6GGWEPh9RoP8kMaD1G1C/Mi2PrdCjlpg2P5Gyg==
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x0
OEMID and OEMTableID Consistent: yes
BIOS Information: 
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL M08 
FACP DELL M08 
HPET DELL M08 
MCFG DELL M08 
ASF! DELL M08 
TCPA 
SLIC DELL M08 
SSDT PmRef CpuPm

 

[Darryl Licht]

You still haven't answered the question about what's on your COA sticker

That said, the report looks good, but you need to go to the Validation center to cleare the obvious remaining error message....
Cached Online Validation Code: N/A, hr = 0xc004f012
Once there - www.microsoft.com/genuine/validate
you should, if all's well, be offered MSE and IE9 (you don't need to take them)

If not, please post a new MGADiag report.

The OP answered that on or about page 3 of this thread... it claims to be a Dell OEM sticker.

Im very confused as to why now that system claims to be clean and activated that the file mismatch errors still show in MGADiag...

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]

ToddB - Run Windows updates several times back to back with reboots in between and let us know what happens. I willing to bet it errors out again on KB971033 update.

 

[NoelDP]

Those four mismatches are, as I've stated before, totally and absolutely normal for a system that has not had the WAT UPdate (KB971033) installed, and has not yet been through a validation process.

They are deliberately ignored for that reason - the update is NOT a required one, and can be uninstalled if the user wishes to do so.

 

[ToddB]

When I go to Windows update it indicates "No important updates available" and when I check my installed updates KB971033 indicates it installed successfully today.

 

[Darryl Licht]

Those four mismatches are, as I've stated before, totally and absolutely normal for a system that has not had the WAT UPdate (KB971033) installed, and has not yet been through a validation process.

They are deliberately ignored for that reason - the update is NOT a required one, and can be uninstalled if the user wishes to do so.

I can tell you that the RemoveWAT hack shows same 4! Well, according to the most recent report the OP posted, now they're gone!

Perhaps it took now! The problem is will it surface again?

ToddB... YOU DID REPORT THE EBAY SELLER TO MS, RIGHT?

 

[Darryl Licht]

When I go to Windows update it indicates "No important updates available" and when I check my installed updates KB971033 indicates it installed successfully today.

Click "Check for Updates" anyway, see if it grabs any.

 

[NoelDP]

Those four mismatches are, as I've stated before, totally and absolutely normal for a system that has not had the WAT UPdate (KB971033) installed, and has not yet been through a validation process.

They are deliberately ignored for that reason - the update is NOT a required one, and can be uninstalled if the user wishes to do so.

I can tell you that the RemoveWAT hack shows same 4! Well, according to the most recent report the OP posted, now they're gone!

Perhaps it took now! The problem is will it surface again?

ToddB... YOU DID REPORT THE EBAY SELLER TO MS, RIGHT?

RemoveWAT does NOT show the same errors - but it DOES show other ones which are characteristic.
Do some reasearch.

Second thoughts - I'll save you the trouble, since you seem to be so certain that you probably wouldn't bother.....
File Scan Data-->
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

Licensing Data-->
Input Error: Can not find script file "C:\Windows\system32\slmgr.vbs".

 

[ToddB]

Nope. It only offers me a Silverlight update which is optional. I told the ebay folks I was Going to report them to MS if they did not make it right with me. That is when I got the refund.

 

[NoelDP]

Nope. It only offers me a Silverlight update which is optional. I told the ebay folks I was Going to report them to MS if they did not make it right with me. That is when I got the refund.

In that case, I'd say you're good to go - so long as you NEVER use another registry cleaner !


I'm still confused about the COA sticker, though

 

[Darryl Licht]

RemoveWAT does NOT show the same errors - but it DOES show other ones which are characteristic.
Do some reasearch.

It sure as heck did the last time I encountered and fixed it!

Since you completely refuse to believe anything I say, perhaps you will believe a MS Forum, perhaps, just perhaps...

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]

However, if you look at the Diagnostic Report, it shows that the WAT update has not been installed or (more likely considering the other parts of the report) was removed at some point, possibly using the Remove WAT tool that is floating around the internet (that Remove WAT tool doesn't do anything good and will usually cause problems like this).

SOURCE: genuine error code 0x8007007e specific module could not be found...
2nd post down...

Or here:

the above file errors are typical of a system that has used RemoveWAT to circumvent the activation requirements.

Source: http://qa.social.microsoft.com/Foru...7/thread/7f3b1f8f-fc36-4949-80b2-6ec96c720069