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

52 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-12-19T22:22:09+00:00

    I have the same problem described by oldguy3.  It begin today, immediately after update to 1809.

    Controller is Asmedia 106x SATA.

    I, too, prefer my pagefile on my D: drive, which is 1TB spin type (W-D Black).

    Very obviously, another 1809 bug.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-12-14T14:55:26+00:00

    P.S. mine is an intel controller also

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-12-14T14:53:19+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-12-11T09:25:12+00:00

    We´ve got the same problem on Server 2019 1809.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-12-04T15:06:16+00:00

    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

    Was this answer helpful?

    0 comments