| Previous | Next |
| ERROR_APP_INIT_FAILURE | ERROR_INVALID_IMAGE_HASH |
ERROR_PAGEFILE_CREATE_FAILED
What this result means
ERROR_PAGEFILE_CREATE_FAILED is a Windows system result. Windows attempted to create or initialize a paging file but could not use the configured path, volume, permissions, or size. Commit capacity and crash-dump support may be reduced.
Why it can appear
- the target volume lacks free space or is unavailable early in boot
- paging-file configuration references a removed or encrypted volume
- filesystem corruption or storage errors prevent creation
- permissions, policy, or a filter driver interferes with the paging file
Diagnostic workflow
- record configured paging-file paths and size policy, volume free space, filesystem, and boot events
- check storage, filesystem, filter-driver, and memory-management logs
- verify that the volume is available at boot and supports paging files
- inspect recent disk-letter, encryption, storage, or policy changes
Correct recovery and handling
Restore a supported system-managed paging file on a healthy local volume and reboot when required. Preserve enough free space for growth and dump policy. Investigate recurring storage errors.
Administrator and support checklist
- confirm whether the condition is isolated to one machine, one user, one file, or one application build.
- Compare the host reporting this result with a known-good system using the same Windows edition and policy.
- Review updates, drivers, security-policy changes, restores, and infrastructure incidents that preceded this result.
- Preserve logs and dumps associated with this result before rebooting when the failure may be intermittent or destructive.
- Use vendor-supported repair or rollback steps for this Win32 error instead of copying system files or disabling protections ad hoc.
Developer guidance
When handling it, log the API or subsystem that returned it, the first lower-level failure, relevant object identifiers, process and thread context, and safe operation parameters. Preserve the original numeric Value rather than converting it to an unrelated HRESULT or NTSTATUS. Retry it only when the evidence shows a transient dependency; deterministic it cases involving policy, format, compatibility, or integrity should fail fast.
What to record in telemetry
- Windows build, architecture, and component version for the result event
- the first result timestamp and the operation then in progress
- process, thread, session, and target object associated with it
- warnings or lower-layer status values immediately preceding it
- whether retry, restart, rollback, or repair changed the result outcome
Example investigation pattern
Investigate it by reproducing the operation once with detailed logging, then correlate that timestamp with Windows events and lower-layer traces. Compare the affected object or process with a known-good one, change one variable at a time, and stop retrying When it is deterministic. That method keeps the first relevant failure from being hidden by secondary cleanup messages.
Related and easily confused conditions
This is different from having no pagefile configured: here Windows tried and failed to create one.
Operational note
Do not diagnose it from its text alone. The result can cross subsystem boundaries and may summarize an earlier, more specific event. The first failure in time is normally more useful than the last message printed during cleanup.
References
Looking for a different code? Search another status or error code.