| Previous | Next |
| STATUS_RESTART_BOOT_APPLICATION | STATUS_INVALID_SESSION |
STATUS_INSUFFICIENT_NVRAM_RESOURCES
Firmware NVRAM could not accept another variable update
UEFI stores boot order, boot entries, Secure Boot databases, and vendor variables in finite nonvolatile storage. A variable update can fail even when the Windows system volume has ample free space because firmware NVRAM has its own capacity, garbage collection, and write rules.
A reboot may allow firmware maintenance to reclaim space, but persistent failure requires identifying stale or oversized variables. Delete entries only through firmware setup, BCDEdit, BCDBoot, or vendor-supported tooling; arbitrary variable removal can make the system unbootable.
What to inspect
- Enumerate firmware boot entries and identify duplicates or obsolete devices.
- Check whether the failure concerns Boot####, Secure Boot, or a vendor variable.
- Reboot once to allow firmware garbage collection, then retest the same operation.
- Update system firmware if the vendor documents NVRAM-management defects.
References
- Microsoft Learn: GetFirmwareEnvironmentVariableEx
- Microsoft Learn: SetFirmwareEnvironmentVariableEx
- Microsoft Learn: BCDBoot command-line options
- Microsoft Learn: Windows UEFI Firmware Update Platform
Looking for a different code? Search another status or error code.