Install The Russian Language Pack For 64-bit Office
Jule Watkinson
Language packs add additional display, help, and proofing tools to Microsoft 365. You can install additional language accessory packs after installing Microsoft 365. If a language accessory pack is described as having partial localization, some parts of Microsoft 365 may still display in the language of your copy of Microsoft 365.
If you're an administrator who has deployed a volume licensed version of Office 2016 to your users, you can download an ISO image of the language packs, language interface packs, and proofing tools from the Volume Licensing Service Center (VLSC).
Select the version of Microsoft 365 you're using from the tabs below, then select the language desired from the drop-down list. Then choose the appropriate architecture (32-bit or 64-bit) from the download links provided. If you're not sure what you're using, see What version am I using?
நறவதலக்க பறக தகப்ப எப்பட கட்டமப்பத என்பதப் பற்ற படக்கவம்.
If the language accessory pack includes proofing tools for that language, its status appears as Proofing installed. If the status is Proofing available, select the link to install the proofing tools.
You can change the default language for all your Microsoft 365 applications in the Set the Office Language Preferences dialog. For more information, see Add a language or set language preferences in Office.
When the English language pack is downloaded, I receive the following file setuplanguagepack.x86.en-us_.exe, which fails to install on a 64-bit Volume Licensing Office 2016 installation with the following message:
Since you have installed 32-bit and 64-bit components of Office 2016 together, you will need to uninstall either one of them. The safest way is to uninstall Office 2016 completely and install one version. Do not use setup.exe provided in the Microsoft Office 2016 DVD. Instead, open the "Office" folder and run setup32.exe or setup64.exe appropriately.
The Office Deployment Tool (ODT) is a command-line tool that you can use to download and deploy Microsoft 365 Apps to your client computers. The ODT gives you more control over an Office installation: you can define which products and languages are installed, how those products should be updated, and whether or not to display the install experience to your users.
The ODT consists of two files: setup.exe and configuration.xml. To work with the tool, you edit the configuration file to define what options you want, and then run setup.exe from the command line. For example, you can edit the configuration file to install the 64-bit English edition of Office with the license terms automatically accepted. For the full set of options, see Configuration options for the Office Deployment Tool.
Best practice: This article shows the XML elements and attributes in the configuration file for the Office Deployment Tool. You can continue to create the configuration file in a text editor, but we recommend using the Office Customization Tool instead. With the Office Customization Tool, you can easily create and modify configuration files in a web-based interface. For more information, see Overview of the Office Customization Tool.
To download Microsoft 365 Apps products and languages, use download mode. Example: setup.exe /download downloadconfig.xml. When you download Office to a folder that already contains that version of Office, the ODT will conserve your network bandwidth by downloading only the missing files. For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack will be downloaded.
To install the downloaded Microsoft 365 Apps products and languages on a client computer, use configure mode. You also use configure mode to remove and update Office products and languages. Example: setup.exe /configure installconfig.xml
To apply new application preferences to client computers that already have Microsoft 365 Apps installed, use customize mode. This mode will apply only application preferences, without changing any other deployment settings. Example: setup.exe /customize preferencesconfig.xml
When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then editing the XML elements and attributes to define the options you want.
In this example, the configuration file downloads the installation files for a 32-bit English edition of Microsoft 365 Apps for enterprise and the subscription version of the Visio desktop app to \\server\share on your network:
From a command prompt, run the ODT executable in download mode and with a reference to the configuration file you saved. In this example, the configuration file is named downloadconfig.xml:
After running the command, go to the download location you defined in the configuration file and look for an Office folder with the appropriate files in it. If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log file in the %temp% folder.
You can use the Office Deployment Tool to download the installation files for Microsoft 365 Apps from a local source on your network. By doing so, you can store a central copy of multiple languages and products for Office and distribute just the languages and products that you need to other locations on your network.
To download from a local source, follow the steps for downloading Office with the ODT, but include in your configuration file the download path, which defines where the installation files are downloaded from. For example, this configuration file downloads a 32-bit English edition of Microsoft 365 Apps for enterprise from \\servera\share (the DownloadPath) to \\serverb\share (the SourcePath):
The location of the Office installation files is \\server\share. The display level is set to None, which means the user will not see any user interface during the install. The AcceptEULA is set to TRUE, which means your users will not have to click to accept the license terms during the installation.
From a command prompt, run the ODT executable in configure mode with a reference to the configuration file you saved. In the following example, the configuration file is named installconfig.xml:
You must have local administrator permissions on the client computer. You can run the executable from the client computer on which you want to install Office or you can put the ODT and the configuration file on a network share and run it from there. If you use a network share, make sure to pass the full network path for both the setup.exe and the configuration file to the command.
After running the command, you should see the Office installation start (unless you set display level to none). After installation is complete, the command prompt will display "Products configured successfully." If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log files in the %temp% folder.
Use the ODT to download the Office installation files and then point your client computers to that location to receive their updates. (By default, clients are updated directly from the Office Content Delivery Network (CDN).)
To change where your client computers receive their updates, run the ODT in configure mode and specify an update path in the configuration file. For example, to have Microsoft 365 Apps get updates automatically from a network share called \\server\updates, include the following line in your configuration.xml file:
This article does not cover all the issues related to managing updates for Office in your organization. For more information on that scenario, including using Group Policy, see Choose how to manage updates to Microsoft 365 Apps.
When installing Microsoft 365 Apps, you can exclude specific applications. To do so, follow the steps for installing Office with the ODT, but include the ExcludeApp element in your configuration file. For example, this configuration file installs all the Microsoft 365 Apps for enterprise applications except Publisher:
If you've already installed Microsoft 365 Apps, you can also use the ExcludeApp element to remove an application that you've previously installed. For example, the configuration file above removes Publisher from the previous installation of Office.
You can also remove an entire language version of Microsoft 365 Apps. To do so, follow the steps for excluding products for installing Office with the ODT, but replace the configuration file with one that uses the Remove element. For example, this configuration file removes the Spanish language version of Microsoft 365 Apps for enterprise:
c80f0f1006