Setup and install windows 10 enterprise build 15111 from the ISOĤ.

Has anyone else seen this issue? Is this an office 2016 issue with Windows 10 or is it the updates to windows 10 to make it version 1511 causing this? Quick overview of how i create my base generic vm images for win10.Ģ. I then went into Activation and changed the product key back to the KMS one: NPPR9-FWDCX-D2C8J-H872K-2YT43 I actually was rebuilding my hardware agnostic image in VMware today and again noticed this happening. Has the proper KMS key but the GUI is not showing this.

WTF is that key doing back? I ran my slmgr /dlv to see what exact key the system had vs what the gui was showing and yup. After it updated and installed KB3140743 i went back to activation screen and lo and behold. I just changed the product key for windows 10 enterprise to the default KMS client key Checked for windows updates and saw the KB3140743 updateĪnd then installed it. Is now our Office 2016 Key for KMS, ending in WFG99. Since the latest updates for 1511 for Windows 10 i noticed that in my Activation screen previously i saw the key installed being the last 5 digits to be the 2YT43 (ie KMS client key) however after the updates and a reboot i notice that the key showing We have setup and are properly activating Windows 10 via KMS using 2012R2 server and VAMT. I am working on creating and deploying Window 10 Enterprise 圆4 at my company.

Kms tools windows 10