The last few days, I've been running FS with an XP system setting of'No page file'.I have two hardware profiles set up, one for normal use and one for FS9 with minimal services running. The procedure I have been using:1. Set the page file to none.2. Reboot with the FS9 profile.I assumed that the page file size applied to the entire system regardless of which profile is used and perhaps this confused the operating system.Anyway, what is happening is that my disk usage has gone from 69% free to 57% free in several days. I noticed this when defragging.The two green bars (system restores and page file) on the defrag screen look normal. What's eating up the drive are blue colored and I am guessing that they are orphaned page files. There is only one pagefile.sys listed on this drive.When I noticed the problem and guessed that this is what was causing it, I did the above mentioned process again and, sure enough, my free space went from 59% to 57%, so I am almost certain that this is what is causing it.How do I delete these presumably orphaned files and recover the disk space? Are there any disk utilities that would identify them? The registry maybe?I have tried:1. Ran Chkdsk with the repair option.2. Changed the pagefile size to none and rebooted with my normal profile and the green colored pagefile was indeed gone, however the blue colored areas were still there.3. Searched MS knowledge base and the web for a solution. No joy.4. Next would be trying a system restore, but I have installed a few FS addons and changes since the time that I think this started and I would rather not have to resort to that if there is a another solution.Help

The only time I have seen these files is when, while working with large sound files and an editing suite, I shut the computer down witout waiting for the page file to `give up` the file space. I have noted that FSX takes a l-o-o-o-n-g time to shut down properly and return the paging space to available-for-use. Possibly that is what has happened here.Delete the page file, defrag the drive, reboot, restore the page file, defrag again, reboot. That's my usual procedure to correct virtual memory problems and it seems to work to remove the orphans.The other solution is a boot-time defragmentation, only possible with aftermarket defrag utilities like Diskeeper and O&O.Allcott

AllcottI set the page file back to the way I have always had it. That is, a fixed number and it works the way it always has with no problems, so I am relatively certain that that's what they are. I can delete the current page file and defrag, but the rogue data areas are being treated as normal data.If I defrag, they get defragged also. It's as if the XP page file process no longer considers them page files, however they still exist. Chkdsk says everything is OK.Tried to do system restores from several restore points from the past week and they all say 'unable to restore', so that is not an option. I did a current backup and restore just to see if it still works and it does.Did a search on files greater than 50,000 KB using the search function and it lists one pagefile.sys, hiberfil.sys and several recognizable files including the FS Evp files. This must mean that the NTFS file directory does not know that they are there.I think I've already tried what you mentioned, but I'll try again and also try chkdsk again.