bootsect.exe
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x1000 | 1011 | bootsect {/help|/nt60|/nt52} {SYS|ALL| |
| 0x1001 | 1011 | An error or status message could not be displayed due to an internal error. |
| 0x1002 | 1011 | The program is out of memory. |
| 0x1004 | 1011 | Could not map DOS drive letters to the associated volume device objects: |
| 0x1005 | 1011 | Could not map drive partitions to the associated volume device objects: |
| 0x1006 | 1011 | The system partition was not found: |
| 0x1007 | 1011 | Could not map the system partition to an associated volume device object: |
| 0x1008 | 1011 | Internal error: target drive letter is malformed. |
| 0x1009 | 1011 | Could not map drive %1!c!: to an associated volume device object. |
| 0x100a | 1011 | Drive %1!c!: maps to volume %2!s!. This volume does not appear to connect to any disk partitions. Volume bootcode is always unused in the absence of associated partitions. |
| 0x100b | 1011 | No bootcode was successfully updated. |
| 0x100c | 1011 | Bootcode was successfully updated on at least one volume. |
| 0x100d | 1011 | Bootcode was successfully updated on all targeted volumes. |
| 0x100e | 1011 | Target volumes will be updated with BOOTMGR compatible bootcode. |
| 0x100f | 1011 | Target volumes will be updated with NTLDR compatible bootcode. |
| 0x1010 | 1011 | Could not enumerate top level volume device object symbolic links: |
| 0x1011 | 1011 | %1!s! (%2!s!) |
| 0x1012 | 1011 | %1!s! |
| 0x1013 | 1011 | Could not open the volume device: |
| 0x1014 | 1011 | Could not construct a path to the volume root directory: |
| 0x1015 | 1011 | Could not open the volume root directory: |
| 0x1016 | 1011 | Could not retrieve volume filesystem properties: |
| 0x1017 | 1011 | Bootcode is only available for FAT, FAT32, and NTFS volumes. A different filesystem appears to be in use on this volume. |
| 0x1018 | 1011 | Could not allocate the transfer buffer required to write bootcode to this volume. |
| 0x1019 | 1011 | Could not move the volume file pointer to the bootcode location: |
| 0x101a | 1011 | Could not read the existing bootcode from this volume: |
| 0x101b | 1011 | Could not write new bootcode to this volume: |
| 0x101c | 1011 | Successfully updated %1!s! filesystem bootcode. |
| 0x101d | 1011 | |
| 0x101e | 1011 | Forced dismount complete, open handles to this volume are now invalid. |
| 0x101f | 1011 | Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be locked during the update: |
| 0x1020 | 1011 | Updated %1!s! filesystem bootcode. The update may be unreliable since the volume could not be dismounted during the update: |
| 0x1021 | 1011 | bootsect {/help|/nt60|/nt52} {SYS|ALL| |
| 0x1022 | 1011 | Internal error: assertion failed. File %1!S!, line %2!d!. |
| 0x1080 | 1011 | The system disk was not found: |
| 0x1081 | 1011 | Could not prepare the system disk for update: |
| 0x1082 | 1011 | Could not prepare disk(s) for update: |
| 0x1083 | 1011 | %1!s! |
| 0x1084 | 1011 | Bootcode is only updated on MBR partitioned disks. A different partitioning scheme is used on this disk. |
| 0x1085 | 1011 | Could not allocate the transfer buffer required to write bootcode to this disk. |
| 0x1086 | 1011 | Could not open the disk device: |
| 0x1087 | 1011 | Could not move the disk file pointer to the bootcode location: |
| 0x1088 | 1011 | Could not read the existing bootcode from this disk: |
| 0x1089 | 1011 | Could not write new bootcode to this disk: |
| 0x108a | 1011 | Successfully updated disk bootcode. |
| 0x108b | 1011 | FAT32 filesystem bootcode is only supported on hardware with 512 byte sector sizes. |
| 0x108c | 1011 | exFAT filesystem bootcode is not supported in this version. |
| 47 entries | ||