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
    2019-05-14T16:52:29+00:00

    I did MS updates today hoping issue is resolved, it reinstalled KB4493509 and installed KB4495667.

    ODBC connection issue is back.

    KB4493509 not available for uninstall.

    uninstalled KB4495667 and KB4493509 then was available for uninstall and I uninstalled it.

    ODBC connection good again.

    Maybe MS will fix for next month's update Tuesday... Don't hold your breath.

    Was this answer helpful?

    0 comments
  2. VARADHARAJAN K 9,726 Reputation points Volunteer Moderator
    2019-05-10T10:53:55+00:00

    currently your page file is 5916MB  , but you trying only 400MB so geeting error messages

    try to set 6500MB to 6600MB

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-10T01:42:31+00:00

    I've just updated my PC with a new mobo and clean install of Windows Pro (1809), and can't move the pagefile to a second disk. Windows reports the disk as fixed (not portable or ejectable), and hot swap is disabled in the bios.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-01T14:21:39+00:00

    ISSUE IS BACK

    Re-cap:

    1809 pagefile issue - windows not recognising a pagefile on a non-O/S drive.

    After a subsequent Microsoft update, the issue was resolved. Was able to use a pagefile on a non-O/S drive again.

    Recent:

    Later I found apps using odbc connections from my workstation to SQL Server on a server, crashed randomly.

    To resolve this new issue, I uninstalled KB4493509.

    This resolved the odbc connection issue.

    But, now the original pagefile issue of windows not using my defined pagefile on my F: drive is back and windows created a temporary pagefile on C: drive.

    app using ODBC issue event log:

    Faulting application name: zim.exe, version: 7.1.1.1539, time stamp: 0x4b7c563d

    Faulting module name: ntdll.dll, version: 10.0.17763.404, time stamp: 0xe1cce3af

    Exception code: 0xc000041d

    Fault offset: 0x0010196f

    Faulting process id: 0x113c

    Faulting application start time: 0x01d4ff7cc03c9b4b

    Faulting application path: C:\Program Files (x86)\Zim\7.11\zim.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

    Report Id: 0c6a61f1-7b26-4f6e-b77c-1992ac8ad1b7

    Faulting package full name:

    Faulting package-relative application ID:

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-03T14:53:51+00:00

    Thank-you Sandeep for your info and encouragement to try again.

    I have been keeping my O/S up to date and re-tried today to create a pagefile.sys on my F: drive without the O/S ignoring it and creating another on C: drive: This time it was successful.

    My hard drives are still listed in the Safely Remove Hardware and Eject Media system tray list, but that doesn't matter to me much.

    I was not about to perform the next most likely solution posted; of downloading and installing new disk controller drivers from Intel to replace the generic windows 10 drivers.

    Was this answer helpful?

    0 comments