This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After I updated Windows 10 Pro 64-bit to the October 2018 version 1809 update. I can't set custom size or no paging file in virtual memory properties in drive C:. By after set custom size or
no paging file and restart computer. Has system properties pop up on start up. And pagefile.sys in drive C: still automatically manage paging file size.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hey guys! Today the new 1809 released still the issue is up, so basically I contacted Microsoft Support, A support guy he's name is Adam connected remotly to my computer and checked everything up, I told him what's going on, he saw and understood my problem, me and him made a feedback and he told me a few days and hopefully will be fixed a devs and engineer's will check the issue and forwarded my issue to the devs straight away.
Let's hope it will be fixed :(
I'm having the same issue on new install of Windows 10 x64 1809 Enterprise (fully patched as of 11/23/18) in vSphere 6.7 Update 1. I'm moving the paging file off the C drive to a D drive for Citrix PVS 1808.
My VM had 4GB of RAM.
I usually set the paging file the same as the RAM so min 4096 MB and max 4096 MB. When I boot up, i get the created temporary page file error, and when i check there's a 1406 MB paging file on the C drive. Even if i set the paging file to 2x the RAM at min 8192 MB and max 8192 MB I experience the same behavior.
I experience the exact same behavior in Server 2019, so it seems like its something with the 1809 codebase. Hopefully its resolved soon.
Intel controller for IDE, using 120GB SSD for system drive, would prefer to have the page file in a mechanical drive, 8GB RAM, was running 1803 and updated to 1809 when issue started.
Windows 10 Pro
We´ve got the same problem on Server 2019 1809.
I have the same issue with the re-release of 1809 on Dec 3.
I have applied 2 cumulative updates for 1809 since and still cannot set up swap on a non-O/S drive.
When does Microsoft expect to release an update to fix it?
I did Microsoft updates on Dec 3.
When I re-booted the message came up.
I have seen several others complain of the same issue after 1809 update.
Seems you can no longer use any drive other than C: (or possibly your O/S drive) for virtual memory.
I had a 30 Gig page file on my F: drive and the update deleted it and created the temporary pagefile on C:
Every time I re-create the F: drive pagefile.sys, the O/S deletes it on re-boot and creates the temporary one.
Although it deleted the pagefile.sys on F:
It still shows in the performance, advanced GUI interface used for setting the virtual memory; that 30 Gig is still set on F: (as I set it originally)
After It created the temporary page file, the GUI interface it still indicates that there is no virtual memory on C: (as I set it originally)
So I have set windows to manage the pagefile on C: and await for Microsoft to fix their O/S.
