Solved Interesting activation situtation

[BReeves]

Hi folks,

Not sure if this is a question or not but kinda wondering why it happened. I bought two refurbished HP computers with Windows 7 64bit. Both computers came with a Windows 7 Pro CD and COA stickers. I needed to downgrade both to 32bit because of a couple hardware drivers that are not available in 64bit.

I did a fresh installation on one and got everything setup and installed I needed. Used the product key off the COA sticker on the case and it activated just fine. I then made a clone of the hard drive for the 2nd computer figuring I would need to change the product key to activate the windows 7 installation on the 2nd computer.

Fired up the second computer and as expected it wasn't activated. When I tried to enter the product key off the COA sticker on the case it came back as an invalid key. I double checked everything, the COA stickers says Windows 7 PRO just like the one on the first computer. Even tried entering it several times checking to be sure it was correct.

At first I thought it may be because I wasn't connected to the internet so I set up the network, connected to the internet and tried again with the same results. Finally out of frustration I just hit the Activate this computer button. To my surprise it activated with the same product key as the other computer.

So now I have two activated Windows 7 installations with the same product key. Kinda wondering why the 2nd product key wouldn't work and why it activated with the same key as the first computer. Both computers are now on the network with internet and so far no messages from Microsoft telling me I might have an illegal copy of Windows. Weird.....

 

[AddRAM]

Possibly because it`s a clone and not a clean install.

Give it some time, you might still get a non genuine pop up.

Still odd it didn`t accept the other key.

 

[ThrashZone]

Hi and welcome to SevenForums,
More interesting is the driver you felt was better to move to 32 bit :/
What driver ?

 

[BReeves]

Hi and welcome to SevenForums,
More interesting is the driver you felt was better to move to 32 bit :/
What driver ?

Mitsubishi direct USB printer port driver from the Mitsubishi SDK and Canon EOS SDK. Canon may come out with a 64bit SDK but as it stands right now the beta 64bit is not as complete as the 32bit version.

I don't need to be able to access gigabytes of ram and a 64bit computer buys me nothing but headaches. Truth be told except for maybe gamers most users and software don't/can't take advantage of a 64bit OS.

 

[ThrashZone]

Hi,
Okay thanks for the update on which driver you had issues with
As long as 3gb's of rams is okay for your usage is what counts,
Keep the startup list short and a ssd will help 32 bit as well as 64 bit if you do end up with a slowdown
Cheers.

 

[alphanumeric]

Possibly because it`s a clone and not a clean install.

Give it some time, you might still get a non genuine pop up.

Still odd it didn`t accept the other key.

To all of the above comments. If they are identical hardware, so far the activation server thinks its just the one PC activating. Sooner or latter one or the other will likely fail activation.

Usually when a key is rejected when entering it into Windows, it's been miss typed. A C instead of a G, I instead of a 1, O for an 0 or vice versa.

 

[NoelDP]

PLease post a MGADiag report of the second computer - then we can actually see what the situation really is.

 

[BReeves]

Sorry folks, just found the thread again, for some reason it quit sending me emails on posts and didn't think it had any additional activity.

Not sure what MGADiag is but will track it down and see what I can come up with.

I entered the key at lest 5 times, each time I double checked it for accuracy reading both the sticker compared to what I entered and reading what I entered compared to the sticker. If one ends up failing activation guess I'll call MS as much as I hate to have to go through that ordeal.

Found, downloaded and ran MGADiag. Anything I need to cross out before I post the results. I did notice the Product Key is not displayed in full but the product ID is?

 

[NoelDP]

Please follow this tutorial and post an MGADiag report - then we can see what the problem is.

http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

Ignore errors produced when clicking on the Copy button - they simply mean that the tool could not create the backup files for some reason. The data is still copied to the clipboard for pasting to your response.

Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine (or inside the battery compartment), but do NOT quote the Key on the sticker!
https://www.microsoft.com/en-gb/howtotell/Hardware.aspx#PCPurchase

 

[BReeves]

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-YR4GP-83MRH-CP7DB
Windows Product Key Hash: 3CazF+cBwkyLeFIjVOaXJa57Y8c=
Windows Product ID: 00371-OEM-8978037-20969
Windows Product ID Type: 3
Windows License Type: OEM System Builder
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {445B1639-E8A6-4786-8926-2C30853708DB}(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: 7600.win7_rtm.090713-1255
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>{445B1639-E8A6-4786-8926-2C30853708DB}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CP7DB</PKey><PID>00371-OEM-8978037-20969</PID><PIDType>3</PIDType><SID>S-1-5-21-2841050044-961068677-783102406</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq dc7900 Convertible Minitower</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786G1 v01.08</Version><SMBIOSVersion major="2" minor="5"/><Date>20080825000000.000000+000</Date></BIOS><HWID>59B93607018400F8</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>HPQOEM</OEMID><OEMTableID>SLIC-BPC</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.7600.16385
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
Activation ID: 90a61a0d-0b76-4bf1-a8b8-89061855a4c9
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00178-780-320969-02-1033-7600.0000-2802012
Installation ID: 000296701392880784358605419840269965057693995683676326
Processor Certificate URL: [URL="http://go.microsoft.com/fwlink/?LinkID=88338"]SpcService Web Service[/URL]
Machine Certificate URL: [URL="http://go.microsoft.com/fwlink/?LinkID=88339"]RacService Web Service[/URL]
Use License URL: [URL="http://go.microsoft.com/fwlink/?LinkID=88341"]UseLicenseService Web Service[/URL]
Product Key Certificate URL: [URL="http://go.microsoft.com/fwlink/?LinkID=88340"]PkcService Web Service[/URL]
Partial Product Key: CP7DB
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 11/4/2015 8:19:04 AM
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: NgAAAAEABgABAAIAAAABAAAAAQABAAEAJJSK9uItVA24ksjrmClmg7DWqjEeDtLkRHS+MkbK
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   COMPAQ  EAGLLAKE
  FACP   COMPAQ  EAGLLAKE
  HPET   COMPAQ  EAGLLAKE
  MCFG   COMPAQ  EAGLLAKE
  ASF!   COMPAQ  EAGLLAKE
  TCPA   COMPAQ  EAGLLAKE
  SLIC   HPQOEM  SLIC-BPC
  DMAR   COMPAQ  EAGLLAKE

This is the second PC, do I need to run it on the first one also?
Both COA stickers say Windows 7 PRO Referbished PC's, Joy Systems.
Only difference is the Product Key

 

[wben353]

I'm having the same e-mail notification issue. Started a few weeks ago. Contacted Brink on same. Received one reply with suggestion, which I had already tried, delete all subscriptions, delete cookies. Still no e-mail.

 

[NoelDP]

The installed Key ends CP7DB
It appears to be properly activated - is this Key the one from the original machine, or the one you were attempting to enter for the second?

 

[BReeves]

The installed Key ends CP7DB
It appears to be properly activated - is this Key the one from the original machine, or the one you were attempting to enter for the second?

It's the key from the original PC, wasn't able to enter the key from the 2nd PC as it kept rejecting it.

 

[NoelDP]

OK - in that case you'll have a problem at some point in the future.
You need to change the Key.
When the Key change option fails even before starting the activation request, then it indicates that at least one of the characters is wrong. The usual suspects here are V/Y 8/B C/G/6 so try variants on any of those first.

 

[BReeves]

OK, I'll try it again but like I said I have double and triple checked it several times. May be a day or two before I get the chance.

Thanks for all the help.

 

[alphanumeric]

I had somebody say that in another thread not to long ago and when they did one last check they found they were entering a G when it should have been a C. They actually took a picture of the COA sticker and then enlarged it. Microsoft doesn't do you any favors with the font size or type.

 

[BReeves]

Success.. Not sure what I was doing wrong. This time I wrote the key down as I read it from the COA sticker then went backwards from what I had written to be double sure I had it written down correctly. When I entered what I wrote down it activated with the new key. The key does have a few B's I may have been trying to enter one or more as an 8, not sure as I hadn't written it down before this try.

Thanks for all the tips and help.

 

[alphanumeric]

Good stuff. It's almost like they intentionally make it hard to read.

 

[NoelDP]

Success.. Not sure what I was doing wrong. This time I wrote the key down as I read it from the COA sticker then went backwards from what I had written to be double sure I had it written down correctly. When I entered what I wrote down it activated with the new key. The key does have a few B's I may have been trying to enter one or more as an 8, not sure as I hadn't written it down before this try.

Thanks for all the tips and help.

Glad it worked - it's caught me a few times, to the point where I almost always now use a torch and magnifier to read a COA sticker, even if it's in good condition.

Good luck!

 

[wben353]

I agree with NoelDP on the characters, transposition can also occur.

What I usually do is use magnifying glass to read sticker, copy 5 characters, skip line, copy 5 characters, etc.

Reduced the error rate to almost zero.