![office 2016 will not activate 365 office 2016 will not activate 365](https://www.smartwebsolutions.org/blog/wp-content/uploads/2019/11/ms-office-activation-page.jpg)
- #Office 2016 will not activate 365 how to
- #Office 2016 will not activate 365 update
- #Office 2016 will not activate 365 windows
These tips will save significant time during the deployment of Office on Windows Server 2019. The above can be accomplished using Group Policy Preference (in a GPO): [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableAADWAM"=dword:00000001 This is a ‘per user’ fix and requires adding the following registry keys: [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity "DisableADALatopWAMOverride"=dword:00000001 To date, the only available fix is a work around that suppresses Web Account Manager (WAM) and reverts Office 365 back to Azure Active Directory Authentication Library (ADAL). However, it only includes half of the workaround and does not provide sufficient details. Trying to activate a seamless published Microsoft Word app will result in an email prompt followed by a complete “freeze” of your Word app.Ĭitrix has released an official CTX article for this issue.
![office 2016 will not activate 365 office 2016 will not activate 365](https://www.thewindowsclub.com/wp-content/uploads/2019/03/Microsoft-Office-Sign-In-600x360.png)
Here is what should be expected when launching Microsoft Word for the first time (native MS and Okta):Īuthentication Experience with Microsoft as IdP:Īuthentication Experience with Okta as IdP: It is a known issue that “Microsoft is working on fixing it” since June 2020. Surprisingly, there is a bug in Windows Server 2019 that breaks the WAM process for published apps. However, with modern builds, Office uses Web Account Manager (WAM) for sign-in workflows for activation. Microsoft used Azure Active Directory Authentication Library (ADAL) framework-based authentication for older builds such as Office 2016. The issue lies in the authentication process. So, what is happening here: the newest Office on the newest server OS cannot activate even using Microsoft’s native activation process? The following updates have the same effect on the Office activation, KB3127907, KB3128055 and the latest one is KB3141505.
#Office 2016 will not activate 365 update
Once this update gets installed Office 2016 loses its activation and can not be activated again until the update is uninstalled.
![office 2016 will not activate 365 office 2016 will not activate 365](https://support.content.office.net/en-us/media/493c02f0-060d-440e-97b0-23161bd167a5.png)
![office 2016 will not activate 365 office 2016 will not activate 365](https://support.content.office.net/en-us/media/242cd36c-f280-4c93-9e6d-00c512ca2b7e.png)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\OEMĬlose the Registry Editor and start Office again.As we move Citrix Virtual Apps and Desktops\Service (CVAD\S) workloads to Windows Server 2019 we notice quite a few outcomes that are “different” and (who would think) do not work in this OS. Right click the OEM value and click File>Export.Īfter the key is backed up, select Edit>Delete. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Common\OEM On the left side of the Registry Editor, under Computer, navigate to the following key in the registry: Select Yes when prompted to open the Registry Editor. Right-click the Start button on the lower-left corner of your screen, and select Run. Then, you can restore the registry if a problem occurs.Ĭlose the activation window and all Office apps. For added protection, back up the registry before you modify it. Therefore, make sure that you follow these steps carefully. However, serious problems might occur if you modify the registry incorrectly.
#Office 2016 will not activate 365 how to
Important: This task contains steps that tell you how to modify the registry.