$WIN_NT$.~BT Temporary Directory Is Not Deleted After Windows Server 2003 Installation Is Complete (823598)


The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Small Business Server 2003, Premium Edition
  • Microsoft Windows Small Business Server 2003, Standard Edition

SYMPTOMS

After installation of the operating system, you may find the following files and directory in the root directory of the hard disk where the operating system resides:
  • $LDR (file)
  • SETUPLDR.bin (file)
  • TXTSETUP.sif (file)
  • $WIN_NT$.~BT (directory)

CAUSE

This problem may occur if you perform the installation by using an Unattend.txt file, and that Unattend.txt file includes multiple entries in the [MassStorageDrivers] section that point to controllers that are not physically present in the system.

This issue occurs because of shuffling of installation paths between TextMode Setup and GUI Mode Setup. Because of this shuffling, GUI Mode may not correctly read the installation paths. Therefore, GUI Mode may not correctly remove the temporary installation files and the temporary directory.

WORKAROUND

There are two workarounds:
  • Workaround 1

    Specify only one boot controller entry in the [MassStorageDrivers] section of your Unattend.txt file. Make sure that this driver corresponds to the boot controller that is installed in the system.
  • Workaround 2

    Manually delete the $LDR file, the SETUPLDR.bin file, the TXTSETUP.sif file, and the $WIN_NT$.~BT directory after setup is complete.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:12/27/2003
Keywords:kbBug KB823598 kbAudDeveloper
©2003 Microsoft Corporation. All rights reserved.