Move the Windows Page File Before Removing a Data Volume

Technical review: 26 October 2026. Product names, licensing references and procedures reflect this review; check the linked documentation for your release.

Windows can refuse to remove a volume because the paging file is active on it. Free space and administrator rights do not remove that dependency. The safe sequence is to provide a suitable replacement, restart, verify the active paging file and only then continue with the storage change.

Confirm the actual dependency

Use Disk Management to record which volume is labeled Page File. Also distinguish Boot, System, recovery and application-data roles: those labels describe different dependencies. Do not force a disk offline simply because the drive letter looks like an ordinary data volume.

Get-CimInstance Win32_PageFileUsage |
    Select-Object Name, AllocatedBaseSize, CurrentUsage, PeakUsage
Get-CimInstance Win32_PageFileSetting |
    Select-Object Name, InitialSize, MaximumSize

The usage class helps identify paging files active in the current boot. The settings view describes configured explicit settings and may not tell the full story when automatic management is enabled. Save the output privately together with the current Virtual Memory and crash-dump configuration.

Check memory-dump requirements first

The page file supports committed memory and can also be part of crash-dump collection. Moving everything away from the Windows volume without checking the dump design can leave the server unable to capture the diagnostic dump you expect. Requirements depend on dump type, memory size and whether a dedicated dump file is configured.

Check free space on the replacement disk and use Microsoft’s sizing guidance for the workload. Avoid a universal rule such as “the page file must always be exactly 1.5 times RAM.” System-managed sizing is often appropriate, but it still requires available disk space and a recovery design.

Change the configured location

Open sysdm.cpl, then Advanced, Performance Settings, Advanced and Virtual memory. If automatic management is enabled, understand its current behavior before changing it. Under an approved maintenance change, configure the replacement volume and use Set to save that selection. Remove the old volume’s paging-file setting only after the replacement and dump requirements have been accounted for.

Record every setting before applying it. Windows may request a restart; a configuration change is not proof that the old paging file has stopped being used. Arrange console access and a normal reboot rather than attempting to delete an active pagefile.sys.

Verify after the restart

• Repeat the active-usage query and confirm the old volume is no longer hosting an active paging file.
• Confirm the intended replacement has space and that the system’s dump configuration still meets requirements.
• Check services and applications for other references to the old drive, including logs, databases, shares and scheduled tasks.
• Retain the original storage layout until the change window has a clear acceptance result.

Only after those checks should you consider deleting or relettering the old data volume. Deleting a partition does not guarantee that C: can extend into it: adjacency, partition style and filesystem support still matter. If results are unexpected, restore the recorded settings and postpone the storage removal rather than forcing it.

References

• Microsoft: page-file sizing guidance
• Microsoft: crash-dump configuration recommendations
• Microsoft: Win32_PageFileUsage