Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You Cannot Install the Windows XP Multilingual User Interface Pack from a Long Path
Article ID: 319598 - View products that this article applies to.
This article was previously published under Q319598
If you install additional languages for the Windows XP Multilingual User Interface Pack from a very long source path (more than 105 characters), Setup finishes, but language may not be installed. When this occurs, the last entries in the Muisetup.log file are similar to:
Note that the command line and the language ID (in this example, 0407 for German) may vary depending on the installation options that you use.
LOG: Command line: MUISetup.exe /i 0407 /r /s
ERROR: CopyFile has failed: C:\WINDOWS\system32\MUI\0407\HHCTRLUI.DLL
The data is invalid.
LOG: Multilingual files for "0407" is installed successfully.
LOG: Multilingual files for "0407" is uninstalled successfully.
LOG: Error copying files.
The Multilingual User Interface Pack Setup program is limited to a maximum path length of 128 characters for some files. In this case, the full path to the Hhctrlui.dll file in the installation source folder is longer than 128 characters. The complete path to the Hhctrlui.dll file in your installation location, including the file name, must not exceed 128 characters.
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/322389/EN-US/ )How to Obtain the Latest Windows XP Service Pack
Date Time Version Size File name ----------------------------------------------------- 01-Apr-2002 15:12 5.1.2600.41 84,992 Muisetup.exe
To work around this problem, make sure that the path length to the installation source files is less than 105 characters in length.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.