Microsoft Finally Fixes Windows 10 Activation Issue

Microsoft Finally Fixes Windows 10 Activation Issue

Microsoft has recently confirmed that the activation issue which hit Windows 10 earlier this week is now fixed, and the company explains that all systems that have been affected by the bug should be re-activated in the coming hours.

A number of Windows 10 Pro systems were listed as not activated due to what appeared to be a server-side issue experienced by Microsoft.

Reactivation did not work and running the built-in troubleshooter didn’t make any difference, with some users even complaining that their systems were upgraded from Windows 10 Pro to Windows 10 Home.

While Microsoft hasn’t released an official statement to confirm that the issue is fixed, a company engineer said in a discussion on the Community forums that reactivation should now happen automatically within the next 24 hours, while users can trigger it manually by launching the Troubleshoot option in Settings.

“Any affected customer can continue to use Windows 10 Pro as usual, and the watermark will disappear within 24 hours as activation is automatically restored. To manually resolve the issue: Select the Start button, select Settings > Update & security > Activation, and then select Troubleshoot to run the Activation Troubleshooter. (If the device is already activated, the Troubleshoot option will not appear.)” the post reads.

Use your system normally

You can find more information on this workaround and how to fix the Windows 10 activation issue in our detailed tutorial here.

User posts indicate that most systems which have previously been impacted by the activation issue are now working as normal, as the reactivation has either performed automatically or they launched the process manually.

Microsoft says that even if the system is listed as not activated, users can continue working just like before, no matter the error showing in the activation screen.

Oddly enough, some people who reached out to Microsoft Support were being told that no workaround exists, so an official statement from Microsoft in this regard would definitely be recommended.