FIX: After you restore Windows Server 2003 for Itanium-based Systems by using ASR, a partition that was originally in the MBR format is converted to a GPT partition unexpectedly

Consider the following scenario. You run an Automated System Recovery (ASR) backup on a computer that is running Microsoft Windows Server 2003 for Itanium-based Systems. Then, you restore the operating system by using ASR. After you restore the operating system, a partition that was originally in the master boot record (MBR) format is converted to a GUID partition table (GPT) partition unexpectedly.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix Information

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed on the computer. For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

Restart Requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) 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.

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Syssetup.dll	5.2.3790.2606	1,947,648	30-Dec-2005	11:33	IA-64	SP1	Not Applicable
Wsyssetup.dll	5.2.3790.2606	1,047,552	30-Dec-2005	11:33	x86	SP1	WOW

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Windows Server 2003 Service Pack 2.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: