Just to ask a really quick question right of the bat. Does Windows 10 allow for a pagefile.sys to be stored on A: ?
I have tried every trick in the book right now. Different sizes, system managed size and all and everything. Just haven't tried to add the pagefile to any other drive than A:
I just googled this now, and there was this one website that said that i should not use drive A: and B: for anything system specific. But if this is the case, wtf..
Floppy drives? 2021? This can't be true right?
i actually just started using A: and B: for NVMe disks a few months ago, i was like, holy damn yeah i have two letters above C: i can use, but of course never did in the old days because they were reserved for floppy drives. But floppy drives aren't even a thing anymore, so is that even a thing now? Why would W10 treat drives on A: and B: any differently than C-Z?
Anyways, reason i want my pagefile on A: is because of my 3600TBW NVMe that is assigned there. The system disk (C) is a smaller expensive 500GB gen4 NVMe with only 300TBW, so i don't want any more wear and tear on that drive than i need to. And i also run 48GB of RAM. So i want my pagefile to be on the 2TB 3600TBW A: drive. But no matter what i do, Windows wont allow me to. Windows creates a temporary pagefile at startup. So is this in fact due to the drive being on A:? Like seriously?
If that's it, that's actually mind blowing to me. That's like not being able to play 1991 DOS games in Dos Box because no ISA ports are found on the motherboard.
Or is something else fishy going on here?
Anyone come across this problem before?
I have so many disks and drives connected to my PC i run out of letters. This is primarily why i started to use A and B after all these years.
I have tried every trick in the book right now. Different sizes, system managed size and all and everything. Just haven't tried to add the pagefile to any other drive than A:
I just googled this now, and there was this one website that said that i should not use drive A: and B: for anything system specific. But if this is the case, wtf..
Floppy drives? 2021? This can't be true right?
i actually just started using A: and B: for NVMe disks a few months ago, i was like, holy damn yeah i have two letters above C: i can use, but of course never did in the old days because they were reserved for floppy drives. But floppy drives aren't even a thing anymore, so is that even a thing now? Why would W10 treat drives on A: and B: any differently than C-Z?
Anyways, reason i want my pagefile on A: is because of my 3600TBW NVMe that is assigned there. The system disk (C) is a smaller expensive 500GB gen4 NVMe with only 300TBW, so i don't want any more wear and tear on that drive than i need to. And i also run 48GB of RAM. So i want my pagefile to be on the 2TB 3600TBW A: drive. But no matter what i do, Windows wont allow me to. Windows creates a temporary pagefile at startup. So is this in fact due to the drive being on A:? Like seriously?
If that's it, that's actually mind blowing to me. That's like not being able to play 1991 DOS games in Dos Box because no ISA ports are found on the motherboard.
Or is something else fishy going on here?
Anyone come across this problem before?
I have so many disks and drives connected to my PC i run out of letters. This is primarily why i started to use A and B after all these years.
Last edited: