| Previous | Next |
| ERROR_KEY_DELETED | ERROR_KEY_HAS_CHILDREN |
ERROR_NO_LOG_SPACE
Registry recovery logging could not obtain required space
Registry persistence uses hive files and supporting recovery data. ERROR_NO_LOG_SPACE is specifically about space required for a registry log, so it should not be treated as a generic application disk-full message or a missing registry key.
Identify the hive involved and inspect free space, hive growth, and supporting-file health on the hosting volume. Registry log allocation problems can accompany broader registry quota or I/O failures, so correlate adjacent error codes and system events instead of deleting the log files manually. The supporting files are part of the hive recovery mechanism; removing them without a controlled offline recovery plan can make a recoverable hive harder to restore. Stop high-rate configuration writers while collecting evidence if they are rapidly growing registry state.
What to inspect
- Check free space and hive growth on the volume containing the hive files.
- Correlate registry quota, I/O, and corruption events at the same time.
- Do not manually delete hive recovery files as a first-line fix.
References
- Microsoft: Windows registry information for advanced users
- Microsoft: RegFlushKey
- Microsoft: Structure of the Registry
Looking for a different code? Search another status or error code.