So, where is Steam installed, on C: or some other drive?
I understand you have Legacy Horizons installed on E:, but where is Steam itself installed?
As others have said above, I would bet that if Steam is installed on C: then it is using C: for "temp storage" during the install and the 50GB size of H4.0/Ody is too big for the "temp storage" space you have available.
@Imo gave an accurate description of how you can fix it, but personally, I would rather uninstall Steam, and all installed games, completely, making sure to SAVE ALL of your game saves for all of your games first, and as needed.
Also, as I said above, I installed Steam on its own 1TB SSD on my current PC. And, as a consequence of that, this problem is avoided, not that I planned it that way specifically for that reason. I did that so that Steam would not interfere with my boot drive in case I needed to reinstall the OS from scratch, not that that is a problem these past 13 years or so since Win7 released.
That is the setting? I was just wondering what the actual size is.
As I stated above, Steam is installed on my D:, and has a separate library folder on my E:. I am not installing to the C:, and have never had an issue with any other program or game eating up my C: free space (some much larger than ED). I don't see how reinstalling Steam will help, when it currently is not on my C:, but the install is still eating up my C: space.
The setting for my page file is 12487MB, yes. I couldn't find an actual Page file on my C:, even though I can see invisible files. Perhaps Windows 10 has it elsewhere..?
Silly me. I just have a single Samsung 2TB NVMe solid state drive. Everything goes on it. No issues of any kind. Still have around 1.6 TB free.
That's fantastic, but doesn't help me at all. You said 18GB is not enough space on my OS partition, but failed to address why that would be the case when I have no issues with any other programs or installations. I now have 24GB free on C: after some cleanup.
It would appear that ED uses your default OS partition to handle temporary files, even when writing to an entirely different drive. This is an issue with Frontier's installer, not my system.
Last edited: