Computers suddenly showing as "Non-Genuine"

A few of our computers have suddenly started showing "non-genuine". We have had a KMS server for a while now and all was running fine. When we try to activate them with slmgr /ato we get the message " Error Windows is running within the non-genuine notification period"

Does anyone know why this is happening and how we can fix it please?

Windows 7?

www.edugeek.net/forums/windows-7/202767-windows-7-vlsc-mak-key-now-invalid.html

If I use VAMT to activate then I get a message to say "successfully activated" but the expiration date is the date and time I ran the command.

Are they on windows 7?

Updates KB4480970 and KB4480960 are causing problems

Regarding the 'Not Genuine' Windows 7 error, Microsoft confirms that "some users are reporting the KMS Activation error, 'Not Genuine', 0xc004f200 on Windows 7 devices".

https://www.zdnet.com/article/microsofts-killer-windows-7-patch-breaks-networking-bricks-legit-not-genuine-pcs/

Windows 7?

 

www.edugeek.net/forums/windows-7/202767-windows-7-vlsc-mak-key-now-invalid.html

Yes windows 7 but we didnt use MAK keys. On VAMT it shows as KMS

Strangely when looking at VAMT more closely some of the info doesnt make sense. "The Licence Status last Refreshed" on some machines is way out of date (2017!!). I thought machines had to talk back to KMS every 180 days?

Are they on windows 7?

 

Updates KB4480970 and KB4480960 are causing problems

 

 

 

https://www.zdnet.com/article/microsofts-killer-windows-7-patch-breaks-networking-bricks-legit-not-genuine-pcs/

I rejected KB4480970 following @Arthur Thread. I will now check KB4480960 as this may have gone out to computers last night.

https://www.zdnet.com/article/microsofts-killer-windows-7-patch-breaks-networking-bricks-legit-not-genuine-pcs/

Just found these articles which exonerate those KBs.

https://support.microsoft.com/en-us/help/4480960/windows-server-2008-kb4480960

https://support.microsoft.com/en-us/help/4487266/activation-failures-and-not-genuine-notifications-on-vl-win-7-kms-clie

Just trying to remove KB971033 from one affected machine to see if it resolves the issue.

This should fix it for you, happened to a few here and this was the fix mentioned on reddit I got from a post in here:

If using KMS in domain Run elevated command propmt rub “ slmgr /rearm “ reboot the machine then run ‘slmgr /ato.

OK, so we are using the MAK key rather than KMS. I've just tried uninstalling KB971033 and then doing the slmgr /rearm, reboot, slmgr.vbs /ato method and it works!! But everything I read says that this update affects KMS environments?

Any clues? And any quick ways to push this around the network?

OK, so we are using the MAK key rather than KMS. I've just tried uninstalling KB971033 and then doing the slmgr /rearm, reboot, slmgr.vbs /ato method and it works!! But everything I read says that this update affects KMS environments?

 

Any clues? And any quick ways to push this around the network?