How To Go Back To Previous Version Of Microsoft Office

You can go back to a previous version of Microsoft Office by reverting a Click-to-Run installation to an earlier update build, or by uninstalling Office and reinstalling an older edition you are licensed to use. The correct method depends on what you want to undo.

Choose between an earlier build and an older edition

An update build and an Office edition are different things. Reversing a recent update keeps the same product but changes its installed build. Moving from a newer standalone Office release to an older release means installing a different product.

If a recent Office update caused a problem

A temporary build rollback may help when a previously working add-in, macro or application starts failing immediately after an update. It does not require uninstalling the entire suite when you use Microsoft's supported Click-to-Run rollback procedure.

Record the exact error and try to reproduce it in a copy of the affected file. If only one add-in fails, check with its developer for a compatible update before changing Office.

If you want an older standalone Office edition

Confirm that you have a licence for that edition and access to its legitimate installer. Do not assume that a newer Office purchase or Microsoft 365 subscription entitles you to install any older standalone release. Check the terms of your licence or ask your organisation's administrator.

Windows does not provide a general Office “Roll Back” button that lets you choose any previous edition. Reinstalling Microsoft 365 through your account also does not automatically restore the build you used before an update.

Check your installation and protect your work

1. Open Word or Excel and select File > Account, or Office Account. Record the product name, version and build number, and the update channel if displayed.
2. Check the information beside the About button for the installation type. Microsoft identifies Click-to-Run installations by their version, build and “Click-to-Run” wording.
3. Save and close your files. Back up important documents, templates, macros and any locally stored Outlook data you need. Confirm that cloud files have finished synchronising.
4. Check that you can sign in to the account associated with your Office licence. Locate purchase records and installation media before removing anything.

Uninstalling Office normally leaves your documents and workbooks in place; it does not delete all your personal files. A backup still protects you against mistakes and gives you untouched copies for compatibility checks.

On a work or school computer, involve your IT administrator before changing versions. Organisation policies may control installation and updates. The Windows steps below do not apply to Office for Mac.

Revert a Click-to-Run installation to an earlier build

Use Microsoft's Office rollback procedure for supported Click-to-Run installations. It does not apply to MSI installations. Choose a build for your product and update channel rather than copying an arbitrary version number from a forum.

1. Set a reminder to review the rollback and restore normal updates.
2. Find the required earlier build in Microsoft's update history for your Office product. Note its full version number.
3. Download the Office Deployment Tool through Microsoft's rollback instructions and extract it to a local folder.
4. In Notepad, create Config.xml in the folder containing the extracted Setup.exe. Use the configuration shown below, replacing the placeholder with your chosen full build number. Save it as an XML file, not Config.xml.txt.
5. Open Command Prompt as administrator, change to that folder and run setup.exe /configure config.xml.
6. Open an Office application and select File > Account > Update Options > Update Now. Allow the process to finish using a reliable internet connection.
7. Confirm the installed build. Temporarily select Update Options > Disable Updates to prevent the problematic update returning while you test.

<Configuration><Updates Enabled="TRUE" TargetVersion="16.0.xxxxx.yyyyy" /></Configuration>

The TargetVersion setting tells Office which build to use. Microsoft's Office Deployment Tool configuration reference explains this setting and how an empty TargetVersion value restores targeting of the latest available version. When the problem is resolved, clear the temporary target using the tool, enable updates and check for updates again. Ask IT to handle this if policies manage your installation.

Reinstall an older standalone Office edition

Secure the installer and confirm compatibility with your operating system before uninstalling your current suite. Use Microsoft account downloads, original installation media or your organisation's authorised deployment source.

1. Sign in to the Microsoft account associated with the older purchase and check whether installation is available. For an organisation licence, obtain the correct package from IT.
2. Close Office applications. For a standard desktop installation, open Control Panel > Programs > Programs and Features, select Microsoft Office or Microsoft 365, and choose Uninstall.
3. Follow the removal prompts and restart if requested. If removal fails or your installation type differs, follow Microsoft's uninstall instructions.
4. Run the older edition's installer and follow its prompts. Activate using the account or product key appropriate to that edition.
5. Open copies of representative files and test the features, add-ins and printing tasks you rely on before returning to normal work.

Resolve activation before relying on the installation

If a retail key has already been redeemed, Microsoft directs you to reinstall through the associated Microsoft account. Re-entering the same key is not always necessary.

If you need to investigate an existing installation, our guide to finding an Office product key using Command Prompt provides related background. Keep your purchase records and account details available rather than relying solely on key recovery.

For installations that use command-line licensing tools, see how to activate Microsoft Office using CMD. Activation must match your licence and installed edition; it does not grant rights to another product.

Check compatibility and plan your next update

An older edition may lack features used in newer documents, and an older build may omit security fixes. Check Microsoft's support information for the exact product before committing to it. Keep supported installations updated; treat a build rollback as a temporary response to a specific fault.

If the original problem persists, record the build and test results before making further changes. The Microsoft Office guides offer help with related setup and troubleshooting tasks.

Start by opening File > Account and writing down your product name and build number. Use those details to choose the appropriate rollback or reinstall path.