Reset Microsoft Office Product Key Mac
Microsoft HUP product keys. Office 2010 product keys. Office 2007 product keys. Office for Mac 2011 product keys. My product key isn't working. First, make sure that you're entering the key correctly on the right site. If you aren't sure which site to use, you can enter your product key using the Virtual support agent (English only). Change your Office product key. On the device where you want to change the key, open any Office app, select the File menu and then select Account near the bottom of the menu. Under Product Information, select the Change License button. If there is no Change License button, you may need to install. Important: Before using the tool, make sure you have the correct account info and password associated with your purchase of Office available for when you reactivate. This tool can also help if you've subscribed to Office 365 but previously had a one-time purchase of Office for Mac on your computer. Jan 30, 2020 Microsoft Office 365 Product Key 2020 + Activator Cracked Microsoft Office 365 Product Key has the many sets up alternatives by making use of individual elements as well as installation files.It may be saved up to five distinct Pc, remote desktop, tablet devices, and Mac. Feb 12, 2020 How do I reload Microsoft office after I had to factory reset my mac. I factory reset my Mac - Answered by a verified Microsoft Office Technician. Hi I am not able to locale the key for microsoft office product on my mac for Renewal how can I do?
This article is written and maintained by Matt Philipenko, Sr Premier Field Engineer. It's very common for users to switch devices or for an enterprise to add or change Microsoft Office 365 tenants. Another scenario is when enterprise organizations roam licenses or credentials to simplify the sign. Jun 29, 2018 Agreement that the key belongs to - License Number (not product key) Total number of Activations you want to see - if original was for 150 and you need it reset to 150, ask for 300; Reason Why you are requesting this - Reimaging, loss of key by VAMT (my problem) Product that is being referred - Windows 7, Office 2010, Office 2013.
-->This article is written and maintained by Matt Philipenko, Sr Premier Field Engineer.
It's very common for users to switch devices or for an enterprise to add or change Microsoft Office 365 tenants. Another scenario is when enterprise organizations roam licenses or credentials to simplify the sign- in process. After an Office 365 user is activated, there are multiple locations that must be cleared to reset the application to a clean state.
Step 1: Remove Office 365 license for subscription -based installations
Note
If Shared Computer Activation (SCA) is enabled and running, you should not see any product keys installed when you follow this procedure. However, if you are trying to set up SCA on a computer, make sure that you first clean up any existing keys.
To remove the Office 365 license, follow these steps:
Run the following cscript command:
Note
The opss.vbs script is in the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, the script is in the Program Files (x86)Microsoft OfficeOffice16 folder. Before you run the 'ospp.vbs' command, you may have to change to the correct directory by using one of the following commands, based on your Office versions:
cd C:Program Files (x86)Microsoft OfficeOffice16cd C:Program Files/Microsoft Office/Office16
The 'ospp.vbs' command generates a report of the current licenses that are in use. The output resembles the following example:
Note
You might see multiple licenses in the report. However, if the output contains a 'No installed Product Keys' message after you run
ospp.vbs /dstatus, you can skip 'Step 2: Remove cached identities in HKCU registry' and go to Step 3.Note the value for Last 5 characters of installed product key.
Run the following command:
For example:
Repeat the command if it is necessary until all keys are removed.
If the output contains a 'product key uninstall successful' message, you can close the Command Prompt window and go to Step 2.
Step 2: Remove cached identities in HKCU registry
Reset Microsoft Office Product Key Mac Free
Warning
Follow the steps in this section carefully. Serious problems can occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
In Registry Editor, locate the following registry:
HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonIdentityIdentities
Remove all the 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
Open Control Panel > Credential Manager.
Remove all Windows credentials that are listed for Office16. To remove the credentials, select the drop-down arrow and then select Remove.
For Shared Computer Licensing scenarios, you must remove the tokens and identities that are listed as follows:
AppdatalocalMicrosoftOffice16.0Licensing
Step 4: Clear persisted locations
Clear the following persisted locations:
Credential Manager
- AppdataRoamingMicrosoftCredentials
- AppdataLocalMicrosoftCredentials
- AppdataRoamingMicrosoftProtect
- HKEY_CURRENT_USERSoftwareMicrosoftProtected Storage System Provider
Office 365 activation tokens and identities
- AppdatalocalMicrosoftOffice16.0Licensing
- %localappdata%MicrosoftOfficeLicenses (Microsoft 365 Apps for enterprise version 1909 or later)
- HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonIdentity
- HKEY_USERSThe user's SIDSoftwareMicrosoftOffice16.0CommonIdentity
These steps reset the activation state for Microsoft 365 Apps for enterprise. After the locations are cleared, the activation flow will represent an initial activation.
The four steps can be automated by using a script. To do this, copy the following content, save the content as a .vbs file, and then run the .vbs file.
Windows 10 Reset Product Key
Simply signing into Office as another User does not change the 'Belongs to' entry in Office 2016. If the person it belongs to doesn't match the signed in person Office 2016 will start showing a licensing error.
It would be nice if there was a change owner button, or something similar, but there isn't. Luckily, it's not too hard to fix.
4 Steps total
Step 1: Open a command prompt
Use your favorite method to get a command prompt open. Winkey+R then CMD, Start then Command Prompt, etc.
NOTE - you need to run this as administrator
Step 2: Run the ospp.vbs command
Run the following command to get the last 5 digits of the product key:
cscript.exe '%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs' /dstatus
Step 3: Run ospp.vbs again, different options
Run the same command again, but change the options. This time you will be unpublishing the key you found in step 2. Replace XXXXX with the key from step 2.
cscript.exe '%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs' /unpkey:XXXXX
Step 4: Exit command prompt, run an Office app
Once you've exited the command prompt open any Office program (Word, Excel, etc.) and you will be prompted to sign in. Whatever account you sign in with will become the 'Belongs to' account.
It only takes a few seconds to do this, but I don't know why MS made it so you have to leave the apps and go CLI for it.
References
- PS script wrapper to automate these steps
6 Comments
- DatilJosh_Cunning Oct 13, 2017 at 07:54pm
I have this issue a lot and you might also need to check a few other places for like the Credential Manager
Also you might need to clear this registry entries:
HKCUSoftwareMicrosoftOffice15.0 or 16.0CommonIdentityIdentities
HKCUSoftwareMicrosoftProtected Storage System Provider
HKCUSoftwareMicrosoftOffice15.0 or 16.0CommonIdentity
HKEYU(The Users SID)SoftwareMicrosoftOffice15.0 or 16.0CommonIdentity - Pure CapsaicinDragonsRule Oct 13, 2017 at 07:55pm
I've never had to do any of that, but thanks for the info.
- Pimientotommurphy5 Oct 13, 2017 at 09:11pm
yeah you can do this, good for non-shared activation of Office 365 2016. its worth looking into the Office Deployment Toolkit from MS, you can setup Shared-User activation for systems that have multi users.
- Chipotleuberchemist Feb 1, 2019 at 08:53pm
Running the commands alone did not affect the 'Belongs to:' entry for me, though I am running Office 365, not 2016. But the comment from Josh about clearing the registry entries DID work. Thanks guys!
- AnaheimDiscordantQ Jun 20, 2019 at 01:36pm
is there a fix for Mac for this? or will this work just as well in Terminal?
- Pure CapsaicinDragonsRule Jun 20, 2019 at 01:42pm
Sorry, I have no Apple devices so have no idea.