-->

1. Office 2016 Retail-VL MAK Keys Office 2016 Pro Retail Keys: Office 2016 Pro Plus Phone Activation Retail Key BN346-KPVRG-HHQG3-6YDPV-8HV7H 22N9F-VR8HC-PW8TJ-HR6HM-X4TDV 3X8YH-BTNY7-JWQ77-XDD8W-J8GDV 4GNGX-8V2VP-6X6M7-M6HJK-6CQK7 4HNHG-V9PBB-BBTVY-C3MY4-MWRHH C8NBR-K9RGG-MP246-RQGJW-F3KX7 GCRKN-4PY64-3KJCJ-MBBH7-KHJ3V HNWFX-3G3J7-MC2JF-W6QJ2-KW3K7 KCNJT-98PG9-H3M2J-WKCBH-FJRHH KGVP3.
2. Microsoft Office 2016 Product Key for Professional Plus. FCMXC-RDWMP-RFGVD-8TGPD-VQQ2X PGD67-JN23K-JGVWW-KTHP4-GXR9G OFFICE 2016 PRO PLUS MSDN RETAIL: New Key1: B9GN2-DXXQC-9DHKT-GGWCR-4X6XK New Key2: 6PMNJ-Q33T3-VJQFJ-23D3H-6XVTX Tested working on Jan 1st. 2016 OFFICE 2016 VISIO PRO PRO PLUS MSDN RETAIL: New Key1: MT7YN-TMV9C-7DDX9-64W77-B7R4D If you want to activate by phone for free.
3. It stands for Microsoft Online. The installation is the Office 365 click-to-run version of Excel.

This article is written and maintained by Eric Splichal, Support Escalation Engineer and Matt Philipenko, Sr Premier Field Engineer.

Method 1: You use batch file to activate Office 365 without product key. Step 1: You copy the code below into a new text document. You copy the code by click here. Then you create a new text document. Step 2: You paste the code into the text file. Then save it as a batch file (named “1click.cmd”). Note: If you use Windows 10, you disable.

It's common for users to switch devices or for an enterprise to add or change M365 or O365 tenants. Another scenario is when enterprise organizations roam licenses or credentials to simplify the sign-in process. After a user is activated, multiple locations must be cleared to reset the application to a clean state.

Note

To automatically perform all of the checks listed below and run the appropriate scripts needed to reset the activation state, you can download and run the Microsoft Support and Recovery Assistant.

Step 1: Remove Office 365 license for subscription-based installations

Note

If Shared Computer Activation (SCA) is enabled and running, you shouldn't see any product keys installed during the procedure. If you're trying to set up SCA on a computer, make sure to clean up existing keys first.

You can use the ospp.vbs script to remove the Office 365 license. The ospp.vbs script is located in the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, go to the Program Files (x86)Microsoft OfficeOffice16 folder.

Important

Before you run the ospp.vbs, make sure that:

• If you want to run the script on a remote computer, the Windows firewall allows Windows Management Instrumentation (WMI) traffic on the remote computer.
• The user account you will use is a member of the Administrators group on the computer on which you run the script.
• You run ospp.vbs script from an elevated command prompt.

1. In an elevated command prompt, set the correct directory by using one of these commands, based on your Office installation location:

   or

2. Run the following command:

   The ospp.vbs command generates a report of the licenses currently in use. The output is in this format:

   Note

   The report could include multiple licenses. If the output contains a 'No installed Product Keys' message after you run ospp.vbs /dstatus, skip the section below and go to 'Step 2: Remove cached identities in HKCU registry'.

   Take note of the Last 5 characters of the installed product key.

3. If a partial product key is returned from /dstatus, run the following command:

   For example:

   Repeat the command until all keys are removed.

   If the output contains the message 'product key uninstall successful', close the Command Prompt window and go to Step 2.

Note

For Shared Computer Activation (SCA), remove the tokens listed under %localappdata%MicrosoftOffice16.0Licensing.

Step 2: Remove cached identities in HKCU registry

Warning

Follow this section's steps carefully. Incorrect registry entries can cause serious system issues. As a precaution, back up the registry for restoration.

In Registry Editor, locate the following registry:

HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonIdentityIdentities

Remove all identities under the Identities registry entry.

Note

If you have Shared Computer Licensing enabled, remove the same identities from the registry HKEY_USERSThe user's SID.

Step 3: Remove the stored credentials in Credential Manager

64-bit Download

1. Open Control Panel > Credential Manager.

2. Remove all Windows credentials listed for Office16 by selecting the drop-down arrow and Remove.

Step 4: Clear persisted locations

Clear the following persisted locations if they exist:

Credential Manager

• %appdata%MicrosoftCredentials
• %localappdata%MicrosoftCredentials
• %appdata%MicrosoftProtect
• HKEY_CURRENT_USERSoftwareMicrosoftProtected Storage System Provider

Office 365 activation tokens and identities

• %localappdata%MicrosoftOffice16.0Licensing
• %localappdata%MicrosoftOfficeLicenses (Microsoft 365 Apps for enterprise version 1909 or later)
• HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonIdentity
• HKEY_USERSThe user's SIDSoftwareMicrosoftOffice16.0CommonIdentity

OLicenseCleanup.vbs

The four steps above can be automated using OLicenseCleanup.vbs. Simply download and run the script with elevated privileges.

Clear Office credentials and activation state for managed devices

The above steps reset the Office activation for unmanaged devices (Domain Joined aka DJ). In a managed environment, more locations store credentials.

Devices are considered managed if they're Azure AD Joined (AADJ), Hybrid Azure AD Joined (HAADJ), or Workplace Joined (WPJ). These configurations use Web Account Management (WAM), which stores credentials in different locations.

Here's how to find out if a device is DJ, AADJ, HAADJ, or WPJ:

1. Open a command prompt as an administrator.

2. Type dsregcmd /status.

   Domain Joined (DJ):

   Azure AD Joined (AADJ):

   Hybrid Azure AD Joined (HAADJ):

   Workplace Joined (WPJ):

In scenarios where all stored credentials (such as domain/tenant migration) must be cleared, clear the additional WAM locations.

To clear all WAM accounts associated with Office on the device, download and run the signoutofwamaccounts.ps1 script with elevated privileges.

Note

• This script will remove tokens and accounts associated with Office, this is a safe operation. Single sign-on (SSO) of other applications will remain untouched, as well as the device state.
• This script is only compatible with Windows 10 version 1803 and later. If the OS isn't compatible, you'll receive a message saying the tool isn't supported on that version of Windows.
• Signoutofwamaccounts.ps1 can be ran separately or in conjuction with OLicenseCleanup.vbs. If you place signoutofwamaccounts.ps1 in the same location as OLicenseCleanup.vbs, running only OLicenseCleanup.vbs will also execute Signoutofwamaccounts.ps1.

Clear credentials from Workplace Join

To manually clear Workplace Joined accounts, go to Access Work or School on the device and select Disconnect to remove the device from WPJ.

Office 365 Mso 16.0 64 Bit Product Key Generator

To automate WPJ removal, download WPJCleanUp.zip, extract the folder, and run WPJCleanUp.cmd.

Note

This tool removes all SSO accounts in the current Windows logon session. After this operation, all applications in the current logon session will lose SSO state, and the device will be unenrolled from management tools (MDM) and unregistered from the cloud. The next time an application tries to sign in, users will be asked to add the account again.

Prevent Workplace Join on your device

After Office successfully authenticates and activates, the Stay signed in to all your apps dialog pops up. By default, the Allow my organization to manage the devices checkbox is selected. This registers your device in Azure AD while adding your account to Workplace Join.

To prevent your device from being Azure AD registered, clear Allow my organization to manage my device, select No, sign in to this app only, and then select OK.

To automate this configuration, add the following registry value to HKLMSOFTWAREPoliciesMicrosoftWindowsWorkplaceJoin:

'BlockAADWorkplaceJoin'=dword:00000001

For more information, see the following articles: