bootmgr.exe
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x2329 | 78.11011 | BM_MSG_FIRST |
| 0x232a | 8.11011 | The Boot Configuration Data for your PC is missing or contains errors. |
| 0x232b | 78.11011 | To specify an advanced option for this choice, press F8. |
| 0x232c | 8.11011 | There was a problem enumerating global parameters. |
| 0x232d | 78.11011 | An unexpected error has occurred. |
| 0x232e | 8.11011 | The application or operating system couldn't be loaded because a required file is missing or contains errors. |
| 0x232f | 8.11011 | The Boot Configuration Data file doesn't contain valid information for an operating system. |
| 0x2334 | 8.11011 | A required device isn't connected or can't be accessed. |
| 0x2335 | 8.11011 | A required file couldn't be accessed because your BitLocker key wasn't loaded correctly. |
| 0x2336 | 8.11011 | There isn't enough memory available to create a ramdisk device. |
| 0x2337 | 8.11011 | The Boot Configuration Data file is missing some required information. |
| 0x2338 | 8.11011 | This 64-bit application couldn't load because your PC doesn't have a 64-bit processor. If you're using Windows To Go, make sure your USB device has a version of Windows that's compatible with the PC you're trying to use. |
| 0x2339 | 78.11011 | An unexpected I/O error has occurred. |
| 0x233a | 8.11011 | The header checksum for this file doesn't match the computed checksum. |
| 0x233b | 8.11011 | The digital signature for this file couldn't be verified. |
| 0x233c | 8.11011 | There is an invalid object in the Boot Configuration Data store. |
| 0x233d | 8.11011 | BitLocker |
| 0x233e | 8.11011 | Enter the PIN to unlock this drive |
| 0x233f | 8.11011 | Incorrect PIN; please enter the PIN again |
| 0x2340 | 8.11011 | Too many PIN entry attempts |
| 0x2341 | 8.11011 | Enter the recovery key for this drive |
| 0x2342 | 8.11011 | The last six digits are incorrect; please enter them again |
| 0x2343 | 8.11011 | The recovery key is incorrect; please enter it again |
| 0x2344 | 8.11011 | Enter the password to unlock this drive |
| 0x2345 | 8.11011 | Incorrect password; please enter the password again |
| 0x2346 | 8.11011 | Too many password entry attempts |
| 0x2347 | 8.11011 | Plug in the USB drive that has the BitLocker key |
| 0x2348 | 8.11011 | There is no valid BitLocker key on this USB drive |
| 0x2349 | 8.11011 | To recover this drive, plug in the USB drive that has the BitLocker recovery key |
| 0x234a | 8.11011 | There is no valid recovery key on this USB drive |
| 0x234b | 8.11011 | You must enter your recovery key to access Startup Settings |
| 0x234d | 1011 | BitLocker needs your recovery key to unlock your drive because your PC's configuration has changed. This may have happened because a disc or USB device was inserted. Removing it and restarting your PC may fix this problem. |
| 0x234e | 1011 | BitLocker needs your recovery key to unlock your drive because the following boot application has changed: %1. |
| 0x234f | 1011 | BitLocker needs your recovery key to unlock your drive because the Boot Configuration Data setting %1 has changed for the following boot application: %2. |
| 0x2350 | 10 | BitLocker needs your recovery key to unlock your drive because the trusted platform module is not functioning correctly. |
| 0x2351 | 10 | BitLocker needs your recovery key to unlock your drive because the trusted platform module is disabled. |
| 0x2352 | 10 | BitLocker needs your recovery key to unlock your drive because the trusted platform module is not accessible. |
| 0x2353 | 1011 | BitLocker needs your recovery key to unlock your drive because the partition table reports an invalid partition size. |
| 0x2354 | 1011 | BitLocker needs your recovery key to unlock your drive because debugging mode has been enabled. |
| 0x2355 | 1011 | BitLocker needs your recovery key to unlock your drive because driver signature enforcement has been disabled. |
| 0x2356 | 1011 | BitLocker needs your recovery key to unlock your drive because of an unknown error. |
| 0x2357 | 8.11011 | To protect the privacy of your data, BitLocker has prevented the unlocking of your drive. You'll need to enter your recovery key. |
| 0x2359 | 8.11011 | There is a limit on the number of attempts allowed. |
| 0x235a | 8.11011 | To reboot and try again, press Enter. For other recovery options, press Esc. |
| 0x235b | 8.11011 | Find the USB drive you used when you turned on BitLocker. |
| 0x235c | 8.11011 | Use the number keys or function keys F1-F10 (use F10 for 0). |
| 0x235e | 8.11011 | Press the Insert key to see the PIN as you type. |
| 0x235f | 8.11011 | Press the Insert key to see the password as you type. |
| 0x2360 | 8.11011 | Press the Insert key to hide the PIN as you type. |
| 0x2361 | 8.11011 | Press the Insert key to hide the password as you type. |
| 0x2362 | 1011 | Recovery key ID (to identify your key): |
| 0x2364 | 8.11011 | Key filename: |
| 0x2365 | 8.11011 | Press Enter to continue |
| 0x2366 | 8.11011 | Press Enter to reboot and try again |
| 0x2367 | 8.11011 | Press Esc for BitLocker recovery |
| 0x2368 | 8.11011 | Press Esc for more recovery options |
| 0x2369 | 8.11011 | Press Esc or the Windows key for recovery |
| 0x236a | 8.11011 | Press Esc or the Windows key for more recovery options |
| 0x236b | 8.11011 | Press F11 to choose an alternate operating system |
| 0x236c | 8.11011 | BM_FVE_EMPTY_STRING |
| 0x236d | 1011 | BitLocker needs your recovery key to unlock your drive because Secure Boot has been disabled. Either Secure Boot must be re-enabled, or BitLocker must be suspended for Windows to start normally. |
| 0x236e | 1011 | BitLocker needs your recovery key to unlock your drive because Secure Boot policy has unexpectedly changed. |
| 0x236f | 1011 | BitLocker needs your recovery key to unlock your drive because Device Lock has been triggered due to too many incorrect password attempts. |
| 0x2370 | 8.11011 | BitLocker recovery |
| 0x2371 | 8.11011 | Press Enter or the Windows key to continue |
| 0x2372 | 8.11011 | This operating system uses the Physical Address Extension feature to support systems with more than 4 GB of RAM. You'll need to use a PC with a compatible processor to run the operating system. |
| 0x2373 | 1011 | A component of the operating system has expired. |
| 0x2710 | 8.11011 | Please wait |
| 0x2711 | 8.11011 | Preparing Automatic Repair |
| 0x2712 | 8.11011 | Preparing System Image Recovery |
| 0x2713 | 8.11011 | Preparing Command Prompt |
| 0x2714 | 8.11011 | Preparing system restore |
| 0x2715 | 1011 | Preparing |
| 0x2716 | 8.11011 | Hyper-V |
| 0x2717 | 8.11011 | |
| 0x2718 | 8.11011 | Multicast Server |
| 0x2719 | 8.11011 | Preparing |
| 0x271a | 8.11011 | Preparing BitLocker recovery |
| 0x271b | 8.11011 | The Windows Boot Configuration Data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture. |
| 0x4e20 | 8.11011 | Recovery |
| 0x4e21 | 1011 | Your PC/Device needs to be repaired |
| 0x4e22 | 8.11011 | There are no more BitLocker recovery options on your PC |
| 0x4e23 | 8.11011 | There was a problem with a device connected to your PC |
| 0x4e24 | 1011 | You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer. |
| 0x4e25 | 8.11011 | This problem can happen when a removable storage device is removed while it's in use or is failing. Properly connecting any removable storage and restarting your PC may fix this problem. |
| 0x4e26 | 8.11011 | Choose one of the options below to address this problem. |
| 0x4e27 | 8.11011 | Press the Windows key for recovery |
| 0x4e28 | 8.11011 | Press Esc for recovery |
| 0x4e29 | 8.11011 | Press the Windows key to use a different operating system |
| 0x4e2a | 8.11011 | Press F9 to use a different operating system |
| 0x4e2b | 8.11011 | Press the Windows key to try again |
| 0x4e2c | 8.11011 | Press Enter to try again |
| 0x4e2d | 8.11011 | File: |
| 0x4e2e | 8.11011 | Source: |
| 0x4e2f | 8.11011 | Line: |
| 0x4e30 | 8.11011 | Error code: |
| 0x4e31 | 8.11011 | Your PC couldn't start properly |
| 0x4e32 | 8.11011 | Your PC couldn't turn off properly |
| 0x4e33 | 8.11011 | Press F8 for Startup Settings |
| 0x4e34 | 1011 | For more information on how to retrieve this key, go to %1 from another PC or mobile device. |
| 0x4e35 | 8.11011 | Press Esc for UEFI Firmware Settings |
| 0x4e36 | 8.11011 | Press the Windows key for UEFI Firmware Settings |
| 0x4e37 | 8.11011 | :( |
| 0x4e38 | 1011 | aka.ms/recoverykeyfaq |
| 0x4e39 | 1011 | The entry cannot be launched because it requires system capabilities that are blocked until reboot. Please reboot the computer or device. |
| 0x4e3a | 1011 | Press F1 to enter Recovery Environment |
| 0x4e3b | 1011 | aka.ms/myrecoverykey |
| 0x4e3c | 1011 | aka.ms/aadrecoverykey |
| 0x4e3d | 1011 | The key should be in your Microsoft account, try here: %1 |
| 0x4e3e | 1011 | The key should be in your work or school account, try here: %1 |
| 0x4e3f | 10 | The key should be in your computer account, contact your organization’s help desk. |
| 0x4e40 | 1011 | The key was previously printed and saved. Look for a printout or a text file with the key. |
| 0x4e41 | 1011 | The key was previously saved. Look for a text file with the key. |
| 0x4e42 | 1011 | The key was previously printed. Look for a printout with the key. |
| 0x4e43 | 10 | Here’s how to find your key: |
| 0x4e44 | 1011 | - Sign in on another device and go to: %1 |
| 0x4e45 | 1011 | - For more information go to: %1 |
| 0x4e46 | 1011 | - Try your Microsoft account at: %1 |
| 0x4e47 | 1011 | - Try your work or school account at: %1 |
| 0x4e48 | 10 | - Contact your organization’s help desk |
| 0x4e49 | 1011 | - Look for a printout or a text file with the key |
| 0x4e4a | 1011 | - Look for a text file with the key |
| 0x4e4b | 1011 | - Look for a printout with the key |
| 0x2350 | 11 | BitLocker needs your recovery key to unlock your drive because the Trusted Platform Module is not functioning correctly. |
| 0x2351 | 11 | BitLocker needs your recovery key to unlock your drive because the Trusted Platform Module is disabled. |
| 0x2352 | 11 | BitLocker needs your recovery key to unlock your drive because the Trusted Platform Module is not accessible. |
| 0x2374 | 11 | Additional BitLocker recovery information |
| 0x2375 | 11 | Additional recovery information |
| 0x2376 | 11 | Press Alt for additional BitLocker recovery information |
| 0x2377 | 11 | Press Alt to go back |
| 0x2378 | 11 | BitLocker needs your recovery key to unlock your drive because of an unexpected error with the Trusted Platform Module. |
| 0x2379 | 11 | BitLocker needs your recovery key to unlock your drive because the Trusted Platform Module is not present or not recognized. |
| 0x4e3f | 11 | The key should be in your computer account, contact your organization's help desk. |
| 0x4e43 | 11 | Here's how to find your key: |
| 0x4e48 | 11 | - Contact your organization's help desk |
| 0x4e4c | 11 | Sign in with this account: %1 |
| 0x4e4d | 11 | Error category and code: %1 (%2) |
| 0x4e4e | 11 | Device lockout |
| 0x4e4f | 11 | TPM |
| 0x4e50 | 11 | Storage |
| 0x4e51 | 11 | Initiated by user |
| 0x4e52 | 11 | Code integrity |
| 0x4e53 | 11 | Boot configuration |
| 0x4e54 | 11 | Protector |
| 0x4e55 | 11 | Unknown |
| 0x4e56 | 11 | E_FVE_TPM_FAILURE |
| 0x4e57 | 11 | E_FVE_DEVICE_LOCKEDOUT |
| 0x4e58 | 11 | E_FVE_DEVICE_LOCKOUT_MISMATCH |
| 0x4e59 | 11 | E_FVE_BAD_SRK |
| 0x4e5a | 11 | E_FVE_TPM_DISABLED |
| 0x4e5b | 11 | E_FVE_TPM_INVALIDATED |
| 0x4e5c | 11 | E_FVE_BOOT_DEBUG_ENABLED |
| 0x4e5d | 11 | E_FVE_CI_DISABLED |
| 0x4e5e | 11 | E_FVE_SECURE_BOOT_DISABLED |
| 0x4e5f | 11 | E_FVE_SECURE_BOOT_CHANGED |
| 0x4e60 | 11 | E_FVE_PCR_MISMATCH |
| 0x4e61 | 11 | E_FVE_BAD_CODE_ID |
| 0x4e62 | 11 | E_FVE_BAD_CODE_OPTION |
| 0x4e63 | 11 | E_FVE_UNKNOWN |
| 0x4e64 | 11 | E_FVE_USER_REQUESTED_RECOVERY |
| 0x4e65 | 11 | BitLocker recovery error additional information: |
| 0x4e66 | 11 | - Mismatched PCR: %1 |
| 0x4e67 | 11 | - Mismatched event number: %1 |
| 0x4e68 | 11 | - Expected event type, observed event type: 0x%1, 0x%2 |
| 0x4e69 | 11 | - Expected event label: %1 |
| 0x4e6a | 11 | - Observed event label: %1 |
| 0x4e6b | 11 | - Date/time of seal: %1 |
| 0x4e6c | 11 | For more information on how to address the BitLocker error, go to %1 |
| 0x4e6d | 11 | aka.ms/unlockissues |
| 0x4e6e | 11 | - Boot Configuration Data setting: %1 |
| 0x4e6f | 11 | - Boot application: %1 |
| 0x4e70 | 11 | - Expected events count, observed events count: %1, %2 |
| 0x4e71 | 11 | Details: %1 |
| 0x4e72 | 11 | - Expected digest: %1 |
| 0x4e73 | 11 | - Observed digest: %1 |
| 0x4e74 | 11 | - Expected bootmgr path: %1 |
| 0x4e75 | 11 | - Observed bootmgr path: %1 |
| 0x4e76 | 11 | - TPM status: %1 |
| 0x4e77 | 11 | E_FVE_TPM_NOT_DETECTED |
| 0x4e78 | 11 | E_FVE_MATCHING_PCRS_TPM_FAILURE |
| 0x4e79 | 11 | - Failing PCR: %1 |
| 0x232a | 7 | An error occurred while attempting to read the boot configuration data. |
| 0x232c | 7 | An error occurred while enumerating global parameters. |
| 0x232e | 7 | The selected entry could not be loaded because the application is missing or corrupt. |
| 0x232f | 7 | The Windows Boot Configuration Data file does not contain a valid OS entry. |
| 0x2330 | 7 | _ |
| 0x2331 | 7 | Invalid group of digits entered. Please correct the highlighted group. |
| 0x2333 | 7 | * |
| 0x2334 | 7 | The boot selection failed because a required device is inaccessible. |
| 0x2335 | 7 | The action could not be completed because the BitLocker Drive Encryption key required to unlock the volume could not be obtained. |
| 0x2336 | 7 | Ramdisk device creation failed due to insufficient memory. |
| 0x2337 | 7 | The Windows Boot Configuration Data file is missing required information. |
| 0x2338 | 7 | Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode. |
| 0x233a | 7 | The file is possibly corrupt. Its header checksum does not match the computed checksum. |
| 0x233b | 7 | Windows cannot verify the digital signature for this file. |
| 0x233c | 7 | The configuration for an element within the object is invalid in the boot configuration data store. |
| 0x234c | 8.1 | Bitlocker needs your recovery key to unlock your drive because |
| 0x234d | 8.1 | your PC's configuration has changed. This may have happened because a disc or USB device was inserted. Removing it and restarting your PC may fix this problem. |
| 0x234e | 8.1 | the following boot application has changed: %1. |
| 0x234f | 8.1 | the Boot Configuration Data setting %1 has changed for the following boot application: %2. |
| 0x2350 | 8.1 | the trusted platform module is not functioning correctly. |
| 0x2351 | 8.1 | the trusted platform module is disabled. |
| 0x2352 | 8.1 | the trusted platform module is not accessible. |
| 0x2353 | 8.1 | the partition table reports an invalid partition size. |
| 0x2354 | 8.1 | debugging mode has been enabled. |
| 0x2355 | 8.1 | driver signature enforcement has been disabled. |
| 0x2356 | 8.1 | of an unknown error. |
| 0x2362 | 8.1 | Recovery key ID: |
| 0x236d | 8.1 | Secure Boot has been disabled. Either Secure Boot must be re-enabled, or BitLocker must be suspended for Windows to start normally. |
| 0x236e | 8.1 | Secure Boot policy has unexpectedly changed. |
| 0x236f | 8.1 | Device Lock has been triggered due to too many incorrect password attempts. |
| 0x2715 | 8.1 | Preparing to refresh your PC |
| 0x4e21 | 8.1 | Your PC needs to be repaired |
| 0x4e24 | 8.1 | You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. |
| 0x4e34 | 8.1 | For more information on how to retrieve this key, go to http://windows.microsoft.com/recoverykeyfaq from another PC or mobile device. |
| 215 entries | ||