19-04-2021

Microsoft Office 2016 Install Stuck On Running Package Scripts

You can't install Office 2016 or Office 2013 on computers running Windows Vista or Windows XP as these operating systems don't meet the system requirements for Office. Attempting to install Office on a computer running an unsupported operating system will result in an error.
Dears Shall you help me I used to use OffScrub VBScript for office to automatic uninstall now i need to uninstall Office 2016 shall any one support me by providing this for me.

(BTW, why MS didn't configure the install to DETECT the version of Windows rather than default to the 32-bit version of Office is beyond my comprehension). They still recommend 32-bit unless you're working on huge workbooks because of plugin compatibility. Personally, I install the 64-bit version across the board and haven't had many issues.

-->

Summary: Plan for multilanguage setup, and customization and proofing tools for Office 2016.

Support for multiple languages and languages other than the default are provided through language accessory packs (LAPs) and language interface packs (LIPs) that you install. Language accessory packs (LAPs) let you see ribbon or menu items, commands, Help, and proofing tools like the spelling checker, grammar checker, and thesaurus in a translated version of Office for all Office applications. Language interface packs (LIPs) only change the language for the ribbon and commands for some Office applications.

To deploy Office 2016 in multiple languages, you must plan carefully. This article discusses the planning considerations for setup and the customizations that you can make when you install language packs or proofing tools.

Important

This article describes methods of deploying and managing language packs for versions of Office 2016 that use the Windows Installer (MSI) installation technology, which are available for enterprises through volume licensing. If you have an Office subscription and you're deploying Microsoft 365 Apps, which uses the Click-to-Run installation technology, see Overview of deploying languages for Microsoft 365 Apps.

Plan setup of Office 2016 multilanguage deployment

The language-neutral design of Office 2016 helps simplify the deployment of Office products in multiple languages. Instead of creating a series of installations, you enable setup to coordinate a single installation of multiple language versions.

All language-specific components for a particular language are contained in an Office 2016 Language Pack. Each Office 2016 Language Pack includes language-specific folders for all Office 2016 products that are available in that language. Folders are identified by a language tag that is appended to the folder name. For a complete list of language tags, see Language identifiers and OptionState Id values in Office 2016.

You install all the Office 2016 Language Packs that you want at the same time by copying them to a network installation point that contains at least one complete Office 2016 product. By default, setup automatically installs the language version that matches the Windows user locale that is set on each user's computer. Or, you can override this default behavior and manage the distribution of multiple language versions manually. For example, you can perform any of the following tasks:

Install more than one language on a single computer
Specify which languages to install on users' computers, regardless of the language of the operating system that is specified by the user locale
Specify custom settings once and then apply them to all language versions that you deploy in your organization
Deploy different languages to different groups of users
Deploy the Microsoft Office 2016 proofing tools for additional languages

Each Office 2016 Language Pack contains the proofing tools for one or more additional languages. For example, the Office 2016 Language Pack - Danish contains the proofing tools for English and German, in addition to Danish. All Office 2016 Language Packs contain the proofing tools for English. For more information about proofing tools, see Plan for Office proofing tools. To determine which companion proofing languages are included in an Office 2016 Language Pack, see Companion proofing languages for Office 2016.

Before setup installs a language version of an Office 2016 product, setup determines whether the user has the required operating system support for that language. Setup stops the installation if there is no support. For example, if a user has not enabled support for East Asian languages, setup does not install the Japanese version of Office 2016.

Determine the languages that you want before you begin your deployment. There are special steps that you must take to include additional languages if you have to change users' configurations after the initial deployment. For more information, see Add or remove language packs after deployment of Office 2016.

Understanding the setup logic for Shell UI language

When you deploy the Office 2016 from a network installation point that contains more than one language version, setup must determine which language to use for the setup user interface. By default, setup uses that same language for the Office 2016 installation language and for the shell user interface (Shell UI). The Shell UI includes core elements of Office 2016 that register with the operating system, such as file name extensions, Tool Tips, and right-click menu items.

Setup always installs Office 2016 in the language of the Shell UI, in addition to any other installation languages. For example, if the Shell UI is set to French, the user can select additional installation languages on the Languages tab. However, the user cannot remove French. You specify the language for the Shell UI by modifying a configuration file, Config.xml.

If you want to install only one language version of Office 2016 on each client computer and if you do not specify any additional languages in the configuration file, setup uses the following logic to determine which language to use:

Setup matches the language of the user locale.
If there is no match, setup looks for a close match. For example, if the user locale is set to English (Canada), setup installs Office 2016 in English (U.S).
If there is no close match, setup looks for a language in the following subkey in the Windows registry:
HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonLanguageResources
If the InstallLanguage entry has not been added to the LanguageResources subkey and set to a particular language (LCID), setup either prompts the user to select a language during an interactive installation, or it stops a silent installation.

If you are installing multiple languages, the language of the setup user interface follows the logic described previously. However, the languages that are installed on the computer and the language of the Shell UI are determined by the entries you specify in Config.xml.

For specific steps on how to customize setup for different scenarios, including how to modify Config.xml, see applicable sections in Customize language setup and settings for Office 2016:

Plan language customizations for Office

When a user starts an Office 2016 application for the first time, setup applies default settings that match the language that is installed on the computer and the language that is specified by the Windows user locale setting.

Four main language settings affect the way users work with Office 2016:

Primary editing language When more than one language version of Office 2016 is installed on the computer, this setting determines the language in which users work with Office applications and documents.
Enabled editing languages Users can specify more than one language for editing Office 2016 documents. Depending on the languages selected, this setting might require the user to install additional proofing tools.
User interface language This setting determines the language in which the user interface is displayed.
Help language This setting determines the language in which users view Help topics.

You can configure these language settings for users in advance. If you specify custom language settings when you install Office, by applying a setup customization file (.msp file) or by setting policies, Office 2016 does not overwrite your settings with the default settings when users start the applications for the first time.

Customizing language settings for Office

You configure language settings by using one of the following methods:

Group Policy Group Policy settings enforce default language settings. Users in your organization cannot permanently change settings that are managed by Group Policy. The settings are reapplied every time that the user logs on.
Office Customization Tool (OCT) You use the OCT to create a setup customization file (.msp file) that setup applies during the installation. Settings specified in the OCT are the default settings. Users can change the settings after the installation.
Language Settings tool If you do not enforce language settings by policy, users who work in Office 2016 applications can use the Language Settings tool to change their language settings.

For specific steps on how to use these tools to customize Office 2016 for multiple language deployments, see Customize language settings.

You can also configure language-specific settings, such as number format, that are related to user locale. For more information, see Customize language-specific settings that are related to user locale.

Plan for Office proofing tools

Proofing tools let users edit documents in 52 languages. Depending on the language, these editing tools might include spelling and grammar checkers, thesauruses, and hyphenators. Proofing tools might also include language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.

The Proofing Tools 2016 ISO provides a single resource from which you can install any of the proofing tools. You can install proofing tools on a local computer or deploy tools to a group of users. You can also customize and install the tools for one user or all users in your organization.

Determining the method to deploy proofing tools

You can deploy additional proofing tools for users who have to edit documents in languages other than those that are already installed on their computers. You can deploy additional proofing tools from either of these sources:

Office 2016 Language Pack Use this option if users want both the user interface and the proofing tools for a specific language. Often, one language pack can provide all the proofing tool languages that you want. The companion proofing tool languages that are contained in a language pack mirror those of what's contained in language versions of Office 2016. You can also use the Office Multilanguage Pack which contains all of the Office language packs.
For a list of companion languages, see Companion proofing languages for Office 2016. If a language pack has all the proofing tool languages that you want, deploy a language pack by using the instructions that fit your scenario in Customize language setup and settings for Office 2016.
Proofing Tools 2016 This product contains the proofing tools for all languages that are available with Office 2016. Use this option if you have to have proofing tools that are not included in the set of companion languages for any languages that are installed or included in an additional language pack that you could install.

The hard disk space requirement to install proofing tools is 1 gigabyte (GB). However, the overall disk space depends on whether you deploy proofing tools from a language pack or from the proofing tools. As with most products in the Office 2016, the complete Proofing Tools 2016 package is cached to the local installation source (LIS).

Proofing tools do not include bilingual dictionaries or word breakers. Those tools are part of the language version or language pack.

Individual Office Language Packs, the Office Multilanguage Pack, and Proofing Tools 2016 are available through Microsoft Volume Licensing programs.

For instructions on downloading language packs and proofing tools, see Download language packs, language interface packs, and proofing tools for volume license versions of Office.

Precaching the local installation source for the Office 2016 proofing tools

When you deploy the Office 2016 proofing tools, setup creates a local installation source on the user's computer — a copy of the compressed source files for the Office 2016 proofing tools. After the files are copied to the user's computer, setup completes the installation from the local installation source. You can minimize the load on the network by deploying the local installation source separately, before you deploy the Office 2016 proofing tools. For information about how to cache the local installation source for the Office proofing tools, see Precache the local installation source for Office 2010. (Although this article is for an earlier version of Office, the information also applies to Office 2016.) Use the Setup.exe and Config.xml files from the ProofKit.WW folder from the Proofing Tools 2016 ISO. For instructions on downloading the Proofing Tools 2016 ISO, see Download language packs, language interface packs, and proofing tools for volume license versions of Office.

Uninstall Microsoft Office from Control Panel or Settings

Of course, the first method that you should always use to uninstall software such as Microsoft Office is from the official uninstaller. This will be found in Programs and Features in the Control Panel or Apps in Windows 10 Settings.

Select the version of Microsoft Office from the list and click the Uninstall button. You will be asked to confirm if you want to remove Microsoft Office from your computer. Click either the Yes or Uninstall button to proceed with the uninstallation.

If the built-in uninstaller fails to remove Microsoft Office from your computer, then refer to other methods shown below.

Remove Microsoft Office using the Setup File

Running the setup executable file that is used for installation can also trigger the option to remove the Microsoft Office installed on the computer. Open the optical drive letter or disc image to view where the install files are located.

Running the setup.exe will open a window giving you the option to add or remove features, repair, remove, or enter a product key.

Uninstalling from the Setup executable on the disk doesn’t work for all versions of Office. We tested the installers for 2013, 2010, and 2007 and they do have the remove option, 2016 didn’t have it.

Uninstall Office with the Microsoft Office Uninstall Support Tool

After discontinuing or making some other Office uninstall tools unavailable, Microsoft has come out with another utility to handle the task. The Office uninstall support tool says it can completely uninstall Office 2007, 2010, 2013, 2016, 2019 and various versions of Office 365. It’s worth noting the tool did not detect our Office 2007 install during testing but did work with 2010, 2013 and 2016.

Download the tool from Option 2 on the Microsoft webpage and double click it, .NET Framework 4.6 or higher is required on Windows 7. It will first install the Microsoft Support and Recovery Assistant of which the uninstall support tool is a part. Run the executable again and select the version of Office that has been detected, then click Next. Read the warning, check the box and click Next.

After some minutes, the process will complete and you will be prompted that the computer is going to be restarted.

The tool will popup after a reboot with the results of the uninstall process with some links to help you reinstall Office if you don’t have a CD/DVD/ISO/IMG with the install files. The Microsoft Support and Recovery Assistant will need to be uninstalled from Programs and Features or Settings > Apps.

Download the Microsoft Uninstall Support Tool

Delete Microsoft Office using FixIt

FixIt used to be a useful set of free troubleshooting tools by Microsoft to repair a variety of common problems including uninstalling Office. Sadly it was discontinued in 2018 in favor of the built in Windows troubleshooters. FixIt’s came as small tools that each focused on one or two specific tasks so you will need to use the correct version for your installed version of Microsoft Office and Windows.

To use one of these tools, download it and double click on the diagcab or MSI file. All you have to do is essentially click Yes or the Next button a few times while the tool attempts to find and completely remove the Office installation.

Uninstall Office 2003, 2007, 2010, 2013 or 2016

From any Windows: O15CTRRemovev2.diagcab

Uninstall Office 2013, 2016 or Office 365

From any Windows: O15CTRRemove.diagcab

Uninstall Office 2010

From Windows 8/10: MicrosoftFixit20055.mini.diagcab
From Windows 7 and below: MicrosoftFixit50450.msi

Uninstall Office 2007:

From Windows 8/10: MicrosoftFixit20052.mini.diagcab
From Windows 7 and below: MicrosoftFixit50154.msi

Uninstall Office 2003:

From Windows 8/10: MicrosoftFixit20054.mini.diagcab
From Windows 7 and below: MicrosoftFixit50416.msi

The tool might scan for Office a couple of times before finishing but just keep pressing Next until you reach the completed window and the Close button, then restart the computer.

Clean Up Microsoft Office using OffScrub VBScript

OffScrub is an Office Removal Utility created in VBScript by Microsoft that is found in many of the Fix it tools mentioned above. You’d have to extract the MSI or diagcab file of the Fix it tool to obtain the OffScrub .vbs file using a third party tool such 7-Zip (for the diagcab files only) or Universal Extractor. It’s not found in the top link of the FixIt tools above but is available in the others.

Some of the advantages of using OffScrub are the ability to remove Office standalone products which you would not be able to do if you were running the Fixit tool and also the possibility of automation using the command line. For the more advanced user, you can also see the different removal stages in real time which could be helpful in pinpointing the cause of uninstallation problems.

Erase Microsoft Office using Remove Office 2007 / 2010

A software developer called “Refuse to Suffer” created two free dedicated tools to clean up Microsoft Office 2007 and 2010 when the normal uninstallation procedure fails. The developer and its website are gone now but the tools still exist. All you need to do is run the programs as admin and click the Go button.

There are a few things you should know before using the Remove Office 2007 or Remove Office 2010 tool. First of all, the tool automatically restarts your computer after completing the removal process so make sure you’ve already saved and closed any other running files. Also, it should not be used when you have two different versions of Microsoft Office installed on the computer because the tool isn’t programmed to keep the important commonly shared files.

Download Remove Office 2007 / Download Remove Office 2010

Get rid of Microsoft Office using a Third Party Uninstall Utility

While there are many third party software uninstaller utilities, we recommend one of the best around which is Revo Uninstaller Pro. It’s reliable and has a feature to analyze leftover files/folders/registry entries based on a given path, and automatically creates a backup so that the forced uninstall can be restored. The only drawback is Revo Uninstaller Pro is shareware but it offers a 30 day fully functional trial.

1. Download Revo Uninstaller Pro and install.

2. Run Revo Uninstaller Pro and double click the Office entry in the list. If you can’t find an entry for Office, click the “Forced Uninstall” button.

3. If you chose Forced Uninstall, enter the program name which is Microsoft Office, click the “Browse for” button and select Folder, then browse to the Microsoft Office folder which is normally installed in “Program Files” or “Program Files (x86)”. If it finds any uninstallers connected to Office they will be listed and you can choose one to try and uninstall with it. Click Next.

4. Revo Uninstaller Pro will create a registry backup and a system restore point. It will first attempt to uninstall Office with any selected official uninstaller. Click Scan and the program will scan for leftover files, folders and registry items which you can review and delete if you want.

If most or all of the installation is still on the system, Revo uninstaller could find thousands of registry entries and files. In the event anything is still leftover from an Office install after going through the process once, you can simply run Revo Uninstaller Pro again and select the remaining files in a forced uninstall.

Last Resort: Uninstall Microsoft Office Manually

If none of the above methods have helped to completely remove Office from your computer, there may be little choice than to try and manually remove it from the system yourself. There are separate guides on the Microsoft website for uninstalling Office 2007, 2010, 2013 and one joint guide for 2016 and newer versions.

The instructions are complex and comprehensive so will take a lot of time and patience. They work with Windows 7, 8.1 and 10 along with versions of Office that are Click-to-Run, MSI installer or Windows Store versions. You will be guided through removing files, folders, scheduled tasks, services, Start menu entries, and registry keys/values. It’s not for the faint of heart but maybe your only option left to get rid of your Office install.

Visit Microsoft Manually Uninstall Office Page

You might also like:

Automatically Diagnose and Repair Microsoft Office 2003, 2007, 2010, 2013, 2016, 365Fix Microsoft Office Word Has Not Been Installed For The Current User ErrorAuto Enter Product Key When Installing Microsoft Office XP, 2003, 2007, 2010 and 2013Change or Remove Button Missing at Control Panel Add or Remove Programs3 Ways to Add Classic Menus and Buttons to Microsoft Office

Good day sir

I couldn’t uninstall Microsoft office 10 from my windows 7. Ive tried uninstalling it with your microsft toolkit and etc. but it wouldn’t work.. mirocsoft office couldn’t be found. or error..

please kindly help me

Dingy2 months ago

Thank your for these tips.
The newest tool did not work on my old Windows 7 SP1 laptop with MS Office 2013 click and run. It would spin for ever after recognizing the installed package.
Using the second option worked like a charm.

It is Working… Fix It tool thankuh!!!

nik10 months ago

I’m desperate…. Dot a licence to use office 365 but couldnt install it. I get error 30033-1011(“check internet connection and space on your HD” error).
After searching for ages, using every tool/uninstall procedure there was written on Microsoft sites, deleting registry, doing system restore I’m clueless…

Microsoft Office 2016 Install Stuck On Running Package Scripts Without

Any ideas?

Thanks a million. Tried all ways to remove remnants of Office 2007 but to no avail. Then I tried your suggestion to use FixIt tool. Great job…fixed it in first attempt. Really appreciate your help

Zinko6 months ago

I also thank you for your comment.

Just an FYI for Raymond.cc readers:
the Microsoft Office Uninstall Support Tool doesn’t seem to remove all versions of Office 365. The installer for the tool downloads however the installer itself had to be rerun multiple times. It seems it could be regional as its downloading/updating from the azure cloud. Once it eventually installed it didn’t detect any products. It’s possible its may be some sort of OEM Office 365 version (HP laptops) however the software also didn’t appear under Control Panel or Apps & Features.

The O15CTRRemove.diagcab also didn’t work for us so not sure if there is a new breed of Office 365 that Micro$haft is now installing.
Thank you for posting this here admin.

Not a fan of Microsoft since

potater2210 months ago

Hello, am encountering this same problem. What can be done to solve this problem so that I can install a different Office version?

Thanks a lot for putting up these solutions. It is helpful!

TOM EUTSLER3 years ago

Before I remove office 2003, what do I need to save in Outlook ? and how
such as e mail addresses etc . Maybe .pst ?

The only method that actually worked for me is Microsoft Toolkit 2.6.2. It is also good for many other problems with Office and Windows.

nikita kashyap3 years ago

thanks buddy revo pro worked for me…

Thanks dear

cfgeagle4 years ago

I was having problem for so long, looking for help everywhere, all the result was sending me to programs uninstall, basic stuff, but I couldn’t see the Office files from the beginning so I didn’t know how or where to look to uninstall, I found this after much search, and I used Fix-it. Unbelievable, it runs the check and start the fixing part, was quick and soon went to the end where I just need to exit from the Command Prompt . Run the install program and done, it was running smooth again. Thank you for this instruction, simple, clear, to the point, and once in it, clear to follow, great support, thank you very much.

Revo did not properly completely removed office 2010, nor 2016, then occurring error when launching office setup.
I had to use microsoft toolkit (>2.4) to uninstall office 2010 (using offscrub), then reboot in order to be able to access office setup dialog and choose custom options.

flotar4 years ago

Revo Uninstaller Pro worked fine on WINDOWS 10, when trying to uninstall OFFICE STANDARD 2007.
Thank you very much :)

Thanks you so much, you help me. I was a problem with my shit office and I couldn’t unistall that, but thanks to you for share your knowlodge I found a solution

Dan4 years ago

Raymond, do you have a solution for removinguninstalling Office XP without access to PRO.MSI file? Thanks!

Microsoft Office 2016 Install Stuck On Running Package Scripts Pastebin

For windows 10 nothing of the above FixIt based methods works, as FixIt is not supported.

Go here for your remedy

whitepages.unlimitedviz.com/2010/05/how-to-completely-remove-all-traces-of-office-2010-from-your-system/

You’ll find vbs scripts for entirely removing all aspects of Office 2010 / Office 2007 from your Windows.
Works under Win10 like a charm.

Before running, add the following vbs snippet at the top of the vbs file, after
Option Explicit
in order to elevate the script permissions, required to edit the registry.

If Not WScript.Arguments.Named.Exists(“elevate”) Then
CreateObject(“Shell.Application”).ShellExecute WScript.FullName _
, WScript.ScriptFullName & ” /elevate”, “”, “runas”, 1
WScript.Quit
End If

For your convenience, here is a direct d/l link:
whitepages.blob.core.windows.net/cdn/2010/05/OfficeScrubbers4.zip

Tiviacz4 years ago

Erase Microsoft Office Using Remove Office 2010
Working for me :)

Thank u Raymond… for this tool , this help me to remove corrupted MS office 2010 :-)

Fabricio9 years ago

Thank you Raymond!!!

Thank you for the millionth time Raymond – you always but ALWAYS come up with the hidden gems ! You are essential reading for the small IT business like mine. I have added these tools to my kit.

ron159 years ago

Thanks for the article Raymond, comes handy in case of “emergency”

Thank you Raymond ,you are pro…

billy139 years ago