Windows 7 Activates - Valid - Not Genuine

[timconstan]

Hi,

I have Windows 7 Professional & 35 identical computers each with a unique Windows 7 license. I setup PC 1 the way I want it, and am using FOG to clone the image to PC 2. On PC 2, after copying the image from PC 1, I change the windows registration key to match the one that came with that computer (from HP -- I know it's a good key!). Registration process happens with no issues and I get a message saying the key is valid. A couple of days later I get a popup saying that my copy of windows is not genuine. I continue to get these popups on all PC's.

Tried various slmgr.vbs options with no success.

See attached screen shots showing that Windows is activated/valid and the 2nd showing that windows is not genuine.

 

[zigzag3143]

Hi,

I have Windows 7 Professional & 35 identical computers each with a unique Windows 7 license. I setup PC 1 the way I want it, and am using FOG to clone the image to PC 2. On PC 2, after copying the image from PC 1, I change the windows registration key to match the one that came with that computer (from HP -- I know it's a good key!). Registration process happens with no issues and I get a message saying the key is valid. A couple of days later I get a popup saying that my copy of windows is not genuine. I continue to get these popups on all PC's.

Tried various slmgr.vbs options with no success.

See attached screen shots showing that Windows is activated/valid and the 2nd showing that windows is not genuine.

Different GUID on each. When you clone you you export the GUID of PC-1 and when PC-2.... tries to activate it shows as activated.

You cant do it that way. You might be able to clone before activation then activate with a valid key

 

[timconstan]

I'm not sure how far I can get in configuring the PC to look the way I want all PC's to look before I'm forced to activate Windows, but I'll give it a shot.

Shouldn't the "change registration key" option shown at the bottom of screen shot 1 allow me to really change the registration key and have things reported as genuine or is it not that smart?

 

[theog]

I change the windows registration key to match the one that came with that computer

Hi Ken

Would it be not better to leave the factory OEM-SLP activation method Product Key in place?

 

[timconstan]

Would it be not better to leave the factory OEM-SLP activation method Product Key in place?

I'm not sure what you mean...

If you mean that I should just copy PC 1 to PC 2 and then not change the product key in PC 2 to match that computer, I still get the same message on PC 2 -- that the copy of Windows is not Genuine.

If you mean I should do something with PC 2 before I copy PC 1 image over to it (I currently am not -- just copying the PC 1 image to PC 2 out of the box), I'm not sure what that would be...

 

[theog]

I have Windows 7 Professional & 35 identical computers

As in HP/Compaq, Yes.

Therefore, All your PC's have the same factory OEM-SLP activation method Product Key installed.

System Locked Preinstallation - Wikipedia, the free encyclopedia

 

[Bill2]

On any of the machines thats non-genuine right now, please download and run this tool.

go.microsoft.com/fwlink/?linkid=52012

In the tool, click Continue, then click Copy, paste into notepad, save as a .txt file and upload the file here.

 

[timconstan]

WGA Diagnostic Report

- Attached -

 

[timconstan]

All your PC's have the same factory OEM-SLP activation method Product Key installed.

I see. Please forgive my ignorance, but I don't know what this means in practical terms. Are you suggesting that I should just be able to clone PC 1 to PC 2 and not change anything and PC 2 should show up as Genuine?

 

[Bill2]

Yes. The machine is licensed but not validated. This is likely the issue:

Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui

Are you using some vistalizator type of software for language settings? If not, something else seems to have corrupted this file so windows thinks its tampered with. To test, run SFC scan 3 times.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

See if its able to clear the corruption. You can run validation again after that. Also run mgadiag then because if the problem is not cleared it'll show up again.

 

[theog]

In practical terms, If you make one set of the HP/Compaq Recovery disks using the disk app, as you have 35 identical computers, the disks will reinstall all the PC's to back to first day you had your new PC.

What you will be doing is making your own Recovery Disks.

 

[Bill2]

timconstan, Apart from the current issue there are also licensing issues with reimaging OEM systems unless you have a volume license, OEM systems are essentially single installs. See here for more info.

Sysprep'ing an OEM Windows 7 image for WDS - Spiceworks Community

 

[timconstan]

Bill2: Took your advice about running sfc /scannow 3 times

---

C:\Users\OneStop1>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

---

Re-running MGADiag, no longer says files have been tampered with. (file attached)

---

Going to Genuine Microsoft Software -- still says I need to buy a copy of windows.

 

[Bill2]

SFC scan was not able to repair the tampered file. MGADIAG log still shows the same tampered file, look carefully. Normally when sfc scan fails, we advise a repair install but I dont know whether its possible with your setup. But its possible your cloning process is responsible for the tampered file. I'm afraid I have no idea about that software and process you use but maybe you can consult the chaps who do. Please correct me but I think this issue occurs only in the cloned systems, not in the mother machine?

But please take a look at the oem sysprep page I linked in my earlier post.

 

[timconstan]

In practical terms, If you make one set of the HP/Compaq Recovery disks using the disk app, as you have 35 identical computers, the disks will reinstall all the PC's to back to first day you had your new PC.

What you will be doing is making your own Recovery Disks.

But I don't want to "reinstall all the PC's back to the first day you had your new PC." I want to copy the way I have PC 1 setup to PC 2.

 

[theog]

In practical terms, If you make one set of the HP/Compaq Recovery disks using the disk app, as you have 35 identical computers, the disks will reinstall all the PC's to back to first day you had your new PC.

What you will be doing is making your own Recovery Disks.

But I don't want to "reinstall all the PC's back to the first day you had your new PC." I want to copy the way I have PC 1 setup to PC 2.

The best way is not to use sysprep as all 35 are identical computers,
& leave the factory OEM-SLP activation method Product Key in place.
In practical terms, you will be making one set of your own Recovery Disks for all 35 identical computers .

 

[alphanumeric]

The OEM-SLP activation method only works if the install media has the $OEM$ folder and that folder has the correct certificate file to match the BIOS SLIC table. It sounds like the OP is using regular install media and inputing the product key on the COA sticker when asked. If so he or she will have to obtain the custom branded OEM install media to go back to SLP activation.

 

[timconstan]

It sounds like the OP is using regular install media and inputing the product key on the COA sticker when asked.

Yes.

If so he or she will have to obtain the custom branded OEM install media to go back to SLP activation.

Does that mean I need to use my install disk and start from scratch or is there something I can do to fix my problem without starting from scratch?

 

[theog]

You could Start a fresh with one of other 35 identical computers

 

[timconstan]

SFC scan was not able to repair the tampered file. MGADIAG log still shows the same tampered file, look carefully.

Sorry about that.

Normally when sfc scan fails, we advise a repair install but I dont know whether its possible with your setup.

I understand this is not possible because I've already applied updates to windows and installed software

But its possible your cloning process is responsible for the tampered file. I'm afraid I have no idea about that software and process you use but maybe you can consult the chaps who do. Please correct me but I think this issue occurs only in the cloned systems, not in the mother machine?

That's correct.

But please take a look at the oem sysprep page I linked in my earlier post.

I looked. It says "You MUST purchase at least one Windows 7 volume license from Microsoft". Maybe the only answer but extraordinarily frustrating! I already bought 35 licenses -- not in the mood to buy something else.