Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Locale information lost when NPM component uninstalled then reinstalled

Locale information lost when NPM component uninstalled then reinstalled

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,015 Votes: 1 Revisions: 8


  1. NPM was installed and Japanese selected for the language/locale.
  2. A component was uninstalled.
  3. When the component is reinstalled, the wizard was in English instead of Japanese.


The locale code must be provided during the reinstallation command.


In the case of Japanese, to retain locale information when reinstalling, use:

msiexec /i Install.msi TRANSFORMS=:ja-jp.mst
Last modified