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

[Darryl Licht]

ToddB:

Just use DVD you created with iso from digital river and follow my link to clean install. Follow that tutorial and then try and activate with MS.

Do not use a registry cleaner, especially if intended for XP on Win7! Actually I dont advise using a registry cleaner at all, ever! Try the clean install with the MS verified valid key and report back to us...

The source of the installation is not the critical factor in ANY Windows instal - it's the source and validaity of the KEY.
Until we see the MGADiag report, we CANNOT offer any opinion as to the validity of this current installation.

UNTRUE if key was manipulated by original installer (eBay seller) with one of many registry hacks out there!

 

[NoelDP]

UNTRUE if key was manipulated by original installer with one of many registry hacks out there!

WTF?????
The MGADiag report can demonstrate something like 90% of the available hacks, to those with a little knowledge.

 

[NoelDP]

Folks-

Okay the Apps I was using to "clean" my machine are as follows"

Wise registry cleaner - Deep Clean (advanced)
Tune up utilities - One click maintenance and registry cleaner and reg defrag
Revo Uninstaller - basically all of theirr clean up utilities they provide besides the uninstall function.

I admit I get a little crazy with this stuff and used it all the time with my XP OS with no problems but I know I am dealing with a different one here.

Please tell me my stupidity is the problem here!

I can almost GUARANTEE that the major error shown in an MGADiag report will be 0x80070424 - service does not exist.

PLEASE!!!!!
Post the report so that we can checlk, and then post a fix!

 

[Darryl Licht]

UNTRUE if key was manipulated by original installer with one of many registry hacks out there!

WTF?????
The MGADiag report can demonstrate something like 90% of the available hacks, to those with a little knowledge.

The untrue portion is that the install doesnt matter, additionally his activated and ran fine with key until he used registry cleaner. Did you read entire thread?

 

[NoelDP]

UNTRUE if key was manipulated by original installer with one of many registry hacks out there!

WTF?????
The MGADiag report can demonstrate something like 90% of the available hacks, to those with a little knowledge.

The untrue portion is that the install doesnt matter, additionally his activated and ran fine with key until he used registry cleaner. Did you read entire thread?

YES I did - and until I see an MGADiag report, I can do nothing but reserve judgement.
I am now CERTAIN that the error that caused his problem is from using a 'registry cleaner' - WiseFixer is well-known for producing this problem.
What I do not knwo is whether the base Key is valid - and from the historey of the thread, it is potentially debatable.

 

[Darryl Licht]

WTH??? Now your going to agree with me? I said that about registry like 5-6 posts ago!

And OP said it validated with key, and was fine until he "cleaned" it with both Wisefixer and Tuneup Utilities.

And we are all here to help... so stop being so adversarial Mr.!!!

 

[ToddB]

Sorry Guys-

Had to step away for a moment. Please find below my report. Keep in mind however that this morning I did a system restore prior to my clean of last night.

Thanks again for your help!

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}(1)
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-3402011
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: 3
Trusted time: 12/8/2011 2:14:56 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

 

[Darryl Licht]

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]

Either you, or the ebay retailer, has used RemoveWAT to crack the activation. Again a full clean install with a legit activation should solve this, if in fact the key is valid!

 

[NoelDP]

Finally
Thanks.

SInce my integrity appears to have been called to account, I'll try and dissect the report.

1) Windows License Type: COA SLP
this inidcates that the machine is from a Direct OEM - but that the OEM_SLP Key has possibly failed for some reason ( such as reinstalling from a Retail disk)

2) the set of file mismatches -
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]
indicates that the WAT update has not been installed, and that the machine has never been through a Validation procedure.

3)What DOES surprise me is that there is NO INDICATION of any problem whatever of any problem with activation or validation.

I still have to ask what the COA sticker has to say about the licensed version of Windows on this machine - but the current indication is that the machine should be fine (presumably because you were sensible, and created a System Restore point prior to using the WiseFixer registry destroyer, and could therefore bring the machine back to a valid state.

 

[NoelDP]

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]

Either you, or the ebay retailer, has used RemoveWAT to crack the activation. Again a full clean install with a legit activation should solve this, if in fact the key is valid!

That is TOTAL RUBBISH.
This is a perfectly normal response in a machine which has not yet had the WAT Update installed, and not been through the Validation process.

 

[Darryl Licht]

ToddB:

Since I now know it was RemoveWAT... Here is how to fix:

Boot from your Windows 7 DVD and select "Repair your computer" and then select Command prompt.

From there use these commands:

bootsect.exe /nt60 SYS /force
bootrec.exe /fixmbr
bootrec.exe /fixboot
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec.exe /rebuildbcd

Although for a novice a clean install may be easier!

 

[Darryl Licht]

That is TOTAL RUBBISH.
This is a perfectly normal response in a machine which has not yet had the WAT Update installed, and not been through the Validation process.

REALLY?????????????????????????????????????????

When OP has said earlier that it activated and ran fine with coa key code, really??? Again if you want to support your statements, with actual facts, then by all means back em up!

 

[ToddB]

Guys I will try Darryls instructions above and report back. Thanks!

 

[Darryl Licht]

ToddB:

This may be easier:

MBR Regenerator - The Professional Windows Fix Tool

 

[ToddB]

So I just download and run?

 

[Darryl Licht]

Yes!

 

[NoelDP]

ToddB:

This may be easier:

MBR Regenerator - The Professional Windows Fix Tool

It might be easier - but it's a HACK which cannot e guranteed.

 

[Darryl Licht]

ToddB:

This may be easier:

MBR Regenerator - The Professional Windows Fix Tool

It might be easier - but it's a HACK which cannot e guranteed.

Ive used in past with no issues, it does what the commands I gave above do. Just easier for a novice than typing at the CLI!

ToddB, if you doubt the legitimacy of this app I suggest you look at the developers site here:

http://www.joshcellsoftwares.com/2011/07/mbr-regenerator-professional-activation.html

 

[NoelDP]

That is TOTAL RUBBISH.
This is a perfectly normal response in a machine which has not yet had the WAT Update installed, and not been through the Validation process.

REALLY?????????????????????????????????????????

When OP has said earlier that it activated and ran fine with coa key code, really??? Again if you want to support your statements, with actual facts, then by all means back em up!

YES!
You can acquire a Key from anywhere - it *may* work for a while, but unless it is truly genuine and unabused it *will* fail eventually.
One of the tests of Guinuine-ness, is whether the COA Key in the report matches the COA Key on the sticker on teh machine - if it doesn't, it raises very 0grave doubts about the Key in use, since the ONLY truly valid Key for an OEM_COA Key is that on the COA sticker.

....and to answer the direct question about the 0x80070003 errors, yes, it is PERFECTLY normal, since the WAT update is the first thing that install theese files (and the validation chekc does so as well) - and the error message it 'file not found'
please learn a little beofre you jump on a horse.

 

[Darryl Licht]

NOel-

Once again, the OP had activated and was "cleaning" offline when his warning occurred. It had to be caused not by a MS activation fail (how so if offline), but the "cleaner"... wouldnt you agree with that one single theory???