Each of our Windows 7 computers with the activation issue ran the "ValidatationTask" just prior to the losing their activation. The "ValidatationTask" task reaches out to co2. Microsoft probably soon realized something was messed up and corrected it.
So when you run the task now, Windows 7 will activate. Can someone from Microsoft explain what happened? Then just entered commands provided. The scary part is I checked the thread just to say Thanks to Teemo and didn't expected to see so many declaring the issue. I didn't find it on failed workstation. Logically, it should not be distributed to corporate environment and should not be applied VLK installations since it was considered for retail versions of W7.
My WSUSs don't have this update for distribution. Yes it could be that this KB was in some deployed images. If it came from MS during Windows 7 update, it came The question how to roll it back in large environment There are machines that possibly have this update for more than a year and KMS activation was not affected. There are many people that declared the same activation problem. Looks like something was done "centrally" and probably should be fixed. We managed to take KB update on time off most of our clients machines, but still got few machines being out of premises for beginning of January and they all got "not-genuine" notification now?
It would be a great solution if couple of more will appear. Or adjusted on their side. There are no "storms" that supposed to come if all W7 were affected. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.
Archived Forums. Windows 7 Installation, Setup, and Deployment. Sign in to vote. Hi, 2 KMS servers in place in large environment. Functioning flawlessly. Today got a request for one W7 machine that is on network for at least couple of years. Prior to ask Telnet connection is fine. Diagnostic Report 1. Tuesday, January 8, PM. Juergen 0. Edited by J. Friday, January 11, AM. Don't have any of those updates applied and has been running fine for years.
Something is going on! We have Windows 10, 8. Marked as answer by pob Wednesday, February 13, PM. Wednesday, February 13, AM. Detailed step-by-step guide here: Uninstall KB Wednesday, January 9, AM.
Juergen Thursday, January 10, AM. Wednesday, January 9, PM. Same here. Several hours of troubleshooting and testing and no solution till now. The only workaround was to slmgr. But this is a temporary solution Additional information will be very apreciated.
This is causing caos Same problem here. We have the same error. This looks like a MS problem! Same issue - started yesterday morning for us. We've been chasing our tails trying to identify the cause.
We're seeing this too. Seriously Microsoft? It will expire in days- you'd have to do it again. Proposed as answer by jamesaf Thursday, January 10, PM.
Thursday, January 10, AM. Proposed as answer by J. According to users' feedback, this issue often occurs after installing some updates with the message on the bottom right of the desktop that says:. Vous pouvez maintenant utiliser la commande slmgr -rearm pour 8 autres fois, soit jours de plus. Suivez ces instructions pour activer votre copie de Windows.
Parfois, vous pouvez soudainement recevoir le message "cette copie de Windows n'est pas authentique" alors que vous utilisez un Windows authentique. Pendant ce temps, le message "Cette copie de Windows n'est pas authentique" est apparu.
0コメント