Can you still edit the Swapfile size?

[MikeHawthorne]

I remember when I used to edit the space reserved for the Swapfile, once I was using at least one solid state drive I would move the file off of C:\ to the Solid state drive and increase its size while reducing the space reserved for it on C:\,

This used to be very easy and safe to do.
I looked for a place to do that in Windows 11 but I can't find any way to do it, is this still a possibility?

I remember we used to make the new file size about one and a half times the amount of ram we had in those days.
Of course that's not really necessary anymore since we have 64 Gigs of ram.

 

[ChatGPT]

Yes — it’s still possible in Windows 11, but the setting is buried. Also, what you used to edit was almost certainly the page file / virtual memory setting, not swapfile.sys specifically. Windows still lets you manage the paging file from Advanced system settings. (support.microsoft.com)

Where to find it​

1. Press Start and type View advanced system settings
2. Open it
3. Under Performance, click Settings
4. Open the Advanced tab
5. Under Virtual memory, click Change
6. Clear Automatically manage paging file sizes for all drives
7. Select the drive you want
8. Choose System managed size or Custom size
9. Click Set
10. Click OK and restart the PC. Microsoft still documents this path under System Properties → Performance → Advanced → Virtual memory. (support.microsoft.com)

Important clarification​

Windows’ official docs talk about page files (pagefile.sys). They can exist on more than one partition, and their location/size is configured in System Properties. Microsoft’s docs do not present a normal separate GUI for sizing swapfile.sys; the user-facing control is the paging file / virtual memory control. (learn.microsoft.com)

With 64 GB RAM, what should you do?​

I would not use the old 1.5× RAM rule literally anymore. Microsoft says there is no single correct size, and with large physical memory a page file may not be needed for peak commit the way it was on older, lower-RAM systems. However, Microsoft also says a page file can still be needed to support crash dumps and to extend the system commit limit. (learn.microsoft.com)

My recommendation for your setup​

Because your C: space is tight, the safest practical choice is usually:

1. Leave a small page file on C:, or leave C: as System managed
2. Put the main/pagefile growth on a drive with much more free space
3. Prefer System managed on the alternate drive unless you have a specific reason to hard-set numbers. Microsoft notes that system-managed page files can grow automatically when commit usage gets high, assuming the drive has free space. (learn.microsoft.com)

If you want a manual setup​

A reasonable modern approach would be:

1. On C: set either:
   • System managed size, or
   • a small custom size
2. On your roomy secondary drive set:
   • System managed size

I would avoid “No paging file” on C: unless you’re comfortable trading away some crash-dump support and troubleshooting convenience. Microsoft explicitly says page files are used to back system crash dumps. (learn.microsoft.com)

If you want fixed numbers anyway​

If you prefer custom values, use something modest — not 96 GB just because you have 64 GB RAM. The old “1.5×” number was only a starting point, and Microsoft says sizing depends on workload, not a fixed formula. (learn.microsoft.com)

Short version​

• Yes, you can still move/manage it in Windows 11. (support.microsoft.com)
• The setting is under Advanced system settings → Performance → Advanced → Virtual memory. (support.microsoft.com)
• With 64 GB RAM, I’d usually use System managed rather than a huge manually sized file. (learn.microsoft.com)
• If C: is cramped, put the main paging file on a roomier drive, but keep in mind page files also help with crash dumps and commit limit. (learn.microsoft.com)

If you want, I can give you a recommended exact pagefile setup for your current drive layout (C:, D:, F:) based on the screenshot you posted earlier.

 

[MikeHawthorne]

I did what you said and gained about 4 gigabytes moRe fRee space!
I can experiment aRound with it some moRe late

Funny when I typed my oRiginal post I didn't have the R pRoblem it typed just the way you see it, but now it's happening again?

 

[ChatGPT]

That’s a good result, Mike — 4 GB back on C: is definitely worthwhile, especially when you were down to the last few gigabytes.

On the R problem​

The fact that it worked for one post and then came back actually fits the pattern you’ve been seeing all along.
Since you already showed that:

• it happens only on this forum
• it still happened in Incognito
• lowercase r could disappear in the reply editor while other typing behaved differently is an intermittent forum-editor / rich-text editor bug, not a keyboard failure.

Why that makes sense​

If a hardware key were failing, it would fail:

• in other websites
• in other apps
• in the forum search box too

But your behavior has been inconsistent and editor-specific, which points much more toward the post editor script than the key itself.

Practical workaround for now​

When it starts acting up again, I’d use one of these:

1. Type the post in Notepad first, then paste it in.
2. If the forum has a plain text / BB code mode, switch to that.
3. If the post starts out normal, finish it quickly before the editor “goes weird” again.
4. Keep using the space-saving changes you made on C:, since that part is at least helping immediately.

My honest conclusion​

At this point, I think you’ve done enough testing to say:
This is almost certainly a forum editor issue that only shows up under certain conditions on your system/browser combination.
If you want, I can help you write a short, clean bug report for the site admin with the exact symptoms and reproduction steps.