Article ID: 931760 - View products that this article applies to.
You use Windows Vista or Windows Preinstallation Environment (Windows PE) 2.0 to create partitions on a hard disk. After you do this, you try to install Microsoft Windows XP on the hard disk without using Windows XP to repartition the disk. In this case, you cannot install Windows XP successfully.
Windows XP Setup successfully completes the text-mode part of Setup. However, after the text-mode part of Setup is complete, the computer cannot be restarted successfully to enter the graphical user interface (GUI)-mode part of Setup. Additionally, the computer may stop responding. You may receive an error message that resembles one of the following:
A disk read error occurred
Unable to load operating system
When you deploy a Windows XP Professional sysprep image to a system, the system may continuously restart after you start the system for the first time. If you press F8 and then disable the "automatic restart" option, you may receive the following Stop error:
Error loading operating system
Additionally, if you view the disk in Windows PE 2.0, the disk may appear as "raw."
Stop: 0x000000ED (0X81F85678, 0xC000014F,0x00000000,0x00000000)
This problem occurs because Windows Vista and Windows PE 2.0 create disk partitions differently than Windows XP. This problem occurs only on computers that use certain BIOS firmware.
To work around this problem, use one of the following methods.
Method 1: Disable the "automatic disk translation" featureBefore you partition the hard disk, you can disable the "automatic disk translation" feature in the BIOS configuration. For example, you can change the disk type from Auto to Large.
Method 2: Modify the registry to use the Windows XP disk partition procedureImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Before you partition the hard disk in Windows Vista or in Windows PE 2.0, modify the registry so that the partitions are created by using the Windows XP procedure. To do this, follow these steps:
Method 3If you are using Microsoft Deployment Toolkit 2008 to deploy Windows XP, follow these steps:
When you use the Windows Vista or Windows PE 2.0 partition procedure to create a partition, the partition border is constructed based on the registry setting on the system. However, when you use the Windows XP partition procedure to create a partition, the partition border is aligned according to the cylinder boundary.
When you create a partition, free space that is followed by the first partition is created at the beginning of the disk. The size of the free space is determined based on how the partition border is constructed. Therefore, the size may vary, depending on how the partition is created.
When you create a partition by using the Windows XP procedure, this free space is equal to one cylinder. However, when you create a partition by using the Windows Vista or Windows PE 2.0 procedure, the free space varies, depending on the registry setting.
To resolve this problem, you must integrate the hotfix into the source files of the Windows XP installation before you install Windows XP. For more information about how to integrate this hotfix into the Windows installation source files, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/828930/ )How to integrate software updates into your Windows installation source files
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesThis hotfix requires Windows XP Service Pack 2 (SP2).
(https://support.microsoft.com/kb/322389/ )How to obtain the latest Windows XP service pack
Restart requirementYou have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 item in Control Panel.
Windows XP with SP2, x86-based versions
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the"Applies to" section.
Article ID: 931760 - Last Review: July 23, 2009 - Revision: 6.0