As long as you have no updates paused or pending, you can always and safely clear this folder out manually if it's built up cruft. This can build to staggering levels over time (I once had ~75GB of orphaned Fallout 4 patches during the game's primary update lifetime). In addition, if a patch is downloading and paused while a new patch is detected, the old paused file will remain while the new delta is downloaded. If a download fails, it will try again under a progressed file name while often leaving the failed file fragments in place. Steam treats downloads much in the same fashion as a browser. Listings removed from the workshop are not auto-unsubscribed, leading to broken mods being left active in games and installed locally, and uninstalling games does not always delete the local workshop folders. The Steam Workshop distribution system is convenient, but sloppy. Be warned, however, that if a game stores saves in the install folder and does not use cloud, deleting these orphaned folders can delete saves. Beyond using WinDirStat to track the possible culprit as already recommended, I can give you at least three possible sources:Įven after uninstalling a game, there's a chance files are left behind not every game's uninstaller is configured to delete its install folder entirely, and most only delete files listed in a pre-written log which doesn't account for patches.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |