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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-02-04T00:20:52+00:00

    Hey Greg... I'm having a similar issue with how Windows 10 v1809 manages the Pagefile size on my OS SSD... In my particular case Windows forces a very large Pagefile on C: Drive... Initially it started at 4gb right after I upgraded to v1809... Then jumped up yo 9gb about a month ago... And currently Windows keeps it at 11 gb... FYI... My rig has 16gb G.Skill FlareX 3200-DDR4 kit... 

    I am however, able to manually set the Pagefile to a fixed min/max value... But that in turn keeps causing a few Steam games to freeze for some weird reason... Specially since my dGPU is an ASUS DUAL OC AMD RX-580-o4gb... For now though I opted for moving the Pagefile to my Secondary 1 TB HDD... Windows maxed out the Pagefile at 32gb though... I manually have it set now at 16gb min/max...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-01-29T14:15:01+00:00

    I can confirm this. 1803 VDI with latest updates and pagefile creation error. This is really bad because its our PVS VDI so pagefile on c-drive is IMPOSSIBLE. But now we have no page file at all.

    I already created microsoft support case for this in which I ask when they will release the patch for 1803. 

    FYI,

    1803 is currently unsupported for VDI for VMWare still. I wouldn't recommend migrating parent images, it most definitely will crash and burn in horizon view creating scratch disks but you won't know till you wiped out the pool.

    Microsoft definitely needs to fix this if they want anyone using vdi to go forward and to get certification from VMWare anytime soon.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-01-29T13:44:54+00:00

    I can confirm this. 1803 VDI with latest updates and pagefile creation error. This is really bad because its our PVS VDI so pagefile on c-drive is IMPOSSIBLE. But now we have no page file at all.

    I already created microsoft support case for this in which I ask when they will release the patch for 1803.

    Was this answer helpful?

    0 comments
  4. 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
  5. Anonymous
    2019-01-05T14:57:51+00:00

    No setting in the bios to change the status of the hard drives. In windows  all my drives appears in the menu to be ejected including my SSD (C:). I can set a paging file on C: but not on the others drives.

    Was this answer helpful?

    0 comments