Share via

Will using ramdisk for temp folder cause a problem with Windows 10 update?

Anonymous
2024-02-15T14:37:26+00:00

When doing a Windows 10 update to Windows 10 version 22H2, it gets to 30% of the update, then a reboot is done to complete the update. Dose this require that the temp files be saved until the update completes, in which case a ramdisk temp folder would be an issue since it gets reset on each reboot.?

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

8 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-15T00:21:53+00:00

    There is an apparent informational or understanding conflict regarding Windows Updates and their storage location. What I mean by this is that like others I employ a RamDisk for Temp files. However, there are certain occurrences where WUpdate will fail to complete an update that requires a reboot. Temporarily resetting the Temp locations to non-RamDisk storage location permits the WUpdate to complete successfully.

    The conflict that I see is that "Temp" is not equal to "%SYSTEMROOT%\SoftwareDistribution". Resetting WUpdate clears out this directory where WUpdates are stored. Given that, why is a Temp located in RamDisk a factor in 'some' Wupdates?

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    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

  3. Anonymous
    2024-02-17T00:09:39+00:00

    I've avoided doing large updates with ramdisk. I could probably set it to 1GB, so a large update would fail on download, but for now I'm just using a folder on the Windows 10 partition.

    Was this answer helpful?

    0 comments No comments