Windows 10 1809 update + KB4464330 can't set no paging file in System Drive (C:)

Anonymous
2018-10-08T03:44:59+00:00

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.

Windows for home | Windows 10 | Windows update

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.

0 comments No comments

52 answers

Sort by: Oldest
  1. Anonymous
    2019-01-05T22:32:50+00:00

    I finally found a solution to this problem. As someone already said in this thread, Windows 10 build 1809 doesn't allow to have the paging file on "portable drives" anymore. So if you click on the "Safely Remove Hardware and Eject Media" icon in the system tray and you see the drive that you want to use for the page file there, then Windows will refuse to use it. The problem is that the BIOS on some older motherboards seems to report the internal SATA ports as "external" ports to Windows. There are now two solutions:

    • Deactivate this behavior for the SATA ports in the BIOS (it should be called "hot-swappable", "non-removable" or something like this). However, this seems to only be available on newer mainboards.
    • Tell Windows that the SATA ports are non-removable.

    I had to use the second solution. Here you can find a nice guide:

    https://superuser.com/a/961242

    I'm not sure how to get the number of a specific SATA port, I also used 0 to 5. Maybe it's the SCSI bus under win+r, msinfo32, System Summary, Components, Storage?

    I hope this helps.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-01-08T07:06:19+00:00

    In my case the problem was solved when I disable the Hot plug in the BIOS, in HOT PLUG mode the mechanical hard drive is detected as External Hard Drive so windows 10 1809 do not permit the creation of the pagefile in that drive. apparently it is a new directive in windows 10 1809 because in 1803 it was not necessary to change the information in the BIOS.

    in this post you can follow the instruction for those who don't have this option in the BIOS.

    https://www.reddit.com/r/Windows10/comments/9lpvwn/paging\_setup\_after\_the\_2018\_october\_update/

    I hope this information helps you.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-01-15T13:43:07+00:00

    killing hotplug isn't really a solution per say, but a workaround, and a pain to try to dig up without great success with what's been posted.

    I don't want to disable sata hotplug support, I WANT hotplug support. I know enough to not eject my paging drive. I want to disable this "feature" which has much more responsibility being a warning pop.

    I'm also a systems engineer and this breaks VDI in windows because of vmware horizon view generating a scratch disk on build. It's a bigger issue than many people likely realize.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-01-23T17:51:03+00:00

    Latest WU update (released on 01/22/2019) resolves this issue for 1809 users:

    https://support.microsoft.com/en-us/help/4476976

    "Addresses an issue that occurs if you create a page file on a drive with FILE\_PORTABLE\_DEVICE characteristics. The “Windows created a temporary warning” message appears. "
    

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-01-28T14:01:48+00:00

    I can confirm this is also an issue with the latest updates to 1803.  Started experiencing it today after fully updating.  No issues prior.

    Was this answer helpful?

    0 comments No comments