| Previous | Next |
| ERROR_VOLMGR_INCOMPLETE_DISK_MIGRATION | ERROR_BCD_NOT_ALL_ENTRIES_SYNCHRONIZED |
ERROR_BCD_NOT_ALL_ENTRIES_IMPORTED
ERROR_BCD_NOT_ALL_ENTRIES_IMPORTED — 0x80390001
ERROR_BCD_NOT_ALL_ENTRIES_IMPORTED means the import operation completed only partially: some source objects or elements could not be brought into the target BCD store.
Start with the failing layer
BCD repair should begin with an export and an inventory of both BCD objects and firmware entries. Object GUIDs, EFI System Partition paths, referenced device elements, firmware NVRAM capacity, and boot order must be correlated; editing one representation in isolation can create a second inconsistency.
A readable store can still produce a partial import; success of the command shell alone does not prove every entry transferred.
Preserve before retrying
- Source and target store paths/hashes, firmware mode, Windows build, and import command/API
- Object GUID list before and after import and the exact entries omitted
- Store ACL, volume availability, referenced device paths, and inherited-object dependencies
- BCDEdit/WMI output preserved before any repair rewrites the store
Three useful comparisons
- Import a copy into an offline temporary store and compare object inventories.
- Export the target first, then test only the missing object/dependency set.
- Validate referenced partitions/devices without changing GUIDs.
A defensible fix
Repair the failed contract rather than the surrounding system: Repair invalid dependencies or inaccessible device references and repeat against a backed-up store, or recreate only the missing entries explicitly.
Close the incident only when object and element inventories match the intended source, the system boots through the selected entry, and rollback from the saved export is tested.
Technical references
The details above are grounded in the following Microsoft specifications and API documentation:
Looking for a different code? Search another status or error code.