
Make sure this is the July licensing issue
Microsoft's known-issue page names two launch messages:
- Unknown Error 0x0
- License Not Found
The timing matters. Microsoft says a licensing certificate used by Microsoft 365 apps expired on July 13, 2026. Apps with the renewed certificate continue normally; older supported builds can enter reduced functionality. Microsoft marked the exact issue Resolved on July 15 and directs users to update.
Error code 0x0 by itself is not a diagnosis. If your message is different, began well before July, follows a payment or account change, or appears in software other than Office, preserve the exact wording and use the support path for that problem.
Before you update, save five details
- the full message and which apps show it
- the macOS version from Apple menu → About This Mac
- the Office version from the app name → About, if the app opens
- whether Office came from microsoft.com, an employer or school, or the Mac App Store
- whether you can open, print, edit, save, and create files
Review screenshots before sharing them. Account email addresses, organization names, filenames, recent documents, and license details can be private.
Choose the update path that matches your install
Office installed from microsoft.com
- Confirm the Mac runs macOS 12 or later.
- Save open documents and fully quit Word, Excel, PowerPoint, Outlook, OneNote, and other Office apps.
- Open Finder → Applications → Microsoft AutoUpdate.
- If Microsoft AutoUpdate is not in Applications, check
/Library/Application Support/Microsoft/MAU2.0/. - Review the available app versions, then choose Update All or update the affected apps individually.
- When the updates finish, reopen one Office app and test again.
Use Microsoft AutoUpdate for this branch. Do not install a second App Store copy on top of it just to test the theory.
Office installed from the Mac App Store
- Confirm the Mac runs macOS 12 or later.
- Save your work and fully quit every Office app.
- Open the App Store and select Updates in the sidebar.
- Update Word, Excel, PowerPoint, Outlook, and OneNote individually, or choose Update All.
- Reopen one app and test activation plus create-and-save behavior.
App Store copies update through the App Store. If the app does not appear there, stop and confirm where it came from rather than mixing installers.
Check the version and operating-system boundary
For Microsoft 365 on Mac, Microsoft's current certificate guidance lists macOS 12 or later and Office version 16.83 or later as the minimum for the July 2026 certificate change. A newer supported version is preferable when it is offered through your normal channel.
That 16.83 figure belongs to Microsoft's Microsoft 365 certificate guidance. Perpetual Office editions have their own lifecycle and update eligibility. Do not assume one version number covers every license type.
Office 2019 for Mac is a hard support boundary
Office 2019 for Mac is out of support. A copy that cannot receive the required licensing update may stay in reduced functionality. Do not use an activator, crack, modified installer, copied license file, or forum script to force it back into service. Use a supported Microsoft 365 or Office release, or Microsoft 365 for the web in a supported browser while you plan the transition.
An older Mac may not be able to take the update
If the Mac cannot run a supported macOS version, it may not be able to install the Office build that carries the renewed certificate. Back up important files, check Apple's support boundary for the exact Mac, and avoid an unsupported operating-system patch as a licensing workaround. Microsoft points affected users toward supported hardware or Microsoft 365 for the web.
Reduced functionality is not the same as lost files
Microsoft describes reduced functionality as being able to open, view, and print existing files while editing, saving, Save As, and creating new files are blocked. Microsoft also says the certificate change is not a security vulnerability and does not put customer data at risk.
Still, keep a current backup before changing software. A licensing message is a bad time to discover that an important file exists in only one place.
Verify the fix with a small test
- Open one affected app after the update completes.
- Check the app version from the app-name menu → About.
- Create a blank local document with no private information.
- Save it, close it, reopen it, make one change, and save again.
- Open one existing document only after the blank-file test works.
If the exact message is gone and create, edit, and save all work, record the updated version and stop. You do not need to delete caches or rebuild the app.
If it still fails after a verified update
Do not turn an update problem into an identity or data problem. Save:
- macOS version and Mac model
- Office product and exact app version
- installation channel: Microsoft AutoUpdate, App Store, or managed deployment
- the exact remaining message and affected apps
- whether the blank create-and-save test works
- update history and any update error
- whether the Mac is managed by an employer or school
On a managed Mac, contact the help desk. The organization may control Office builds, update timing, licensing, and sign-in. On a personal supported Mac, take the record to Microsoft Support. A fully updated app that still fails no longer fits the simple update-only branch.
Where OmniMend fits
OmniMend 1.7.16 for Apple Silicon Mac can help keep local Mac, application, version, and diagnostic evidence together. It does not update Office, activate a license, replace Microsoft AutoUpdate or the App Store, edit Keychain or license data, or guarantee that this certificate incident caused your error.
Use the OmniMend help article library for related evidence-first guides, or see OmniMend help for product guidance. For this incident, Microsoft's current update channel remains the fix.
Editorial sources
Checked August 6, 2026 against Microsoft Support's current Unknown Error 0x0 and License Not Found known-issue page and Office update guidance for macOS, plus Microsoft Learn's current July 13 certificate, minimum-version, and reduced-functionality documentation. The incident timing was independently corroborated against Kyoto University's July 17 Microsoft 365 service notice. OmniMend added the incident-signature boundary, installation-channel split, safe verification test, unsupported-version stop, privacy limits, and product boundaries.