Windows 7 VLSC MAK Key Now Invalid?

[JRA]

Hi all - bit of a panic here!

 

Set up a new KMS server just this morning, but it looks like our old client image used a MAK key. That key is still current in our VLSC but Windows itself and slmgr.vbs (partial key shows) now tell me it's invalid.

 

Can anybody tell me how to figure this out? What on earth does it want from me?

 

Thanks very much all.

[howartp]

Use VAMT to reset the key on clients to the default "GVLK" KMS client key.

 

Then add your MAK key to VAMT and once you've got 25 PCs connected, it will validate them all.

[cscc]

You could run a start up script via GP which pushes out the default KMS key to clients:

 

https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

 

Something like the below should work:

 

 

"%SYSTEMROOT%\system32\cscript.exe" "%SYSTEMROOT%\system32\slmgr.vbs" /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
cls
TIMEOUT /T 10
cls
"%SYSTEMROOT%\system32\cscript.exe" "%SYSTEMROOT%\system32\slmgr.vbs" /skms kms.server.dns.name:1688
cls
TIMEOUT /T 10
cls
"%SYSTEMROOT%\system32\cscript.exe" "%SYSTEMROOT%\system32\slmgr.vbs" /ato
cls
TIMEOUT /T 10
cls

[Chris_]

We've had a few PCs here reporting as not genuine.

 

Just browsing Reddit and I found this on the first page of /r/sysadmin..

[Arthur]

Just browsing Reddit and I found this on the first page of /r/sysadmin..

Have you also seen the following post on Reddit...?

 

https://www.reddit.com/r/sysadmin/comments/adyx0q/global_kms_activation_issues_reported/edl8tne

 

This the fix to save you the call to Microsoft.

 

1. Uninstall KB971033
   
2. Reboot
   
3. Run Command Prompt as administrator
   
4. Type:

   net stop sppsvc

   
   

5. Type:

   del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah

   
   

6. Type:

   del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah

   
   

7. Type:

   del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat

   
   

8. Type:

   del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat

   
   

9. Type:

   net start sppsvc

   
   

10. Type:

    slmgr /ipk 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH

    
    

11. Type:

    slmgr /ato

    
    

As others have correctly pointed out, the key in step 10 is for Windows 7 Enterprise. Use the correct key for your environment. https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

 

Someone also reported success with the following...

 

https://twitter.com/Jonathan_Job/status/1082774040278896641

 

slmgr /rearm followed by a restart and a slmgr /ato

Edited January 9, 2019 by Arthur

[JJonas]

slmgr /rearm followed by a restart and a slmgr /ato

 

Thanks, this worked for me.

[Cache]

So glad I came across this, an hour I spent trying to activate an f'ing laptop with a MAK key last night....

[JJonas]

This is quite a handy fix. I modified my copy to include our key.

 

https://support.microsoft.com/en-ph/help/4032981/powershell-script-for-windows-7-non-genuine-issue-is-available

[JJonas]

I am still getting this.

 

I can patch it by using the batch file but is there a way to stop it once and for all?

[masond]

If people are still having this issue, it's windows update kb:971033, uninstall and try vamt it again