"Computer name cannot contain only numbers" error message when you install Windows 7

[budeone]

"Computer name cannot contain only numbers" error message when you install Windows 7 by using Windows 7 SP1 integrated installation media

Hotfix Download Available
View and request hotfix downloads


Consider the following scenario:

• You try to install Windows 7 by starting the computer from installation media that is integrated with Windows 7 Service Pack 1.
• During the initial installation, you set the Time and Currency Format setting to a locale other than English, Finnish, German, or Swedish. Or, the locale was selected for you before you purchased your computer.
• A computer name that contains non-ASCII characters is entered in the Out of Box Experience (OOBE) Wizard.

In this scenario, you receive an error message that resembles the following:Computer name cannot contain only numbers, may not be identical with the user name and cannot contain spaces. Retype the name of the computer.



Note See the "More information" section for a list of accepted characters.


A computer name that contains non-ASCII characters may be entered during the OOBE Wizard in one of the following situations:

• You manually enter a computer name that contains a non-ASCII character.
• You manually enter a user name that contains a non-ASCII character.
  Note The default computer name is automatically generated based on the user name. Therefore, if the user name contains a non-ASCII character, the default computer name will also contain a non-ASCII character.
• Your language setting is Russian, Croatian, Ukrainian, or Thai.
  Note The default computer name is automatically generated by appending “-PC” to the user name. In Russian, Croatian, Ukrainian, or Thai, the translation of “-PC” contains non-ASCII characters. Therefore, the default computer name will also contain non-ASCII characters.

Back to the top


RESOLUTION

The hotfix package is recommended for OEMs and enterprises that build Windows 7 installation images. If you are a user who experiences this issue, click here to view the methods that are described in the "Workaround" section.Back to the top
Hotfix information

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 the problem described in this article. 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: http://support.microsoft.com/contactus/?ws=support
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.Prerequisites

To apply this hotfix, you must have a Windows 7 installation image that is integrated with Windows 7 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base: 976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.Restart requirement

You do not have to restart the computer after you apply this hotfix.Hotfix replacement information

This hotfix does not replace a previously released hotfix.File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows 7 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
  
  VersionProductMilestoneService branch6.1.760 1.17xxxWindows 7SP1GDR6.1.760 1.21xxxWindows 7SP1LDR
• GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7



File nameFile versionFile sizeDateTimePlatformMsoobeui.dll6.1.7601.175911,11 5,13608-Apr-201107:29x86Msoobeui.dll6.1.7601.217001,115,13608-Apr-201106:39x86
For all supported x64-based versions of Windows 7



File nameFile versionFile sizeDateTimePlatformMsoobeui.dll6.1.7601.175911,16 1,72808-Apr-201107:36x64Msoobeui.dll6.1.7601.217001,161,72808-Apr-201107:24x64


Found by Cooled
read more
http://support.microsoft.com/kb/2534111