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.
This issue is seen only on PCs with specific storage controllers. Mahfoud is seeing this on his Jmicron storage controller. Can people who are hitting this issue, please share their storage controller information (vendor name and/or PNP device ID)?
(win+r, msinfo32, System Summary, Components, Storage, IDE)
Building Xendesktop with 1809 and I have this issue. I can't move the pagefile to any other drive.
Built Xendesktop with 1803 and no issue.
I hope somebody check this
Hello,
I've the same problem and my controller is a jmicron. Unable to set paging file.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Same problem after upgrading to 1809. Can't move/use pagefile to/at non C drive. System just ignores it after creation and uses only C drive pagefile (Intel controller if it matters)
