Install The Romanian Language Pack For 64-bit Office

[Fidelia Boldul]

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.

Several years ago Microsoft published Office 2010 Starter. Office 2010 Starter was a free Office 2010, however some functions were disabled.
It installed only Microsoft Word and Excel and showed Microsoft advertisments during use.

Microsoft Starter 2010 works with a virtualization technology like V-App. It does not really install Office on your computer, but a virtualized office (like Office in a virtual machine).
To do this it creates a drive Q: which is not user accessable . If you are using drive Q: already, Office 2010 Starter won't work.

Office 2010 Starter could be installed using a setup (SetupConsumerC2ROLW.exe) which downloaded the installation files from internet.
Sometime around 2012, Microsoft pulled the plug, so the installation files couldn't be downloaded anymore.

A few days ago, I found the old executable and behold, I got it working again on my old computer with Windows 10 installed.
So Microsoft quietly activated the Office 2010 Starter files again, but will they pull the plug again in the near future ?

I found out that if the installation files are available locally, the setup won't need internet during the installation.
However the setup does not keep the files after installation, so I had to figure out how to get the installation files together locally.
Monitoring the installation I got some partial information how to download all the installation files needed.

This information was used to create the Office 2010 Starter downloader v1.0.
Be ware, this script works as is. Not a lot of error checking has been put in place. E.g. I do not check for downlad errors, but every language folder should be about 700 - 900 MB.

Thanks for the wonderful tool and script.
On Linux, installation with wine has an issue:
The script (Both version E and F) couldn't load update directory files and office setup program refuses to install by saying corrupted installation file.
The script (version F) itself terminates with the following error message:

You can try the download part on a Windows box and copy the "\bin\" folder. Then run the installation since you've got all the files but, then again, it'll try to make a Q: drive and run it from that and, good luck with wine handling that

That error is likely due to the fact that the InternetExplorer com objects aren't loaded in wine?
I believe this line is the actual culprit: $oHTTP = ObjCreate("WinHttp.WinHttpRequest.5.1") in this func:

I have downloaded allthe necessary files from a windows 10 machine and copied them to my linux installation without any issue for two different language sets. (I made the full installaton on that windows machine also wtihout any issues.)

No clue why it works nor why wouldn't. I don't think they support this version anyway. In any case, I got it to work in English from the US a few days back. Maybe is country dependent. But again, no clue.

Folks, these aren't the supportforums for old microsoft installers. The AutoIt3Part works perfectly and downloads the files.
So maybe try to find a forum that has more takers for these kind of issues?

This article covers the options for deploying languages for Microsoft 365 Apps, including what method to use, where to deploy languages from, how to deploy proofing tools, and best practices. We recommend using this article as part of planning your Office deployment.

You can't use language resources for Windows Installer (MSI) versions of Office with Microsoft 365 Apps, which uses Click-to-Run. For example, you can't use language packs downloaded from the Volume Licensing Service Center (VLSC) with Microsoft 365 Apps.

In general, you deploy languages for Microsoft 365 Apps with the same process and tools that you use to deploy Office itself. You can deploy multiple languages by including those languages directly in the Office packages, or you can deploy languages as a separate package, after Office is already installed. The steps in this article assume that you're deploying with Configuration Manager or the Office Deployment Tool, and that you use the Office Customization Tool (OCT) to create the configuration files for your deployment. If a setting isn't yet available in the OCT, steps are given for creating the configuration file in a text editor.

If your organization allows it, users can install Microsoft 365 Apps languages directly from the Office 365 portal. When users install Office from the Software page, they select a language from the Language drop-down box. If a user needs another language, they can just rerun the process for each required language. The setup adds the selected language to the user's device.

To deploy Microsoft 365 Apps in multiple languages, you need to include the other languages in the Office packages you create. To do so, select the languages you want to deploy in the Language section when creating the configuration file in the Office Customization Tool.

If you deploy Office from a local source on your network, you must download your languages to that source, in the same way that you download the Office package. For more information, see Download the installation files for Microsoft 365 Apps. When deploying from a local source, we recommend that you use the Office Content Delivery Network (CDN) as a backup source for language packs.

When you select a primary language in the Office Customization Tool, it sets the language for displaying shortcuts, right-click context menus, and tooltips, known as the Shell UI language. To change the Shell UI language after installing Office, you need to uninstall and then reinstall Office.

After deploying Microsoft 365 Apps, you can deploy more languages for Office. To do so, use the same process and tools you used to deploy Office, such as Configuration Manager or the Office Deployment Tool.

When you add to an existing deployment, the ODT can automatically detect the architecture (32-bit or 64-bit) and source location (Office CDN or local source) used by the current Microsoft 365 Apps installation. This means you don't have to specify these values when creating the configuration file. As a result, a single configuration file can serve multiple deployment groups. However, when using the Office Customization Tool, you must specify all these values. Therefore, this feature is available only if you create the configuration file using a text editor.

Users need local administrator permissions on their devices to install other languages for Office by default. However, to enable users without local admin rights to install a new language, activate the policy setting 'Allow users who aren't admins to install language accessory packs.'

You can use either Group Policy or Cloud Policy to enable the policy setting. In the Group Policy Management tool, you can find the policy setting under User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Language Preferences\Display Language.

If you're using a local source to deploy Office, we recommend that you use the AllowCdnFallback attribute in your configuration.xml file. This attribute enables you to use the Office CDN on the internet as a backup source location for the language files if they aren't available on your local source. For more information, see Use the Office CDN as a backup source for language packs.

If you've enabled the "Delay downloading and installing updates for Office" policy setting, the installation of additional languages by users will also be delayed by the number of days that you've specified in the policy setting.

Each language version of Microsoft 365 Apps includes proofing tools for a set of companion languages. For example, when you deploy the English version of Office, users receive proofing tools for English, Spanish, and French. These proofing tools include spelling and grammar checkers, thesauruses, and hyphenators. They might also include language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect.

c80f0f1006