1. Can I Install Ms Office 2019 On Windows 7
2. Can I Use Office 2019 On Windows 7 Service Pack

Developer Community| System Requirements| Compatibility| Distributable Code| License Terms| Blogs| Latest Release Known Issues

Any supported Windows 10 SAC release Windows 10 Enterprise LTSC 2018 The next LTSC release of Windows Server. Windows 7 is not listed in supported system. I notice that you are using Office 365 ProPlus which is a online-subscription product and different from Office 2019 product. You can still working with Office 365 ProPlus on Windows 7 currently. Microsoft uses various strategies to make Office 2019 less attractive when compared to Office 365. The company made Office 2019 Windows 10 exclusive on Windows, and increased the price of select editions of Office 2019. Last but not least, Microsoft revealed that it won't add any new features to Office 2019 after its release. The following versions of Office have been fully tested and are supported on Windows 10. They will still be installed on your computer after the upgrade to Windows 10 is complete. Office 365 (Version 16) Office 2019 (Version 16) Office 2016 (Version 16) Office 2013 (Version 15).

Visual Studio 2019 contains many new and exciting features and IDE productivity enhancements tosupport Windows app development, cross-platform mobile development, Azure development, web and cloud development,and more. To try out Visual Studio 2019, see Visual Studio 2019 Downloads.For more information about everything that's new in this release, see theVisual Studio 2019 release notes andWhat's New in Visual Studio 2019.

For Visual Studio Code, see Visual Studio Code FAQ.
For Visual Studio 2019 for Mac, see Visual Studio for Mac Platform Targeting and Compatibility.
For Visual Studio 2019 for Mac release notes.

Installation

You can install and use Visual Studio 2019 alongsideprevious versions of Visual Studio, including Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012.

Download

Click a button to download the latest version of Visual Studio 2019. For instructions on installing and updating Visual Studio 2019, see theUpdate Visual Studio 2019 to the most recent release.Also, see instructions on how to install offline.

Note: Installation package size will vary depending on your current Visual Studio configuration.

System Requirements

For information on the system requirements for installing and running the Visual Studio 2019 family of products,including Team Foundation Server 2019, see the Visual Studio 2019 System Requirement page andVisual Studio for Mac Product Family System Requirements.

Feedback and Support

For support, or to submit feedback on Visual Studio, see:

Upgrade Projects to Visual Studio 2019

When following the supported upgrade paths, your Visual Studio source, solutions, and project files will continueto work; however, you should expect to make some changes to sources. While we cannot guarantee binary compatibilitybetween releases, we will do our best to document significant changes to assist you with updates.

Note

For details on how to migrate your projects to Visual Studio 2019, see Porting, Migrating, and Upgrading Visual Studio Projects.

Platform Targeting

Visual Studio provides cutting-edge tools and technologies to create apps that take advantage of thelatest platform capabilities, whether Windows, Android, iOS, or Linux. Visual Studio 2019 also targetsearlier platforms so you can create new apps or modernize existing apps that execute on earlier versionsof Windows while leveraging the enhanced development tools, quality enablement, and team collaborationcapabilities in Visual Studio 2019. For more information, see Managing references in aproject and Visual Studio Multi-TargetingOverview.

Visual Studio 2019 Support for Windows Development

The following table explains the Microsoft Windows platforms for which you can build apps by using Visual Studio 2019.

Notes

• For support information regarding Microsoft operating systems, see Microsoft Support Lifecycle and Windows 10 Release Information.
• For support information on Microsoft .NET Framework, see .NET Framework Support Lifecycle FAQand .NET Framework System Requirements.
• Windows 10 Enterprise LTSC edition, Windows 10 S and Windows 10 Team Edition are not supported for development.You may use Visual Studio 2019 to build apps that run on Windows 10 LTSC, Windows 10 S and Windows 10 Team Edition. Remote debuging is supported on LTSC.
• Universal Windows app development for all target platforms is available when Visual Studio is installed on Windows 10.
• Universal Windows apps can be built from the command line when using Windows Server 2012 R2 or Windows Server 2016. UWP development—includingdesigning, editing, and local debugging—is not available on Windows Server. You may deploy these apps to Windows server and debug them remotely.
• Unity, and Xamarin can also be used for cross-platform development of Universal Windows Apps on Windows 10.

Visual Studio 2019 Support for .NET Development

Visual Studio 2019 supports development of apps that use any of the .NET implementations. Among the workloads and project types, you can find support for.NET Framework, .NET Core, Mono, .NET Native for Universal Windows Platform (UWP), C#, F#, and Visual Basic. Visual Studio 2019 supports the following .NET implementations:

• .NET Framework versions 4.8, 4.7.2, 4.7.1, 4.7, 4.6.2, 4.6.1, 4.6, 4.5.2, 4.5.1, 4.5, and 4.0
• .NET Core 3.1, 3.0, 2.2, 2.1, and 1.1.

Note

For more information on each of these implementations, and on the common API specification .NET Standard, see .NET architectural components.

Visual Studio 2019 Support for Android Development

Visual Studio 2019 enables you to build native Android apps using Xamarin and C# or using C++. The Visual Studio Tools for Unity andthe Unreal Engine enable Android game development. You can also use Visual Studio for Macto build Android apps using a Mac.

You can use Visual Studio setup to easily obtain the Android SDK and Android API levels 19, 21, 22, and 23.You can download additional API levels separately using the Android SDK Manager.You can also use Visual Studio Setup to obtain the Android Native Development Kit (R10E), Java SE Development Kit, and Apache Ant.

For more information, see Android development with Visual Studio andMobile App Development.

Note

For information on .NET development for Android, see .NET architectural components.

Visual Studio 2019 Support for iOS Development

Visual Studio 2019 enables you to build and debug apps for iOS by using C++, Unity, or Xamarinand a Mac configured for iOS development when using remotebuild, vcremote, the Visual Studio Tools for Unity,or the Xamarin Mac Agent. Xamarin supports iOS 7 and higher, and requires OS X 10.10 'Yosemite' or higher.You can also use Visual Studio for Mac to build iOS apps using a Mac.

Note

For more information, see Cross-platform mobile development in Visual Studio.For information on .NET development for iOS, see .NET architectural components.

Visual Studio 2019 Support for Linux Development

Visual Studio 2019 enables you to build and debug apps for Linux using C++, Python, and Node.js.Creating C++ apps for Linux requires theVisual C++ for Linux Development extension. Creating apps with Python orNode,js, requires that you enable remote debugging on the target Linux machine. You can also create, buildand remote debug .NET Core and ASP.NET Core applications for Linux using modern languages such as C#, VB and F#.

Note

For information on .NET development for Linux, see .NET architectural components.

• CentOS 7.1 and Oracle Linux 7.1
• Debian 8
• Fedora 23
• Linux Mint 17
• openSUSE 13.2
• Red Hat Enterprise Linux 7.2
• Ubuntu 14.04 and 16.04

Note

For more information see https://dot.net/core.

Visual Studio 2019 Support for macOS Development

Visual Studio 2019 enables you to build console applications and ASP.NET applications that target macOS.However, debugging is not supported. For additional macOS development tools choices, try Visual StudioCode or Visual Studio for Mac. Visual Studio Code provides a streamlined,extensible developer tool experience for macOS. Visual Studio for Macprovides a feature-rich IDE that enables you to build native macOS apps, including ASP.NET, using C#.

Note

For information on .NET development forMacOS, see .NET architectural components.

Other Platforms and Technologies

Visual Studio 2019 also supports the following platforms and technologies. For more information, seehttps://visualstudio.microsoft.com/vs/features/.

• Apache Ant
• Azure web apps and connected services, including Azure Data Lake
• Docker
• PowerShell
• Web Development with ASP.NET, HTML5/CSS3, JavaScript, Node.js, Python, or TypeScript

Can I Install Ms Office 2019 On Windows 7

Compatibility with Previous Releases

.NET Framework

.NET 4.7 is is a highly compatible in-place update of .NET 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, and 4.6.2.

Note

For more information, see the Migration Guide to the .NET Framework 4.7, 4.6, and 4.5.

Team Explorer, Azure DevOps Server, and Team Foundation Server

Team Explorer for Visual Studio 2019 will connect to Azure DevOps Server 2019, Team Foundation Server 2017,Team Foundation Server 2015, Team Foundation Server 2013, Team Foundation Server 2012, and Team Foundation Server 2010 SP1.

Silverlight

Silverlight projects are not supported in this version of Visual Studio. To maintain Silverlight applications,continue to use Visual Studio 2015.

Windows Store and Windows Phone apps

Projects for Windows Store 8.1 and 8.0, Windows 10 Mobile and Windows Phone are not supported in this release. Tomaintain these apps, continue to use Visual Studio 2015. To maintain Windows 10 Mobile projects, use Visual Studio 2017.To maintain Windows Phone 7.x projects, use Visual Studio 2012.

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.

Tip

Can I Use Office 2019 On Windows 7 Service Pack

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