Over 100 machines requiring reactivation

[Trouble-Shooter]

Hello everyone,

A business I manage has (over the last 48 hours) had over 100 machines suddenly get flagged for Not Genuine Windows. I go to each one and reactivate using the OEM key on each machine and all is well. We do not use any kind of Key Management Server or volume license. Does anyone know what could cause this issue? I have eliminated the following:

-hardware changes
-software changes
-group policy updates

That's all I can think of off the top of my head. I'm not greatly concerned about getting these systems activated and all, I'm more worried that in a few days the problem will repeat itself.

I appreciate your time, and hope everyone is enjoying their summer!

Machine info:
All HP machines (laptops and desktops)
Windows 7 Professional 64
All are less than 2 years old
All are daily-use machines

 

[Slaters Kustum Machines]

Have you checked the time on them? Are NTP settings correct?

 

[Trouble-Shooter]

Everything is synced up as it should be. That was a good idea though, I hadn't checked that yet.

 

[FremontPC]

Check to see if your A/V quarantined something it shouldn't have, a certificate or the like?

 

[YeOldeStonecat]

A/V FP is my first hunch.

 

[Slaters Kustum Machines]

Any updates installed over the last couple of days?

 

[Trouble-Shooter]

We haven't had any updates get pushed out for the last 2 weeks. That company uses Symantec for a/v, that may be a good direction to go. I'll report back. Thank you all for your ideas.

 

[YeOldeStonecat]

That company uses Symantec for a/v, that may be a good direction to go. I'll report back. Thank you all for your ideas.

Won't be the first time SymantSuck caused a "Windows ain't genuine" error....look at this Google search link and how many different dates are sprinkled across time here from many glitches from updates...
https://www.google.com/webhp?source...mantec update causing windows genuine&es_th=1

 

[jft135]

We've been seeing a lot of mangled systems over the last few days that were ultimately resolved by removing Symantec products. They must have released a bad update recently.

 

[Trouble-Shooter]

Removed SEP from an affected machine and rebooted. "Not Genuine" error has disappeared and Windows states it is activated. Thanks everyone! I'm glad to be back on these forums. It has been a while. Enjoy your weekend!

 

[ohio_grad_06]

Had one at my work like this about a 2-3 year old hp with sep ironically, which is what we run at my full time job, not my choice though. But seems like there was a Windows update that caused issues. Do some googling, there is an update I had to uninstall and hide I think and it was happy.

 

[nlinecomputers]

I had a system on the bench that was a N&P do this during windows updates. Had to phone it in.