New
#11
Please follow the instructions - there is a LOT more data in the full report than is given in any of the tabs in the tool.
Post the report, otherwise all we're doing is guessing in a data-vacuum.
Please follow the instructions - there is a LOT more data in the full report than is given in any of the tabs in the tool.
Post the report, otherwise all we're doing is guessing in a data-vacuum.
Ok, thanks. Here's the mgadiag output. The sticker is not readable, but it's Win7 Home Premium. The machine is an Acer 722 11.6" netbook, manufactured in 2012. Bear in mind that this install has been validated via the coa key, which I was able to make out.
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-X6BFP-D3KR8-CCFGV
Windows Product Key Hash: McucydXC95LeQwImdod1BjNBiVE=
Windows Product ID: 00359-OEM-9821967-45939
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {22F0F767-32F8-4F57-9476-2F65D0DC90B1}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130828-1532
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)\Opera\Opera.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>{22F0F767-32F8-4F57-9476-2F65D0DC90B1}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-CCFGV</PKey><PID>00359-OEM-9821967-45939</PID><PIDType>8</PIDType><SID>S-1-5-21-3989258524-3741901635-3973668346</SID><SYSTEM><Manufacturer>Acer</Manufacturer><Model>AO722</Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V1.08</Version><SMBIOSVersion major="2" minor="7"/><Date>20111206000000.000000+000</Date></BIOS><HWID>D3DF0800018400F2</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><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</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, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00196-219-645939-02-1033-7601.0000-0432014
Installation ID: 012570224426856105457605883182814664905230338116561245
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: CCFGV
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 2/13/2014 1:42:58 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 2:12:2014 14:46
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: LgAAAAAAAgABAAEAAAACAAAAAgABAAEAJJTwu1T5wuSCmfALYj32fWC4ijZQXg==
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 ACRSYS ACRPRDCT
FACP ACRSYS ACRPRDCT
HPET ACRSYS ACRPRDCT
BOOT ACRSYS ACRPRDCT
MCFG ACRSYS ACRPRDCT
SLIC ACRSYS ACRPRDCT
SSDT AMD POWERNOW
SSDT AMD POWERNOW
The installed Key is from a COA sticker on a major manufacturer's machine.
This machine is an Acer AO722 built late 2011/early 2012 (BIOS date is 6 Dec 2011)
Assuming that the installed Key is the one from this machine's COA sticker (and not one from another machine), then the install is genuine and you should have no problems.
Assuming that the other machine also had Win7 Home Premium, AND was also an Acer, then the original installed Key would have worked, unless it had already been changed to the COA Key for that machine. This was one reason why I asked for the MGADiag (and why everyone else should have!).
Computers that come pre-installed with Windows from large manufacturers usually come with two Product Keys.
OEM SLP: This is the key that came in Windows (from the factory). It works by connecting to a BIOS flag (the SLIC table) found only on computers from that Manufacturer. It also checks for the existence of proper matching licenses in the OS itself. Once it sees both, it self-activates every time the machine is rebooted.
COA SLP: This is the key seen on the sticker located on the side, bottom or in the battery compartment of your machine. This key is for use if the OEM SLP self-activation stops working for whatever reason.
The OEM_SLP Key is valid on any similar machine from the same manufacturer - but how similar the machine needs to be depends on the manufacturer (I believe that some Dells will fail with inappropriate Recovery media/Key despite being outwardly the same, due to changes in the BIOS SLIC table and associated licenses in the media)
On the other hand, other manufacturers have either a limited or non-existent range of license/SLIC table variants.
Had you (been asked for and) posted the MGADiag report initially, we could have given definite (almost) opinions of the state of affairs at that point, and you may have been saved a lot of hassle.
As it is, we are still none the wiser about the initial status of the license..
All of which is irrelevant, now that you have the COA Key in place - make sure that you keep a good record of it in a safe place as it's the only copy in existence!.
Ok, thanks much Noel, and everyone. Yes, the coa is from this machine, so it should be solid.
The clone was from a very similar acer. I'm not sure if it was a coa or a slp key. I didn't think Win7 was able to validate across a manufacturer's line. XP, yes, but I thought Win7 bios tables were more specific than that (whether model-specific or unit-specific I don't know). I've even had factory restoration partitions fail to activate when run on other machines.
I find this quite confusing. Since there are some unknowns depending on the manufacturer, it seems that the next time a clone registers as valid, I should post the mgadiag and see if it's for real.
Mostly, except for Dell, so long as the COA sticker for the 'new' machine is for the same edition and version of Windows as the one on the source machine, then the transfer should be problem-free, hardware permitting.
Thanks much! I'll keep that in mind.