For years now, and across numerous XP Prof and W3KS systems, I’ve observed a curiosity and nuisuance regarding paging files. The objective is to set up paging files on volumes other than on the C: volume. The issue is that on alternate startups Windows will shoehorn itself into a ridiculously small paging file on C: and ignore the settings specified in Advanced Settings for a correctly sized paging file elsewhere. Once starup is complete, Windows complains about low virtual memory. The only reliable fix I’ve found is to reboot a second time, at which time the paging files correctly reflect the Advanced Settings entries.
This nuisance seems to follow most W3KS servers and power XPP workstations that I manage.
In scouring the web on paging files, I have read about and tried setting C: volume paging sized from say 1 MB to 20 MB, while keeping the main paging file on other volumes or drives in line with installed RAM sizes, 2GB, 16 GB, etc. And, unless I’m missing somehting, I’ve tried it all in trying to select a C: volume size that Windows startup ignores.
If for instance, I specify no paging file on C:, on alternate startups, Windows will put one there anyway of a size of its own choosing. On a second reboot, the arbitrary C: paging file will go away in favor of the Advanced Settings one specified for placement elsewhere. If I specify a minimum sized C: volume paging file – say 1 MB (or larger) – on alternate startups, Windows will shoehorn itself into that size and complain later about insufficient virtual memory. But, a second, succesive reboot will fix things.
Thus, when I take down one of our primary W3KS servers or power workstations, I always plan on two, successive re-starts to overcome this issue and have the Virtual Memory settings corrected implemented.
One other thing, generally I do not use the C: volume as the SysVol. It’s a personal preference that provides me more flexibility in the management of these systems. However, I still fail to see the connection between where the SysVol is and the paging files are.
To complicate the matter, this issue is not reflected on every system that I have personally or on systems that I manage professionally. But, many to most have this problem.
What I am hoping for is that someone who reads this has experienced the identical issue and has a surefire fix for it: a registry setting, additional registry entry or KB doc, etc. Thanks in advance!
