| 0x1000 | bootsect {/help|/nt60|/nt52} {SYS|ALL|:} [/force] [/mbr]Boot sector restoration toolBootsect.exe updates the master boot code for hard disk partitions in order toswitch between BOOTMGR and NTLDR. You can use this tool to restore the bootsector on your computer./help Displays these usage instructions./nt52 Applies the master boot code that is compatible with NTLDR to SYS, ALL, or . The operating system installed on SYS, ALL, or must be older than Windows Vista./nt60 Applies the master boot code that is compatible with BOOTMGR to SYS, ALL, or . The operating system installed on SYS, ALL, or must be Windows Vista, Windows Server 2008 or later.SYS Updates the master boot code on the system partition used to boot Windows.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 could be used as Windows boot volumes, which excludes any dynamic volumes that are not connected with an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition. Updates the master boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) is not associated with a volume or 2) is associated with a volume not connected to an underlying disk partition./force Forcibly dismounts the volume(s) during the boot code update. You should use this option with caution. If Bootsect.exe cannot gain exclusive volume access then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the target volume are currently opened by other programs. When successful, a forced dismount allows exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the target volume. This could result in unexpected behavior from the programs that opened these files. Therefore, you should use this option with caution./mbr Updates the Master Boot Record without changing the partition table on sector 0 of the disk that contains the partition specified by SYS, ALL, or drive letter. When used with /nt52 option, the master boot record is compatible with operating systems older than Windows Vista. When used with the /nt60 option, the master boot record is compatible with Windows Vista, Windows Server 2008 or later.Example:To apply the master boot code that is compatible with NTLDR to the volumelabeled E:, use the following command:bootsect /nt52 E: |
bootsect {/help|/nt60|/nt52} {SYS|ALL|:} [/force] [/mbr]Boot sector restoration toolBootsect.exe updates the master boot code for hard disk partitions in order toswitch between BOOTMGR and NTLDR. You can use this tool to restore the bootsector on your computer./help Displays these usage instructions./nt52 Applies the master boot code that is compatible with NTLDR to SYS, ALL, or . The operating system installed on SYS, ALL, or must be older than Windows Vista./nt60 Applies the master boot code that is compatible with BOOTMGR to SYS, ALL, or . The operating system installed on SYS, ALL, or must be Windows Vista, Windows Server 2008 or later.SYS Updates the master boot code on the system partition used to boot Windows.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 could be used as Windows boot volumes, which excludes any dynamic volumes that are not connected with an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition. Updates the master boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) is not associated with a volume or 2) is associated with a volume not connected to an underlying disk partition./force Forcibly dismounts the volume(s) during the boot code update. You should use this option with caution. If Bootsect.exe cannot gain exclusive volume access then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the target volume are currently opened by other programs. When successful, a forced dismount allows exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the target volume. This could result in unexpected behavior from the programs that opened these files. Therefore, you should use this option with caution./mbr Updates the Master Boot Record without changing the partition table on sector 0 of the disk that contains the partition specified by SYS, ALL, or drive letter. When used with /nt52 option, the master boot record is compatible with operating systems older than Windows Vista. When used with the /nt60 option, the master boot record is compatible with Windows Vista, Windows Server 2008 or later.Example:To apply the master boot code that is compatible with NTLDR to the volumelabeled E:, use the following command:bootsect /nt52 E: |
| 0x1001 | An error or status message could not be displayed due to an internal error. |
An error or status message could not be displayed due to an internal error. |
| 0x1002 | The program is out of memory. |
The program is out of memory. |
| 0x1004 | Could not map DOS drive letters to the associated volume device objects: %0 |
Could not map DOS drive letters to the associated volume device objects: %0 |
| 0x1005 | Could not map drive partitions to the associated volume device objects: %0 |
Could not map drive partitions to the associated volume device objects: %0 |
| 0x1006 | The system partition was not found: %0 |
The system partition was not found: %0 |
| 0x1007 | Could not map the system partition to an associated volume device object: %0 |
Could not map the system partition to an associated volume device object: %0 |
| 0x1008 | Internal error: target drive letter is malformed. |
Internal error: target drive letter is malformed. |
| 0x1009 | Could not map drive %1!c!: to an associated volume device object. |
Could not map drive %1!c!: to an associated volume device object. |
| 0x100A | Drive %1!c!: maps to volume %2!s!.This volume does not appear to connect to any disk partitions. Volume bootcodeis always unused in the absence of associated partitions. |
Drive %1!c!: maps to volume %2!s!.This volume does not appear to connect to any disk partitions. Volume bootcodeis always unused in the absence of associated partitions. |
| 0x100B | No bootcode was successfully updated. |
No bootcode was successfully updated. |
| 0x100C | Bootcode was successfully updated on at least one volume. |
Bootcode was successfully updated on at least one volume. |
| 0x100D | Bootcode was successfully updated on all targeted volumes. |
Bootcode was successfully updated on all targeted volumes. |
| 0x100E | Target volumes will be updated with BOOTMGR compatible bootcode. |
Target volumes will be updated with BOOTMGR compatible bootcode. |
| 0x100F | Target volumes will be updated with NTLDR compatible bootcode. |
Target volumes will be updated with NTLDR compatible bootcode. |
| 0x1010 | Could not enumerate top level volume device object symbolic links: %0 |
Could not enumerate top level volume device object symbolic links: %0 |
| 0x1011 | %1!s! (%2!s!) |
%1!s! (%2!s!) |
| 0x1012 | %1!s! |
%1!s! |
| 0x1013 | Could not open the volume device: %0 |
Could not open the volume device: %0 |
| 0x1014 | Could not construct a path to the volume root directory: %0 |
Could not construct a path to the volume root directory: %0 |
| 0x1015 | Could not open the volume root directory: %0 |
Could not open the volume root directory: %0 |
| 0x1016 | Could not retrieve volume filesystem properties: %0 |
Could not retrieve volume filesystem properties: %0 |
| 0x1017 | Bootcode is only available for FAT, FAT32, and NTFS volumes. A different filesystem appears to be in use on this volume. |
Bootcode is only available for FAT, FAT32, and NTFS volumes. A different filesystem appears to be in use on this volume. |
| 0x1018 | Could not allocate the transfer buffer required to write bootcode to this volume. |
Could not allocate the transfer buffer required to write bootcode to this volume. |
| 0x1019 | Could not move the volume file pointer to the bootcode location: %0 |
Could not move the volume file pointer to the bootcode location: %0 |
| 0x101A | Could not read the existing bootcode from this volume: %0 |
Could not read the existing bootcode from this volume: %0 |
| 0x101B | Could not write new bootcode to this volume: %0 |
Could not write new bootcode to this volume: %0 |
| 0x101C | Successfully updated %1!s! filesystem bootcode. |
Successfully updated %1!s! filesystem bootcode. |
| 0x101D | |
|
| 0x101E | Forced dismount complete, open handles to this volume are now invalid. |
Forced dismount complete, open handles to this volume are now invalid. |
| 0x101F | Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be locked during the update: %0 |
Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be locked during the update: %0 |
| 0x1020 | Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be dismounted during the update: %0 |
Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be dismounted during the update: %0 |
| 0x1021 | bootsect {/help|/nt60|/nt52} {SYS|ALL|:} [/force] [/mbr]Boot sector restoration toolBootsect.exe updates the master boot code for hard disk partitions in order toswitch between BOOTMGR and NTLDR. You can use this tool to restore the bootsector on your computer.Run \"bootsect /help\" for detailed usage instructions. |
bootsect {/help|/nt60|/nt52} {SYS|ALL|:} [/force] [/mbr]Boot sector restoration toolBootsect.exe updates the master boot code for hard disk partitions in order toswitch between BOOTMGR and NTLDR. You can use this tool to restore the bootsector on your computer.Run \"bootsect /help\" for detailed usage instructions. |
| 0x1022 | Internal error: assertion failed. File %1!S!, line %2!d!. |
Internal error: assertion failed. File %1!S!, line %2!d!. |
| 0x1080 | The system disk was not found: %0 |
The system disk was not found: %0 |
| 0x1081 | Could not prepare the system disk for update: %0 |
Could not prepare the system disk for update: %0 |
| 0x1082 | Could not prepare disk(s) for update: %0 |
Could not prepare disk(s) for update: %0 |
| 0x1084 | Bootcode is only updated on MBR partitioned disks. A different partitioning scheme is used on this disk. |
Bootcode is only updated on MBR partitioned disks. A different partitioning scheme is used on this disk. |
| 0x1085 | Could not allocate the transfer buffer required to write bootcode to this disk. |
Could not allocate the transfer buffer required to write bootcode to this disk. |
| 0x1086 | Could not open the disk device: %0 |
Could not open the disk device: %0 |
| 0x1087 | Could not move the disk file pointer to the bootcode location: %0 |
Could not move the disk file pointer to the bootcode location: %0 |
| 0x1088 | Could not read the existing bootcode from this disk: %0 |
Could not read the existing bootcode from this disk: %0 |
| 0x1089 | Could not write new bootcode to this disk: %0 |
Could not write new bootcode to this disk: %0 |
| 0x108A | Successfully updated disk bootcode. |
Successfully updated disk bootcode. |
| 0x108B | FAT32 filesystem bootcode is only supported on hardware with 512 byte sector sizes. |
FAT32 filesystem bootcode is only supported on hardware with 512 byte sector sizes. |
| 0x108C | exFAT filesystem bootcode is not supported in this version. |
exFAT filesystem bootcode is not supported in this version. |