Why Setup Reboots Three Times When Converting to NTFS

Last reviewed: May 8, 1997
Article ID: Q103058

The information in this article applies to:
  • Microsoft Windows NT operating system, version 3.1
  • Microsoft Windows NT Advanced Server, version 3.1

The Autoconvert program converts file systems to NTFS. During Windows NT Setup, Autoconvert reboots your system three times. This is because it needs to unmount and remount partitions several times while handling open files. The following sequence of events occurs:

  1. From Setup or Disk Administrator, file system conversion is initiated. Before any changes can be made to the target volume, the system must be rebooted.

  2. NTFS requires that a particular sector (n/2) be free to store a backup copy of the boot sector. Autoconvert begins by noting that sector n/2 is not free. Autoconvert then shuffles file-system structures until this sector is free. To prevent any possibility of disk corruption due to incomplete conversion, it reboots the system so that the file system will remount the volume and recognize the changes just made.

  3. Autoconvert now recognizes that sector n/2 is free. It converts the volume to NTFS. Once finished, it writes the new sectors, zero and n/2, and then, to force the file system to remount the volume as NTFS, reboots.

  4. Autoconvert recognizes that the volume is now NTFS, displays the "Volume is already NTFS" message, takes itself out of the Registry, and lets the system continue.


Additional query words: prodnt
Keywords : kbsetup ntfilesys ntsetup
Version : 3.1
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.