Microsoft Activation - This copy of Windows is not genuine

[k-strider]

MAK keys are in the volume license service center and are unique to each individual organization.

[hardtailstar]

MAK keys are in the volume license service center and are unique to each individual organization.

 

Yep I know, Getting myself mixed up with this all and tearing my hair out.

 

Anyways I decided to wipe the laptop with a new SSD (had a HDD) and go from there.

[mavhc]

Glad I switched to motherboard authentication with Win 10 Pro then, easier and cheaper

[Ditto]

Is anyone seeing KB971033 return after removing. A couple of colleagues are saying they are seeing the KB971033 error come up even though it had previously been removed? I know there was supposed to a license check ever 90 days, but as we are Win 7 Enterprise, I didn't think we'd see the problem again if previously removed? It could be 90 days since it was originally removed. I hope to check some logs soon to confirm.

[hardtailstar]

Is anyone seeing KB971033 return after removing. A couple of colleagues are saying they are seeing the KB971033 error come up even though it had previously been removed? I know there was supposed to a license check ever 90 days, but as we are Win 7 Enterprise, I didn't think we'd see the problem again if previously removed? It could be 90 days since it was originally removed. I hope to check some logs soon to confirm.

Not seen it return but the activation seems to be hit and miss.

 

One laptop will be fine yet another won't even activate with both laptops having same image, updates and programs.

 

Sometimes it'll take days to work.

[witch]

I have a script that works on Win 7

BUT computers are still appearing that have the message. I have now sorted out almost all the staff laptops. The childrens laptops are 8.1 and unaffected. Never thought I'd be happy that they are on 8.1

I was told it was one update on one day doing this - but I have laptops that WERE fine and only now are showing the "not genuine" message. Don't get it.

This is my script:

net stop sppuinotify

sc config sppuinotify start= disabled

net stop sppsvc

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

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

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

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

net start sppsvc

cscript c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\windows\system32\slmgr.vbs /ato

sc config sppuinotify start= demand

 

Obviously you would need to put in your own licence code

[hardtailstar]

I have a script that works on Win 7

BUT computers are still appearing that have the message. I have now sorted out almost all the staff laptops. The childrens laptops are 8.1 and unaffected. Never thought I'd be happy that they are on 8.1

I was told it was one update on one day doing this - but I have laptops that WERE fine and only now are showing the "not genuine" message. Don't get it.

This is my script:

net stop sppuinotify

sc config sppuinotify start= disabled

net stop sppsvc

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

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

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

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

net start sppsvc

cscript c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\windows\system32\slmgr.vbs /ato

sc config sppuinotify start= demand

 

Obviously you would need to put in your own licence code

 

I use the same, doesn't always work!

[witch]

I use the same, doesn't always work!

 

I run it twice which seems to work OK

[hardtailstar]

I run it twice which seems to work OK

 

Ive run it many times on one laptop. Left it for a couple of days and then it worked!

[Cazale]

I ran a script on all ours and one just absolutely refused to accept the key. I got so mad with it I rang Activation Support, went through the menu options for Volume Licensing, got through to someone, and this genuine conversation just happened:

 

Support: "It's a Windows 7 Enterprise key and you're using Windows 7 Professional"

 

> (me) Nope, it's a volume licence key and works for either.

 

(we went round and round in circles for half an hour, with him insisting I install Windows 7 Enterprise instead. I eventually had to get him to remote to the PC and watch me click "Key" on Windows 7 Professional in the Volume License Service Centre).

 

"Right, you need to connect to the server"

 

> What server? What are you talking about?

 

"The key server"

 

> What 'key server'?

 

"Your company uses a server?"

 

> Err yes, are you talking about a key management server? Because we don't use that in this school, this is a MAK key.

 

"Oh it's a MAC key? Well that's your problem. You can't use MAC keys on Windows. Have you tried contacting your IT department?"

 

> Riggggght. I'll be off now. Thanks for your help.

 

(this was the brief version, total time on call was 40 minutes, getting absolutely nowhere).

 

I was in the queue waiting for another support agent when I tried the same script I'd tried 10+ times, and this time it thankfully worked. Absolutely no idea why it didn't work the previous X times I'd tried it, but there's definitely something dodgy going on. Not sure if it's the client or their activation servers, but it's a horrible waste of time when it happens. As I said above, we've seen this at multiple schools. I'm probably somewhere in the region of 10 hours wasted on this!

Edited May 13, 2019 by Cazale

[witch]

This issue has raised its head again. I am getting the message reappearing on PCs and laptops that I had sorted out weeks ago. Can anyone tell me why this is happening and if there is anything I can do?

[JJonas]

I am looking for an answer to this as well, I switched to your script as it appears to do it all without the need to reboot, but I am concerned that I am burning through my activations.

[E_G_R2]

Is it because the same update is being applied again? I'm also going through the pain again especially with those users who need their special desktop

[Ditto]

Interesting, some colleagues thought the same in terms of the problem reappearing in previously fixed PCs. I thought MS stopped the KB going out to Enterprise/Education editions. I'd be interested to hear if anyone's update logs show it getting reinstalled, but were there two different updates that could have originally caused the issue? Also, and this is pure speculation, for us it feels as though it could be 90 days since the PCs were fixed. I also have a feeling the license check intended for Home versions was going to check every 90 days?

[CiderBaz]

Bad luck.

[IonutZ]

Rebuild the activation-related files and then reactivate the system by running the following commands in a Command Prompt window as administrator:

net stop sppuinotify

sc config sppuinotify start= disabled

net stop sppsvc

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

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

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

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

net start sppsvc

cscript c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\windows\system32\slmgr.vbs /ato

sc config sppuinotify start= demand

Note In the first "cscript" command, replace XXXXX-XXXXX-XXXXX-XXXXX-XXXXX with the actual key.