ERROR_NO_PAGEFILE: Causes, Diagnosis, and 6 Reliable Fixes

TutorialPedia Team

Date Updated

If Windows or one of your applications reports ERROR_NO_PAGEFILE, the machine is running without a usable paging file — the pagefile.sys backing store Windows uses for virtual memory. Without it, the system commit limit collapses to slightly less than your installed RAM, memory-hungry programs fail with allocation errors, and crash dumps can no longer be written. The good news: this error almost always traces back to one of a handful of configuration or storage problems, and each one has a concrete fix.

This guide explains what the error code actually means, shows how to confirm the root cause on a live system, and walks through six fixes — from simply turning automatic paging file management back on to repairing a volume or repairing a broken registry entry. It also covers crash dump sizing rules and the related error codes you may see alongside 578.

Table of Contents#

What Is ERROR_NO_PAGEFILE?#

ERROR_NO_PAGEFILE is a standard Win32 system error code. The official definition is:

PropertyValue
Symbolic nameERROR_NO_PAGEFILE
Decimal code578
Hex code0x242
Message{No Paging File Specified} No paging file was specified in the system configuration.
Kernel equivalentSTATUS_NO_PAGEFILE (NTSTATUS 0xC0000147)

Because it is a Win32 error code — not a bug check (stop error) — you will normally see it in an application or installer dialog, in a setup or API log next to GetLastError() (578), or in the output of a deployment script. The kernel raises the same condition as STATUS_NO_PAGEFILE (0xC0000147), so the wording {No Paging File Specified} can also show up in event logs and driver diagnostics.

What a paging file actually does#

The paging file (pagefile.sys) is an extension of physical RAM. Windows uses it to hold modified but infrequently accessed memory pages so that physical RAM stays free for hot data, and to back the system commit limit. The commit limit is the total of physical RAM plus all paging files combined; Windows will not promise more committed memory than that.

Two consequences follow directly:

  1. With no paging file at all, the commit limit is slightly less than installed RAM. Workloads that legitimately need more than that fail with memory errors — that is when ERROR_NO_PAGEFILE (or the related ERROR_COMMITMENT_LIMIT, 1455) surfaces.
  2. Crash dump capture depends on the paging file. For kernel and complete memory dumps, a paging file (or a dedicated dump file) on the boot volume must exist and be large enough, or Windows cannot write Memory.dmp after a stop error.

Why the Paging File Matters#

The paging file is not just a legacy hard-drive trick. Modern Windows still relies on it in several everyday situations:

  • Memory pressure and commit limit. When physical RAM fills up, Windows moves cold modified pages to the paging file and keeps working. Without a paging file, the first process that asks for committed memory beyond RAM fails outright.
  • Application compatibility. Installers, games, virtual machines, databases, and creative tools routinely reserve large amounts of committed memory. Many of them report ERROR_NO_PAGEFILE (578) or STATUS_NO_PAGEFILE (0xC0000147) when the reservation fails because no paging file is configured.
  • Crash dumps and supportability. If the machine blue-screens and no suitably sized paging file exists on the boot volume, you get no Memory.dmp and no %SystemRoot%\Minidump files — making the crash far harder to diagnose later.
  • Booting with missing storage. If the paging file is configured on a drive that disappears (a replaced disk, a detached VHD, an offline RAID member), Windows logs paging file errors at startup and may fall back to a temporary paging file.

A common related symptom is the boot-time notification "Windows created a temporary paging file..." — a sign the configured paging file could not be created and Windows had to improvise.

What Causes ERROR_NO_PAGEFILE?#

The message says "no paging file was specified," and in practice that happens in six recurring ways:

  1. No paging file is configured on any volume. Someone unchecked Automatically manage paging file size for all drives and then selected No paging file on every drive — often to save space on a small SSD, or as part of image optimization for VDI/RDS golden images.
  2. The configured volume is gone at boot time. The paging file points at D: or E:, but that disk was removed, the VHD/VHDX no longer mounts, the Storage Spaces or RAID member is offline, or the drive letter changed.
  3. The volume cannot hold the file. The target volume is full, nearly full, or file-system corrupted, so Windows fails to create or grow pagefile.sys. (ERROR_PAGEFILE_CREATE_FAILED, 576, is the closely related code here.)
  4. The registry entry is wrong or damaged. PagingFiles under Session Manager\Memory Management points to a nonexistent path, contains a mangled multi-string entry, or was overwritten by imaging/sysprep or a configuration script.
  5. Third-party memory tools interfered. RAM disks, "memory optimizer" utilities, and some performance suites take over paging file management, then leave the system with no paging file when they are removed or disabled.
  6. Platform bugs block the settings UI. On Windows Server 2025, a 32-bit integer overflow can display inaccurate free disk space, which in turn prevents setting the desired paging file size through the standard dialog; Microsoft's documented workaround is to set the registry value directly.

Diagnose the Problem First#

Before changing anything, establish what the machine currently thinks its paging file configuration is. Open an elevated PowerShell window and run:

# 1. Is Windows managing the paging file automatically?
Get-CimInstance -ClassName Win32_ComputerSystem |
    Select-Object Name, AutomaticManagedPagefile
 
# 2. Configured page file settings (applied at startup)
Get-CimInstance -ClassName Win32_PageFileSetting |
    Select-Object Name, InitialSize, MaximumSize
 
# 3. Live page file state right now
Get-CimInstance -ClassName Win32_PageFileUsage |
    Select-Object Name, AllocatedBaseSize, CurrentUsage, PeakUsage
 
# 4. Does pagefile.sys exist on the boot volume?
Get-Item -Path 'C:\pagefile.sys' -Force |
    Select-Object FullName, Length, LastWriteTime
 
# 5. Registry configuration behind all of the above
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management' -Name PagingFiles

How to read the results:

  • AutomaticManagedPagefile : False combined with an empty Win32_PageFileSetting output means no paging file is configured — the direct cause of ERROR_NO_PAGEFILE.
  • A Win32_PageFileSetting entry pointing at a volume that is missing or offline confirms cause 2.
  • A Name entry that exists but no pagefile.sys on disk, or a file with zero length, points at causes 3 or 5.
  • The PagingFiles registry value is the master record: it is a REG_MULTI_SZ value in which each line has the form path initialMB maximumMB, for example C:\pagefile.sys 8192 16384. Windows writes C:\pagefile.sys 0 0 for a system-managed file, and omits drives that have No paging file selected. The Win32_PageFileSetting WMI class is mapped directly to this registry value.

Also scan the System event log for paging file and volume messages:

Get-WinEvent -FilterHashtable @{LogName='System'} -MaxEvents 300 |
    Where-Object { $_.Message -match 'paging file|pagefile' } |
    Format-Table TimeCreated, Id, ProviderName -Wrap

And check free space on the volume that is supposed to host the file — Get-Volume in PowerShell, or File Explorer.

Fix 1: Re-Enable Automatic Paging File Management#

If diagnostics show the paging file was disabled outright, the simplest and usually best repair is to hand control back to Windows.

  1. Press Win + R, type sysdm.cpl, and press Enter.
  2. On the Advanced tab, under Performance, click Settings.
  3. Open the Advanced tab and click Change under Virtual memory.
  4. Tick Automatically manage paging file size for all drives.
  5. Click OK, close the dialogs, and restart.

After reboot, Win32_ComputerSystem.AutomaticManagedPagefile should read True and C:\pagefile.sys should exist again. Windows sizes system-managed paging files dynamically: the minimum varies with usage history and RAM (RAM ÷ 8, capped at 32 GB) plus crash dump requirements, and the maximum is 3 × RAM or 4 GB — whichever is larger — limited to the volume size ÷ 8, with room to grow further if crash dump settings require it.

When to use it: any standalone workstation, laptop, or general-purpose server that is not under a specific storage or dump policy. This is the recommended default.

Fix 2: Set a Custom Paging File on the System Drive#

If you need predictable sizing (for example, on a database or file server, or on an image that must behave identically everywhere), configure an explicit initial and maximum size on the system drive.

  1. Open Virtual memory as in Fix 1 (sysdm.cpl → Advanced → Performance → Settings → Advanced → Change).
  2. Clear Automatically manage paging file size for all drives.
  3. Select the system drive (usually C:).
  4. Choose Custom size and enter an Initial size (MB) and Maximum size (MB).
  5. Click Set, then OK, and restart.

How large should it be?#

Microsoft's sizing guidance is not "1.5× your RAM." Page file sizing depends on two things, both specific to the machine:

  1. Crash dump settings. The paging file (or a dedicated dump file) must be big enough to capture the dump type you selected:

    Dump typeMinimum paging file requirement
    Small memory dump (256 KB)1–2 MB on the boot volume
    Kernel memory dumpEnough for kernel-mode virtual memory usage
    Automatic memory dump (default)Depends on kernel usage; Windows grows it after repeated crashes
    Complete memory dump1 × RAM plus 257 MB (header plus driver data)
  2. Peak system commit charge. Commit charge must stay under the commit limit (RAM + all paging files). If Task Manager or Performance Monitor shows commit charge approaching the limit, add paging file capacity.

A practical approach for a fixed configuration: set the initial size to cover your crash dump requirement and expected peak commit charge, and let the maximum run to about 3 × RAM on a volume with enough free space. For machines where you want crash dumps but no paging file at all, use a dedicated dump file instead — a paging file that is reserved solely for crash dumps rather than normal paging.

Fix 3: Restore the PagingFiles Registry Value#

If the UI is unavailable (Server Core, broken Settings app, the Windows Server 2025 free-space display bug) or the registry entry itself is damaged, repair the master value directly.

Editing the registry carries risk. Back it up first: in regedit, use File → Export and save a full backup to another volume.

  1. Press Win + R, type regedit, and press Enter.

  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.

  3. Open the PagingFiles value (type REG_MULTI_SZ).

  4. Set its data to one line per volume, in the form path initialMB maximumMB:

    C:\pagefile.sys 8192 16384

    Use C:\pagefile.sys 0 0 for a system-managed file. If PagingFiles does not exist, create it as a Multi-String Value with that name.

  5. Restart Windows — the value is only read at startup.

The same change from an elevated PowerShell prompt (the MultiString type and -Force flag work whether the value exists or not):

New-ItemProperty `
    -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management' `
    -Name PagingFiles -PropertyType MultiString `
    -Value 'C:\pagefile.sys 8192 16384' -Force
 
Restart-Computer

This registry value is exactly what the Win32_PageFileSetting WMI class maps to, and Microsoft documents writing it directly as the workaround when the standard sizing dialog misbehaves.

Fix 4: Point the Paging File at a Drive That Exists#

If the registry or the Virtual memory dialog references a volume that is no longer present, the settings silently fail at boot. Typical triggers: a secondary disk was swapped out, a VHD/VHDX stopped mounting, a Storage Spaces or RAID member went offline, or a drive letter was reassigned.

Repair path:

  1. In Disk Management (diskmgmt.msc) or Get-Volume, confirm the expected volume exists and is Online.
  2. If the volume is a VHD/VHDX or removable disk that can return, reattach it so the configured path resolves again.
  3. If the volume is gone permanently, re-point the paging file at an existing fixed volume using Fix 1 or Fix 2 — do not leave stale entries in PagingFiles.
  4. Remove any No paging file selections that are now pointless, and keep at least one fixed NTFS volume hosting a paging file.

Note that with multiple paging files configured, the one that responds first is the one Windows uses most; files on faster disks are favored. A configuration like C:\pagefile.sys 1024 4096 (small, for crash dumps) plus a larger system-managed file on a fast data volume is a common production layout.

Fix 5: Repair the Volume and Free Up Disk Space#

If the target volume is full or its file system is damaged, Windows cannot create or extend pagefile.sys, and you may see ERROR_PAGEFILE_CREATE_FAILED (576) alongside 578.

Check and repair the file system on the affected volume from an elevated Command Prompt:

chkdsk C: /f

Replace C: with the target volume. If the volume is in use, answer Y to schedule the scan for the next restart, then reboot. For suspected bad sectors, add /r (it implies /f and takes considerably longer).

Reclaim space on the volume that must host the paging file:

  • Settings → System → Storage (Storage Sense on Windows 11/10) for a guided cleanup.
  • cleanmgr for the classic Disk Cleanup tool, including Clean up system files.
  • Move user data (Documents, Downloads, media) to another volume — but leave C:\Windows, C:\Program Files, and other system folders alone. Never delete pagefile.sys manually while Windows is running.
  • Extend the volume with adjacent unallocated space in Disk Management if cleanup is not enough.

For a system-managed paging file, remember that Windows sizes the file with a cap of volume size ÷ 8 (with a growth allowance for crash dumps) — a nearly full volume produces a paging file too small to help, even when one technically exists.

Fix 6: Remove Tools That Manage Memory for You#

RAM disks, "RAM optimizers," and some tuning suites temporarily disable or relocate the paging file. If such a tool was uninstalled or crashed mid-configuration, the machine can be left with AutomaticManagedPagefile disabled and no paging file anywhere — exactly the state that triggers ERROR_NO_PAGEFILE.

  1. Identify recently installed memory, RAM-disk, or "performance" software in Settings → Apps → Installed apps.
  2. Use the tool's own "restore Windows-managed paging file" option if it has one, then uninstall it.
  3. Re-apply Fix 1 or Fix 2 to establish a valid configuration.
  4. Restart and re-run the diagnostic commands from earlier to confirm Win32_PageFileUsage reports an allocated page file.

On managed fleets (VDI golden images, RDS hosts, provisioning scripts), audit anything that writes to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. Image-prep steps that set PagingFiles to empty save a few gigabytes in the template but guarantee commit-limit errors and this exact 578 message in production.

Keep Crash Dumps Working#

One of the most overlooked side effects of running without a paging file is losing crash dumps. Requirements documented by Microsoft:

  • A small memory dump needs only a minimal paging file on the boot volume; Microsoft documents the floor as 1 MB in its page file sizing table and at least 2 MB in its recovery-options guidance.
  • A kernel memory dump needs a paging file on the boot volume large enough for kernel-mode memory usage. For reference, Microsoft's sizing table points to a paging file of 1.5 × RAM for systems with 256 MB–1,373 MB of RAM, and at least RAM + 128 MB on 64-bit systems above that threshold.
  • A complete memory dump needs a paging file on a local volume that can hold all of physical RAM plus 257 MB.
  • The default Automatic memory dump starts with a modest paging file; if the machine crashes again within four weeks, Windows raises the paging file to RAM size or 32 GB (whichever is smaller) so the next crash has a better chance of being captured.

If you deliberately want no paging file for paging purposes but still want dumps, configure a dedicated dump file — a file that backs only the crash dump and is not used for ordinary paging. Microsoft explicitly recommends this option for that scenario.

To confirm your dump configuration, check HKLM\SYSTEM\CurrentControlSet\Control\CrashControl (CrashDumpEnabled, DumpFile, MinidumpDir) or the Startup and Recovery dialog, and verify the boot volume's paging file satisfies the table above.

Best Practices and Common Mistakes#

  • Prefer system-managed sizing unless you have a measured reason (commit-charge data, dump policy, or multi-disk layout) to fix the sizes.
  • Never leave the system with zero paging files. The commit limit drops to just under RAM, and crash dumps stop working — the two conditions behind most ERROR_NO_PAGEFILE reports.
  • Keep a paging file on the boot volume even if the bulk of paging lives on a faster disk; this preserves kernel and complete dump capture.
  • Do not hand-tune sizes from folklore. "Initial = RAM, maximum = 1.5–3× RAM" is a rule of thumb, not Microsoft's guidance; size against crash dump requirements plus peak commit charge.
  • Expect to reboot. Paging file changes (including PagingFiles registry edits) only take effect at startup.
  • Do not delete pagefile.sys by hand. Manage it through System Properties, the registry, or CIM; if a stale file is locked, a chkdsk /f and reboot is the safe route.
  • Avoid deprecated tooling. pagefileconfig is marked deprecated, and the WMIC command line (wmic pagefileset, wmic computersystem) has been deprecated since 2016; on Windows 11 version 24H2 it is disabled by default and installable only as an optional feature, with removal planned. Use PowerShell CIM (Get-CimInstance) and the registry instead.
  • On Windows Server 2025, if the Virtual memory dialog refuses a size change because free space looks wrong, fall back to the PagingFiles registry method (Fix 3) — this is Microsoft's documented workaround for the free-space display overflow.

These codes appear in the same troubleshooting territory but mean different things:

CodeHexMessage / meaningTypical trigger
ERROR_NO_PAGEFILE (578)0x242{No Paging File Specified}No paging file configured anywhere
STATUS_NO_PAGEFILE0xC0000147Same message, kernel NTSTATUSSame condition, seen in kernel/driver contexts
ERROR_PAGEFILE_CREATE_FAILED (576)0x240{Unable to Create Paging File}Volume full, corrupted, or missing
STATUS_PAGEFILE_CREATE_FAILED0xC0000146Same message, kernel NTSTATUSSame condition
ERROR_COMMITMENT_LIMIT (1455)0x5AFThe paging file is too small for this operationCommit limit reached during memory allocation
ERROR_COMMITMENT_MINIMUM (635)0x27B{Virtual Memory Minimum Too Low}Windows had to grow the paging file under pressure
ERROR_PAGEFILE_QUOTA_EXCEEDED (567)0x237Page file quota was exceededPer-process page file quota exhausted

Frequently Asked Questions#

Is ERROR_NO_PAGEFILE a blue screen (BSoD) error? No. It is a Win32 error code (578 / 0x242) returned to user-mode applications and scripts. It can appear on machines that also experience stop errors, but 578 itself is not a stop error code — and running with no paging file additionally prevents crash dumps from being written when a stop error does occur.

Can Windows run without a paging file at all? It can boot and run light workloads, but the commit limit falls to slightly less than physical RAM, so any workload that overcommits memory will fail with allocation errors, and crash dumps cannot be captured. Keeping at least a small paging file is the safe configuration.

Does adding more RAM make the paging file unnecessary? No. RAM reduces paging activity, but the paging file still backs the commit limit, absorbs modified idle pages, and supports crash dumps. Even 64 GB workstations benefit from a system-managed paging file.

I have plenty of RAM and an SSD. Is it safe to disable the paging file to save writes? The write-volume concern is largely outdated, while the downsides are real: a hard commit ceiling and no crash dumps. Leave a system-managed paging file in place.

How do I set the paging file without the GUI on Windows 11 24H2 or newer? Use the PagingFiles registry value (Fix 3) or PowerShell CIM for inspection. Avoid wmic — it is deprecated and disabled by default on new Windows 11, version 24H2 installations.

The machine boots with a message about a temporary paging file. Is that the same problem? It is the same family of failures: Windows could not create the configured paging file (usually a missing volume or a full/corrupt disk) and fell back to a temporary one. Work through Fixes 3–5 and the diagnostic steps above.

Conclusion#

ERROR_NO_PAGEFILE (578 / 0x242, kernel STATUS_NO_PAGEFILE 0xC0000147) means Windows has no paging file to back virtual memory — and the fix always starts by finding out why. Verify the state with Win32_ComputerSystem, Win32_PageFileSetting, and the PagingFiles registry value; then re-enable automatic management, set a sized paging file on an existing volume, or repair the registry entry, the volume, or the disk space that is blocking pagefile.sys. Whatever route you take, keep a paging file (or a dedicated dump file) on the boot volume so crash dumps remain possible, size it against dump requirements and peak commit charge rather than folklore, and reboot to let the change take effect. With a valid paging file restored, the 578 error disappears — and the system regains both its full commit limit and its supportability story.

References#