Bootsect Command-Line Options
3/21/2011
Bootsect.exe updates the master boot code for hard disk partitions to switch between BOOTMGR and NTLDR. You can use this tool to restore the boot sector on your computer. This tool replaces FixFAT and FixNTFS.
Bootsect Command-Line Options
Bootsect uses the following conventions:
bootsect.exe {/help | /nt52 | /nt60} {SYS | ALL | DriveLetter:} [/force]
For example, to apply the master-boot code that is compatible with NTLDR to the volume labeled E, use the following command:
bootsect.exe /nt52 E:
A description of each option follows.
| Command | Description |
|---|---|
/help |
Displays usage instructions. |
/nt52 |
Applies the master-boot code that is compatible with NTLDR to SYS, ALL, or DriveLetter. The operating system installed on SYS, ALL, or DriveLetter must be an earlier version of Standard 7. |
/nt60 |
Applies the master-boot code that is compatible with BOOTMGR to SYS, ALL, or DriveLetter. The operating system installed on SYS, ALL, or DriveLetter must be Standard 7. |
SYS |
Updates the master-boot code on the system partition that is used to boot Standard 7. |
ALL |
Updates the master-boot code on all partitions. ALL does not necessarily update the boot code for each volume. Instead, this option updates the boot code on volumes that can be used as Standard 7 boot volumes. This excludes any dynamic volumes that are not connected by using an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition. |
DriveLetter: |
Updates the master-boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) DriveLetter is not associated with a volume, or 2) DriveLetter is associated with a volume not connected to an underlying disk partition. |
/force |
Forcibly dismounts the volume(s) during the boot-code update. Use this option with caution. If Bootsect.exe cannot gain exclusive volume access, the file system might overwrite the boot code before the next restart. Bootsect.exe always tries to lock and unmount the volume before each update. When /force is specified, a forced unmount is tried if the initial lock attempt fails. A lock can fail, for example, if files on the destination volume are currently opened by other programs. When successful, a forced unmount enables exclusive volume access and a reliable boot-code update even though the initial lock failed. At the same time, a forced unmount invalidates all open handles to files on the destination volume. This can result in unexpected behavior from the programs that opened these files. Therefore, use this option with caution. |