Activating Windows 7 64bit on a Latitude E6510
-
Thursday, February 14, 2013 3:42 PM
I have a Dell Latitude E6510 laptop, on which I've recently installed Windows 7 64bit, replacing the previously installed Windows 7 32bit. Four weeks on, I'm trying to activate (using the original key) but receive the message code '0XC004E003 - The Software Licensing Service reported that license evaluation failed.'
If I try slui.exe 4, I receive the message, 'The windows 7 professional product key you typed is invalid for activation' along with three options (buy, type a new key, contact Microsoft).
This is the output from MGADiag. Can you help? - Ian
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
Windows Product ID: 00371-OEM-8992671-00524
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {1B1A1437-CD87-40CC-B7EC-81DF14F27999}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130104-1431
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 (x86)\Google\Chrome\Application\chrome.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>{1B1A1437-CD87-40CC-B7EC-81DF14F27999}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-733WD</PKey><PID>00371-OEM-8992671-00524</PID><PIDType>2</PIDType><SID>S-1-5-21-337898126-1566272450-2129270082</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6510</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A13</Version><SMBIOSVersion major="2" minor="6"/><Date>20120730000000.000000+000</Date></BIOS><HWID>0AA33207018400FC</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><OEMID>DELL </OEMID><OEMTableID>E2 </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_SLP channel
Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00178-926-700524-02-2057-7601.0000-0452013
Installation ID: 010185069770583521066522669641557515496113714182915670
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: 733WD
License Status: Initial grace period
Time remaining: 4200 minute(s) (2 day(s))
Remaining Windows rearm count: 3
Trusted time: 14/02/2013 15:19:34
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: MAAAAAEAAQABAAEAAQABAAAAAwABAAEAln1KaFGAgAu8xMB80nmkvB3B4E96sVxd
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL E2
FACP DELL E2
HPET DELL E2
BOOT DELL E2
MCFG A M I GMCH945.
TCPA
SLIC DELL E2
SSDT PmRef CpuPm
All Replies
-
Thursday, February 14, 2013 5:07 PM
You have to contact the Microsoft Activation via telephone and explain the situation.
See information in thread @ http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/windows-7-activation-error-code-0xc004e003/0e20e661-9d99-4321-863f-4f06262f6859
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
-
Thursday, February 14, 2013 5:25 PM
Thanks, Rick,
As stated above, if I run slui.exe 4 I don't get the phone activation option. As a result, I don't get the installation id numbers that the phone activation process requires. I tried contacting the relevant number anyway (found through a web search) and navigated through to an assistant who wouldn't help me without the installation id.
Any further thoughts?
-
Thursday, February 14, 2013 7:44 PM
Try the following found in a thread @ http://social.microsoft.com/Forums/en-US/genuinevista/thread/8d9ebba1-f4bb-4aad-a048-13b6dc37e083/ I know it is originally for Vista, but it's worth a try.
When you use the Change Product Key option, it should offer alternative ways to activate – one of them being Telephone Activation.
If you don’t get that far then the problem is with the Key you are entering (it has an incorrect character or two) The error message you are seeing(0xC004E003) will ALWAYS appear when you have an OEM_SLP Key – because it’s blocked from activation by the MS servers, as it’s supposed to self-activate using the BIOS SLIC table and internal certificates. Since you say that you’ve already attempted to change the Key, but the Key in use is still the OEM_SLP Key, this would indicate that either something is preventing the Key change, or you are entering the wrong Key.Try this...
Please try the below steps to recreate the Licensing Store files. This may resolve the issue.
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 - or it may say that it's not running - this is OK)
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)
Reboot TWICE
If necessary, then you may be required to enter the Product Key and/or Activate.
Reboot
Once complete, please post back with a new MGADiag report
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
-
Thursday, February 14, 2013 11:42 PM
Maybe I am misunderstanding the question but, can you confirm a something for me?
Are you trying to activate Windows 7 x64 Professional with an OEM Windows 7 x86 Professional key?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” How to ask a question that is fixable.
-
Friday, February 15, 2013 10:49 AMYes, I am.
-
Friday, February 15, 2013 10:57 AM
Rick,
I ran the procedure as you suggest (for Windows 7, substitute SoftwareProtectionPlatform for SoftwareLicensing and substitute sppscv for slsvc).
Rebooted twice - there's no evident change in system behaviour. If I use slui.exe I get the same options as before.
Here's the new MGADiag.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-M3DJT-4J3WC-733WD
Windows Product Key Hash: xo+ajVSpae7/4VoZjS7m6JL0f3A=
Windows Product ID: 00371-OEM-8992671-00524
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {1B1A1437-CD87-40CC-B7EC-81DF14F27999}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130104-1431
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 (x86)\Google\Chrome\Application\chrome.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>{1B1A1437-CD87-40CC-B7EC-81DF14F27999}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-733WD</PKey><PID>00371-OEM-8992671-00524</PID><PIDType>2</PIDType><SID>S-1-5-21-337898126-1566272450-2129270082</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude E6510</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A13</Version><SMBIOSVersion major="2" minor="6"/><Date>20120730000000.000000+000</Date></BIOS><HWID>0AA33207018400FC</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><OEMID>DELL </OEMID><OEMTableID>E2 </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_SLP channel
Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00178-926-700524-02-2057-7601.0000-0462013
Installation ID: 010185069770583521066522669641557515496113714182915670
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: 733WD
License Status: Initial grace period
Time remaining: 3060 minute(s) (2 day(s))
Remaining Windows rearm count: 3
Trusted time: 15/02/2013 10:27:33
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 2:14:2013 17:32
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MAAAAAEAAQABAAEAAQABAAAAAwABAAEAln1KaFGAgAu8xMB80nmkvB3B4E96sVxd
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL E2
FACP DELL E2
HPET DELL E2
BOOT DELL E2
MCFG A M I GMCH945.
TCPA
SLIC DELL E2
SSDT PmRef CpuPm
-
Friday, February 15, 2013 11:17 AM
Perhaps you might find an answer at one of the links from the link:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked As Answer by Ian Popplestone Friday, February 15, 2013 11:36 AM
-
Friday, February 15, 2013 11:54 AM
Thanks, Rick,
These links indirectly resolved the issue in pointing out to me that I might find the COA in the battery compartment! Any trace had long ago been erased from the underside of the laptop, where I'd expected to find it.
The product key that I'd been running under with Windows 7 32bit, which I was trying to reuse, was causing the problems. The product key finally retrieved from the COA worked fine.
Thanks for your help - Ian

