Office 2019 is compatible with Windows 10 and the three most recent versions of macOS. It can't be installed in Windows 7 and Windows 8/8.1. You must be using Windows 10 operating system to install Office 2019. Nov 08, 2018 After successfully installing office 2019 on windows 7, activating it - Office 2019 does not update to the latest version. Do you also have this problem? I think this is related to the update channel whether monthly or semi-annual!! Aug 19, 2020 When you are using an Microsoft 365 (formerly Office 365) installation or a Click-to-Run installation of Office 2013, Office 2016 or Office 2019, then the updates will not be offered via Windows Update but will be installed automatically. Office 365, on the other hand, currently works with Windows 7, 8, and 10, but also uses that three-version shifting scheme for macOS. How Does Office 2019 Compare to Office 2016? Office 2019 does offer some of the new features incorporated into Office 365 since the release of Office 2016. This includes features like the following. 1) Repair Office 365 or Office 2019 In Windows 7 or 8 locate “Control Panel” “Programs” “Programs and Features” Highlight “ Office 365 ProPlus ” (do not click on it) and select the “ Change ” button Select “ Quick Repair “.
-->To configure and perform deployments of volume licensed versions of Office 2019, including Project and Visio, for users in your organization, you use the Office Deployment Tool (ODT). The Office Customization Tool (OCT) that you previously used for Windows Installer (MSI) is no longer used.
The installation files for Office 2019 are available on the Office Content Delivery Network (CDN) on the internet instead of on the Volume Licensing Service Center (VLSC). You can install Office 2019 directly from the Office CDN. Or, you can download the installation files from the Office CDN to a location on your local network, such as a shared folder, and install Office 2019 from that location. You can use different methods for different sets of computers in your organization. Whichever method you choose, you use the ODT.
Installing directly from the Office CDN requires the least amount of administrative effort and is recommended. But you might have constraints that prevent you from installing directly from the internet. For example, some computers might not have connectivity to the internet or you may have limited bandwidth to the internet.
Download the Office Deployment Tool from the Microsoft Download Center
The Office Deployment Tool is a free download from the Microsoft Download Center. We recommend that you always download and use the most current version of the ODT.
After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you are finished, you should have several files: setup.exe and some sample configuration.xml files. For an Office 2019-specific sample, see Sample configuration.xml file to use with the Office Deployment Tool.
The setup.exe file is the ODT and is a command-line tool that supports downloading and installing Office 2019. The configuration.xml files are sample files to get you started. You use the configuration.xml file to provide settings for the ODT to use when downloading or installing Office 2019. The configuration.xml is a simple xml file that can be created and edited in any text editor, such as Notepad. You can name the file anything that you want, as long as it retains the xml file extension.
Create the configuration.xml
Once you have a copy of the ODT, you need to create a configuration.xml file. You can create multiple configuration.xml files to be used with the ODT. For example, you would create a configuration.xml file to download and install the 64-bit version of Office Professional Plus 2019 in English and a different configuration.xml file to install the 32-bit version of Visio Professional 2019 in French. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.
Tip
Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool. Please note that this is different than the Office Customization Tool that you might have used in the past to install volume licensed versions of Office that used Windows Installer (MSI) as the installation technology.
There are a series of settings in the configuration.xml file that you configure to customize the Office 2019 download or installation. The following table lists the most common settings to configure in the configuration.xml file.
| Configuration | configuration.xml setting | Additional information |
|---|---|---|
| Where to download the Office installation files to and where to install Office from For example, servershare (a shared folder on your local network) | SourcePath | If you don’t specify a SourcePath when using the ODT to install Office, the ODT looks for the installation files in the folder it’s located in. If it doesn’t find the Office installation files there, it goes to the Office CDN to get the installation files. We recommend that you install Office directly from the Office CDN, if internet connectivity and network bandwidth make that possible. |
| Which products to download or install For example, Office Professional Plus 2019 | Product ID | Valid values for volume licensed versions of Office 2019 include the following: - ProPlus2019Volume - Standard2019Volume - ProjectPro2019Volume - ProjectStd2019Volume - VisioPro2019Volume - VisioStd2019Volume For a list of Product IDs for other volume licensed versions of Office 2019, such as Access 2019, see Product IDs that are supported by the Office Deployment Tool for Click-to-Run. |
| Use Key Management Service (KMS) to activate Office 2019 | PIDKEY | Enter the Generic Volume License Key (GVLK) for KMS activation. |
| Use Multiple Activation (MAK) to activate Office 2019 | PIDKEY | Enter the product key for MAK activation. |
| Which languages to download or install For example, English (en-us) and French (fr-fr). | Language ID | You can install multiple languages at the same time you’re Installing Office 2019, or you can install them later. For more information, see Deploy languages for Office 2019. |
| Which proofing tools to install | Product ID | The Product ID is 'ProofingTools' and is used in combination with the Language ID. For more information, see Deploy languages for Office 2019. |
| Which edition of Office 2019 to download or install. For example, the 64-bit version. | OfficeClientEdition | Valid xml values are '32' and '64.' All Office products on the computer must be of the same architecture. You can’t have both 32-bit and 64-bit Office products installed on the same computer. We recommend 64-bit on computers that have 4 gb or more of memory. But you should assess application compatibility and other factors that might require you to use the 32-bit version. For more information, see Choose between the 64-bit or 32-bit version of Office. |
| Which apps to install For example, all apps except Publisher. | ExcludeApp | By default, all apps included in Office Professional Plus 2019 are installed. For example, to not install Publisher, you can include the following line in your configuration.xml: <ExcludeApp /> For more information, see ExcludeApp element. |
| Where to get security and quality updates from. For example, directly from the Office CDN on the internet. | UpdatePath | The default is to get updates directly from the Office CDN on the internet. This is recommended and requires the least amount of administrative effort. But if you need to update computers that don’t have connectivity to the internet, you can specify that Office gets updates, for example, from a shared folder on your local network. But this means that you must download the updates from the Office CDN and copy them to the shared folder. For more information, see Update Office 2019 (for IT Pros). |
| Which update channel to install from and get updates from | Channel | Office uses the concept of update channels to determine which updates an installed version of Office receives. For more information, see Update channel for Office 2019. |
| Whether to remove previous Windows Installer (MSI) versions of Office before installing Office 2019 | RemoveMSI | This is recommended. For more information, see Remove existing versions of Office before installing Office 2019. |
Tip
More information about these configuration.xml settings is available here: Configuration options for the Office Deployment Tool. Keep in mind that not all the information in that article applies to Office 2019. For example, the settings related to shared computer activation, such as SharedComputerLicensing and SCLCacheOverride, don’t apply to Office 2019.
Sample configuration.xml file to use with the Office Deployment Tool
The following is a sample configuration.xml file that can be used to either download or install the 64-bit version of Office Professional Plus 2019 in English using a shared folder on your local network and activate by using MAK. If you’re using this configuration.xml to install Office 2019, previous Windows Installer (MSI) versions of Office are removed as part of the installation process. Also, even though it’s not specified in the configuration.xml file, updates are automatically enabled and are configured to come directly from the Office CDN, because those are the default settings.
For the PIDKEY, replace #####-#####-#####-#####-##### with your MAK client activation key.
Remove existing versions of Office before installing Office 2019
We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office 2019. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the Office Deployment Tool and specify the RemoveMSI element in your configuration.xml file.
There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office 2019.
- Uninstall all Office products on the computer.
- Identify any existing language resources, like language packs, and install the same languages.
- Keep some Office products and uninstall all other Office products on the computer.
RemoveMSI can be used to uninstall 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).
For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though this article is about Microsoft 365 Apps, most of the information also applies to volume licensed versions of Office 2019.
Download the Office 2019 installation files
Once you have a copy of the ODT and have created your configuration.xml file, you can download the Office 2019 installation files to your local network. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type this command:
If you have saved the configuration.xml file with a different name, use that name in the command.
It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt.
If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration.xml file. You should see a folder named “Office” with a subfolder named “Data.” There will also be a folder named with the version number of the download. For example, 16.0.10336.20044. Which files you see and the names of the files depend on whether you are downloading the 32-bit or 64-bit version of Office and which languages you are downloading.
Here some additional details about downloading Office 2019 installation files:
- You must download the 32-bit and 64-bit versions separately.
- All volume licensed versions of Office 2019 – such as Office Professional Plus 2019, Visio Professional 2019, and Project Professional 2019 – are included in the same download, regardless of which products you specify in the configuration.xml file. This helps you save disk space on your local network. The core files for the Office 2019 products are in the stream.x86.x-none.dat or stream.x64.x-none-dat file, depending if it’s the 32-bit or 64-bit version of Office.
Install Office 2019 by using the Office Deployment Tool
Once you have a copy of the ODT and have created your configuration.xml file (and downloaded the Office 2019 installation files to your local network, if necessary), you can install Office 2019. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type the following command:
If you have saved the configuration.xml file with a different name, use that name in the command.
Once the installation is complete, you are returned to a command prompt and you can go open Office 2019 programs you’ve installed.
Install Office 2019 by using Microsoft Endpoint Configuration Manager
You can also use Microsoft Endpoint Configuration Manager to deploy volume licensed versions of Office 2019. Configuration Manager (current branch) has a wizard that steps you through the process and builds the configuration.xml file for you. Earlier versions of Configuration Manager require you to download the ODT and create your own configuration.xml file.
Configuration Manager (current branch): If you’re using Configuration Manager (current branch), you can use the Office 365 Client Installation wizard to deploy Office 2019. You must be using at least version 1710, but version 1806 is recommended. You’ll see an entry for Office Professional Plus 2019 in the Office 365 Client Installation wizard. On that same page, you can also select to install Project and Visio.
System Center 2012 R2 Configuration Manager: If you’re using System Center 2012 R2 Configuration Manager, the steps are different and much more manual. First you need to get a copy of the ODT from the Microsoft Download Center and create the appropriate configuration.xml file for your deployment. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it.
Deploy languages for Office 2019
You can use the ODT and the configuration.xml file to install volume licensed versions of Office 2019, including Project and Visio, in multiple languages. For more details, see Language element.
You can also just install proofing tools by specifying the Product ID as 'ProofingTools' in your configuration.xml file along with the appropriate Language IDs. Proofing tools packages, which are a new capability for Office 2019, are much smaller than full language packs. Consider deploying proofing tools in cases where users work with documents in multiple languages but don’t need the Office product UI in all those languages. The proofing tools can be installed at the same time you’re installing Office 2019, or you can install them later. They can also be installed whether or not the language pack for a given language is installed.
If you're upgrading from a Windows Installer (MSI) version of Office, you can get Click-to-Run versions of the same language resources – for example, language packs, language interface packs, or proofing tools – installed when you deploy Office 2019. For more information, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though this article is about Microsoft 365 Apps, most of the information also applies to volume licensed versions of Office 2019.
Related topics
Home → End User Setup → Before You Install → Windows and Office Versions Supported by Palisade
International language versions of this article:
Which software platforms or operating systems are supported by Palisade?
Palisade's latest release, 8.0, is supported on Microsoft Office 2010 and newer, running on Windows 7 and newer. For older releases, see the compatibility charts below.
Please note: Some functions in our software may seem to work in some Office or Windows version that are not supported. But some functions will not work, or not work correctly, not necessarily with an obvious failure mode. We strongly recommend against running our software with unsupported Office or Windows versions, and we cannot assist with troubleshooting on unsupported platforms.
If you have an older version and need to upgrade for compatibility with Microsoft Office or Windows, please see Upgrading Palisade Software. Customers with a current maintenance agreement can receive the upgrade to our latest versions at no charge; others please contact your Palisade sales manager.
Hardware:
Please see Hardware Requirements or Recommendations.
Microsoft Office Versions:
Palisade products with these version numbers require Microsoft Office for Windows to be installed on the same computer. Mac users, please see @RISK on the Apple Mac. Lotus, OpenOffice, LibreOffice, and StarOffice products are not supported.
Don't know your Excel version? See Which Version of Excel Am I Running?
| Palisade version: | 8.0 | 7.6 7.5 7.0 | 6.3 6.2 6.1 | 6.0 | 5.7 | 5.5.1 | 5.5.0 5.0 | 4.5.7 1.0.9 | 4.1.4 |
|---|---|---|---|---|---|---|---|---|---|
(1)With Office 365 or Office 2019, we strongly encourage you to upgrade to the latest release of Palisade software for full compatibility. For Office 365 deployments, see Office 365 with Palisade Software. (2)With @RISK 7.0 only, if you have Project 2007 you may need to apply the patch mentioned in this article. (3)@RISK for Project 4.1.4 works with Project 2000–2003; 4.1.4r2 works with Project 2000–2007; and 4.1.4r3 works with Project 2003, 2007, and 32-bit 2010. To check your sub-version of @RISK for Project within 4.1.4, navigate to the Palisade installation folder, then to subfolder RISKPJ41, and double-click the Version History file. | |||||||||
| Office 365 Excel (except pre-release and 'Office Insider' builds) | (1) | (1) | |||||||
| Excel 2019 | (1) | (1) | |||||||
| Excel 2016 | ✔ | ✔ | |||||||
| Excel 2013 32- or 64-bit | ✔ | ✔ | ✔ | ||||||
| Excel 2010 64-bit | ✔ | ✔ | ✔ | ✔ | ✔ | ||||
| Excel 2010 32-bit | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Excel 2007 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Excel 2003 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
| Excel 2002/XP | ✔ | ✔ | ✔ | ✔ | |||||
| Excel 2000 | ✔ | ✔ | ✔ | ✔ | |||||
| Office 365 Project (except pre-release and 'Office Insider' builds) | (1) | ||||||||
| Project 2019 | (1) | ||||||||
| Project 2016, build 16.0.4229.1002 or newer | ✔ | ||||||||
| Project 2013 32- or 64-bit | ✔ | ✔ | |||||||
| Project 2010 64-bit | ✔ | ✔ | |||||||
| Project 2010 32-bit | ✔ | ✔ | ✔ | (3) | |||||
| Project 2007 | (2) | ✔ | ✔ | ||||||
| Project 2003 | ✔ | ✔ | |||||||
| Project 2002/XP | |||||||||
| Project 2000 | |||||||||
Notes:
- In releases 6.0 and newer, one Palisade installer works with both 32-bit Excel and 64-bit Excel. Excel is required; Project is optional.
- See also: Recommended Option Settings for Excel.
Windows Versions for End-User Software:
(For license server software, please see License Server System Requirements.)
| Palisade version: | 8.0 7.5.2 | 7.5.1 7.5.0 7.0.1 7.0.0 | 6.3 6.2 6.1 6.0 | 5.7 | 5.5 5.0 | @RISK for Project 4.1.4r3 4.1.4r2 4.1.4 | RDK/BDK/ EDK/RODK 4.1.2 |
|---|---|---|---|---|---|---|---|
| Windows 10 through version 1903 | ✔ | ✔ | ✔ | ||||
| Windows 8.1 | ✔ | ✔ | ✔ | ✔ | |||
| Windows 8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Windows 7 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Windows Vista | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Windows XP | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
| Windows Server | See notes below. | ||||||
| Windows RT | Not supported. | ||||||
Notes:
- Windows Server versions are not listed in the chart, because we have not done extended Quality Assurance of our end-user software with any Windows Server version. However, we are not aware of any incompatibilities between our end-user software and Windows Server 2008, 2012, 2016, or 2019 (through version 1903).
- Vista and newer: Right-click the installer and select Run as Administrator; simply double-clicking may not work. After install and activation, the applications do not need admin rights.
- All of our installers work in 32-bit and 64-bit Windows; but the RDK, BDK, EDK, and RODK must run in 32-bit processes. In 64-bit Windows, all products install in C:Program Files (x86).
- Windows 8.1 with our 6.0 and 6.1 installers: Please see Installing Palisade Software 6.0 or 6.1 in Windows 8.1 before installing.
- Windows 8 with our 5.7 and 6.0 installers: Please see Installing Palisade Software 5.7 or 6.0 in Windows 8 before installing.
If you have a system with a standalone or enterprise version of our software, before you upgrade Windows, please deactivate the software to preserve the license; then reactivate it after upgrading. See Transferring Standalone Software 6.x/7.x to a New Computer or Transferring Standalone Software 5.x to a New Computer for the transfer procedure.
Windows Versions for License Server Software:
Starting with release 7.5.2, our license server software requires Windows Server 2008 or newer, or Windows 7 or newer.
UNIX:
At the present time, Palisade products are not supported on Linux or any other flavor of UNIX.
Additional keywords: Compatibility, Version
Office 2019 Does Not Work On Windows 7 Pc
Last edited: 2020-03-20