FIXED: Error: “Microsoft Office cannot find your license for this application” and application closes in Office 2016 (Build: 16.0.7167.2040)

Anonymous
2016-09-14T21:33:54+00:00

Issue:

When opening an Office application, you may see the following error message:

"Microsoft Office cannot find your license for this application. A repair attempt was unsuccessful or cancelled. Microsoft Office will now close."

IMPORTANT: This error appears if you have this Office 2016 build: 16.0.7167.2040. If you don’t have this specific version and you’re getting this error, or you’re getting a different error, we recommend you create a new post. To check your Office version, choose the Uninstall a program option in the Windows Control Panel, find your Office program in the list and check the version number.

Status: Fixed

This licensing issue has been resolved in Office 2016 version 16.0.7167.2055 or later. To get the latest update, please run an online repair of Office 2016:

  1. Restart your computer. Don’t open any Office applications when you’re back on your desktop.
  2. Run an online repair of Office from the Control Panel.

IMPORTANT: Please choose the Online Repair option instead of Quick Repair. If you run Quick Repair, the latest build version doesn’t get installed. 3. Restart the computer again and open the Office application. 4. Click File > Account, and verify the Office version under Office Updates in the Product Information section. It should be a newer version than 16.0.7167.2040.

If you’ve done the above step and you continue to get the same error message, please do the following:

  • Choose the Uninstall a program option in the Windows Control Panel, find your Office program, and check the Office version.
  • If the Office version isn’t 16.0.7167.2040, create a new post with the error you’re getting along with the exact Office build version.
Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

120 answers

Sort by: Newest
  1. Anonymous
    2016-09-19T21:38:17+00:00

    Mine is up to date and does not work.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-19T20:29:45+00:00

    Thank you Jo for reporting back. This confirms the solution on our end as well and the build that caused this issue (.2040). Glad to know that this is now working for you.

    Thanks,

    Michelle V.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-09-19T20:21:39+00:00

    Hello Michelle

    MS Word (About) -> 16.0.7127.1026. 32 bit; I'm on version 16.0.7167.2060

    I've not seen the error message since I managed to update to this (it was 2040 when it went horribly wrong)

    Fingers crossed eh? ;-)

    I'm going to drop out this thread now, my mail box is overflowing with unhappy souls.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-09-19T18:52:56+00:00

    I have given up.

    The PC is new and so has next to nothing on it. Am currently wiping and reinstalling Windows. Not happy.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-09-19T18:19:48+00:00

    The initial error message told me that I did not have an active license.  I have been using Office 2013 since inception and upgraded to Windows 10 on July 8, 2016.  Office closed down and told me to repair/uninstall re-install if that failed.  I was able to uninstall but now cannot reinstall.  Prior to the repair attempt, I noted that the installation date was 9/6/2016.  I did not install on that date and the last Windows updates were run on 8/29/2016.  I checked another user and noted that there workstation also had 9/6/2016 installation date.  The laptop was deployed last March.  Did Microsoft push out something?  So this in not just on Office 365 problem.

    In any event, I am not currently able to reinstall Office 2013.  So far, I am the only workstation with this issue, but since you have identified this as a problem, I expect additional license issues.

    Any ETA to resolve this matter?

    Was this answer helpful?

    0 comments No comments