Article ID: 259303 - View products that this article applies to.
This article was previously published under Q259303
When you attempt to convert a partition from FAT32 file system to NTFS file system during a Sysprep cloning operation, and the volume being converted has anything other than a blank (null) volume label, the conversion may be unsuccessful. Depending on the method you use to attempt the conversion, there is either no error message to indicate that the conversion was unsuccessful, or an error message is displayed that disappears before you can read it.
If you use Sysprep in conjunction with a modified Sysprep.inf file and the following line is added to the [unattend] section, in this particular scenario, the conversion is unsuccessful:
In addition, the [GUIRunOnce] section in the Sysprep.inf file allows you to run commands. If you use a convert command, the process stops and you are prompted for a volume name.
Use of the ConvertNTFS parameter is not supported during the Mini-Setup phase that is run after a cloned system prepared with the System Preparation Utility is first started. The ConvertNTFS parameter is only supported during text mode setup, which is never invoked by the System Preparation utility.
It is possible to convert a FAT32 volume to NTFS using the CONVERT.EXE command. The convert command can be incorporated into the system preparation process in one of two ways:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
If you use Convert.exe to convert a FAT32 partition to NTFS and the volume has a label, the following message is displayed:
If you type the volume name, the following message may be displayed:
The type of the file system is FAT32.
Enter current volume label for Drive X:
Convert cannot gain exclusive access to the X: drive,
so it cannot convert it now. Would you like to
schedule it to be converted the next time the
system restarts (Y/N)?
Article ID: 259303 - Last Review: March 1, 2007 - Revision: 3.2