When you run the Sysprep Mini-Setup wizard, if you change
the default user interface (UI) from English to a language that localizes the
word "administrator" in its Multilingual User Interface Pack (MUI) resources,
the profiles for the three accounts that run in the system context (System.
Local Service, Network Service) are no longer synchronized. The System profile
(S-1-5-18) uses the localized UI but the Network Service profile (S-1-5-20) and
the Local Service profile (S-1-5-19) are still in English. When Lsass.exe
impersonates these service accounts, the inconsistency causes the computer to
take up to 10 minutes to start and many services do not start.
Microsoft Windows may stop responding on multiprocessor computers during startup when the Preparing Network Connections windows is displayed.NOTE
: Languages that localize the word "administrator" include most
European languages. Languages from East Asia do not localize this word.
This problem occurs because the Sysprep Mini-Setup wizard
resets the localization values that are configured through Intl.cpl.
Microsoft Windows XP
Service pack information
To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows XP service pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have Windows XP service pack 1 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
28-Oct-2002 18:31 5.1.2600.11 122,368 Intl.cpl
28-Oct-2002 18:31 5.1.2600.11 939,520 Syssetup.dll
Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this problem in Windows XP and in Microsoft Windows Server 2003, follow these steps:
- Start Registry Editor.
- Locate and then click the following registry setting:
- Note the value of the
- Change the value of the
registry key in the following registry settings to match the value that you
noted in step 3:
- Quit Registry Editor.
- Restart the computer.
After you complete this procedure, the computer starts much
faster and the services start successfully.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Windows XP Service Pack 2.