| 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
The short system message identifies the immediate outcome, but the useful interpretation is narrower: partial BCD import. In this case, 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.
Do not collapse this result into a nearby status. A readable store can still produce a partial import; success of the command shell alone does not prove every entry transferred. Compare lifecycle, identity, caller, and first API.
Preserve before retrying
| Record | How it narrows the cause |
|---|---|
| Source and target store paths/hashes, firmware mode, Windows build, and import command/API | Creates a stable before/after control. |
| Object GUID list before and after import and the exact entries omitted | Tests whether the first boundary moves. |
| Store ACL, volume availability, referenced device paths, and inherited-object dependencies | Pins evidence to one attempt. |
| BCDEdit/WMI output preserved before any repair rewrites the store | Separates contract failure from environment. |
Identifiers, timestamps, versions, counts, state flags, hashes, and redacted paths normally provide enough correlation. Keep credentials, private keys, message bodies, recovery material, and personal data out of routine incident logs.
Three useful comparisons
- Import a copy into an offline temporary store and compare object inventories; keep every other input fixed and record the first event that differs from the failing run.
- Export the target first, then test only the missing object/dependency set; use a disposable or backed-up environment when the comparison changes boot, security, device, queue, or encryption state.
- Validate referenced partitions/devices without changing GUIDs; retain one negative control so that a broad workaround is not mistaken for a root-cause correction.
A retry becomes evidence only when one controlled variable changes. In this case, if the same operation later succeeds unchanged, preserve that fact but continue checking timing, object generation, service restart, cache replacement, or policy refresh; transient success does not explain the earlier boundary.
Decision points
Interpret the controlled tests as evidence about the returning boundary:
| Observed result | Interpretation |
|---|---|
| The minimal or known-good comparison succeeds | The control works; inspect production-specific state. |
| The control fails at the same first operation | The control also fails; inspect host/provider evidence. |
| A new HRESULT marks another boundary | this boundary moved; diagnose the new status separately rather than treating it as confirmation that the entire operation is fixed. |
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. Preserve the pre-change configuration or trace.
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. Repeat under the original identity and state. A different environment is comparison, not proof.
Technical references
The diagnostic boundaries above are grounded in the following Microsoft specifications and API documentation:
- Microsoft Open Specifications: HRESULT values.
- Microsoft: boot options in Windows.
- Microsoft: BCDEdit command-line options.
- Microsoft: BcdStore class.
Looking for a different code? Search another status or error code.