Version non authentique de windows

It don't think it can be directly connected to those patches - they were only just released and I expect very few Enterprise clients will have deployed them yet as there are usually testing and change control processes to follow which delay patch deployment by a week or more.

None of the machines I'm seeing affected by this have received the patches for January yet. We first started getting reports of this early afternoon GMT on the 8th, a few hours before patches would have been released. Is there anything that would cause an activated Windows 7 machine to jump straight from successful KMS activation one day to Non-Genuine notification the next? Or does this only happen after days of not activating? In which case did the problem happen back in July?

None of our VDI machines that exhibited the issue had the Jan updates installed. This leads one to conclude that a change in the Microsoft activation servers on 8-Jan triggered the issue. Yes, KB should not be installed on Windows 7 computers in a KMS environment, but since this KB is advertised via Microsoft update, it can potentially sneak back in, and a change in the Microsoft activation servers could cause the issue to reoccur.

I just checked one of the workstations Windows 7 Pro that had this problem occur for us yesterday and it does not have any of these 3 updates installed. This is good information to learn about, but I have to think there is still something else going on that can cause this problem. 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 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.

La raison principale pour laquelle Windows 7 n'est pas authentique est que vous n'utilisez pas la version authentique de Windows fournie par Microsoft. D'autre part, n'oubliez pas de nous communiquer vos suggestions pour rendre Windows 7 authentique ou vos questions lors de l'utilisation de MiniTool ShadowMaker pour la sauvegarde de l'ordinateur.

Achetez-le toujours sur le site officiel de Microsoft.