Answered by:
stuck in activation

Question
-
done the diagnostics here they are
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Status: Invalid License
Validation Code: 50
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-3RBY2-BGQ2R-DR9M6
Windows Product Key Hash: EYIpz/47G03lWRAOmk3kg+lR7Rc=
Windows Product ID: 89578-OEM-7332157-00141
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.0.6000.2.00010300.0.0.003
ID: {41D63495-054D-452E-919E-947F85168132}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows Vista (TM) Home Premium
Architecture: 0x00000000
Build lab: 6000.vista_gdr.100218-0019
TTS Error:
Validation Diagnostic:
Resolution Status: N/AVista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002Windows 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 = 0x80070002OGA 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 = 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>{41D63495-054D-452E-919E-947F85168132}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-DR9M6</PKey><PID>89578-OEM-7332157-00141</PID><PIDType>2</PIDType><SID>S-1-5-21-4132393068-255085999-2775772457</SID><SYSTEM><Manufacturer>VMware, Inc.</Manufacturer><Model>VMware Virtual Platform</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>6.00</Version><SMBIOSVersion major="2" minor="4"/><Date>20091231000000.000000+000</Date></BIOS><HWID>3A303507018400E8</HWID><UserLCID>0409</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/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.0.6000.16509
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-500141-02-1033-6000.0000-0172011
Installation ID: 001162944963399564738183645892567062468601601690938980
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57201
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57203
Use License URL: http://go.microsoft.com/fwlink/?LinkId=57205
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=57204
Partial Product Key: DR9M6
License Status: UnlicensedWindows Activation Technologies-->
N/AHWID Data-->
HWID Hash Current: MAAAAAEAAgABAAEAAQABAAAAAgABAAEAnJ/y6AwSDFzmt0R8/BTy9PGe972sVuIQOEM Activation 1.0 Data-->
N/AOEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC PTLTD APIC
FACP INTEL 440BX
SRAT VMWARE MEMPLUG
BOOT PTLTD $SBFTBL$
MCFG PTLTD $PCITBL$Monday, January 17, 2011 3:12 PM
Answers
-
"liammmmmm" wrote in message news:04cd1f09-aed7-4ae7-9441-04237013e598...
thanks for the reply but i cant do the steps as i cant log into vista (reduced functionality)
also i am running vista on VMware fusion on mac so i think thats why you cant find the special instructions
Your installation is not valid in VMWare - OEM_SLP licenses are not sold separately, but only pre-installed on OEM machines.You need to purchase a FULL license (either OEM or Retail) for whichever version of Windows you want.I do NOT recommend OEM versions, as they may be invalidated by an update to the VM environment, or if you decide to change from using VMWare to Parallels or BootCamp (or another VM solution).
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by liammmmmm Tuesday, January 18, 2011 11:14 AM
Tuesday, January 18, 2011 10:21 AMModerator
All replies
-
Hello liammmmmm,
Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:
A) OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) 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 (sush as if the OEM SLP key stops self-activating for whatever reason). 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 Windows 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.
Thank you,
Darin MS- Marked as answer by Darin Smith MS Tuesday, January 18, 2011 12:30 AM
- Unmarked as answer by Darin Smith MS Thursday, January 20, 2011 12:39 AM
Tuesday, January 18, 2011 12:30 AM -
"Darin Smith MS" wrote in message news:e32c3f74-5a60-488e-98c7-483b82e4af4a...
Hello liammmmmm,
Darin MS
DarinThe OP is attempting to use an OEM_SLP activation within a VM?
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothTuesday, January 18, 2011 9:02 AMModerator -
thanks for the reply but i cant do the steps as i cant log into vista (reduced functionality)
also i am running vista on VMware fusion on mac so i think thats why you cant find the special instructions
Tuesday, January 18, 2011 9:11 AM -
"liammmmmm" wrote in message news:04cd1f09-aed7-4ae7-9441-04237013e598...
thanks for the reply but i cant do the steps as i cant log into vista (reduced functionality)
also i am running vista on VMware fusion on mac so i think thats why you cant find the special instructions
Your installation is not valid in VMWare - OEM_SLP licenses are not sold separately, but only pre-installed on OEM machines.You need to purchase a FULL license (either OEM or Retail) for whichever version of Windows you want.I do NOT recommend OEM versions, as they may be invalidated by an update to the VM environment, or if you decide to change from using VMWare to Parallels or BootCamp (or another VM solution).
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth- Marked as answer by liammmmmm Tuesday, January 18, 2011 11:14 AM
Tuesday, January 18, 2011 10:21 AMModerator