Hello,

maybe its only a problem of mine. I had Cyberpunk 2077 from Day 1 to Patch 1.06 on my SSD, moved it to my HDD (space problems), moved it back to the SSD 2 days ago. GOG re-checked the game, tried several downloads of sizes 30 GB to 57 GB and the server always had problems and I got error-messages. So I installed it completely new 2 days ago. Version 1.10 Today I start GOG, a new update is visible, 1.12, a new download is there: 57 GB. The servers crash again. I know from friends, that the Steam-Update has only a few MB.

Do I have to completely download new 50GB+ for every patch? (including the constant "errors" from the Server, I now have to wait several hours to play the game further ...)

Do you have the box your pc came in? (hahaha, couldn't help it)

Dude, patch is 14mb.

If your client is trying to download the entire game it's probably because it doesn't think you have it installed. Maybe because you moved it huh?

You need to tell the client the updated location of the game files. If you don't know how to do this, then you shouldn't be moving them.

no, i played the 1.11 version 2 days ago after a complete new installation.

You've messed with it. But it can be "fixed" much faster than new install.

If you moved/copied "Cyberpunk 2077" to e.g. your second PC (like I did; GOG.com allows such thing) use "import" function of GOG Galaxy:
https://www.gog.com/forum/general/gog_galaxy_how_to_import_games/post3

If you have CP2077 on your two PCs and you updated one only then you can copy the game (without need of downloading it again) to second PC. To make GOG Galaxy recognize it correctly you need to make a trick:
1) make sure GOG Galaxy is not running, is closed
2) after coping/moving rename "Cyberpunk 2077" folder (e.g. _new_Cyberpunk 2077)
3) start GOG Galaxy - it will not find the game and will "think" it was uninstalled
4) close GOG Galaxy
5) rename folder again to its original name "Cyberpunk 2077"
6) start GOG Galaxy and use "import" function (see: above link).

After this GOG Galaxy will not try to download again entire game (c.a. 60 GB). Works for me.

Or you could just stop using Galaxy and use offline installers.

Amazing the amount of issues people have with Galaxy - half of these threads are about how Galaxy misperforms, re-downloads, hangs, does not register achievements etc. Yet GOG continues to persist with this.

Sometimes you need to learn how some programs work to use them. They are not idiot proof. And for patching sometimes patches need double the space so it can replace all files. If you dont have enough space delete something first or buy bigger disk. Its almost always user error when someone encounters some issues with patches and games. Or buy console if you cant handle PC :)

GOG Galaxy has now new function - user can set folder for downloads on different drive than installed games.

Example:
Folder "GOG Games" is on fast SSD disk but it's not big enough to take several GB patch for e.g. Cyberpunk 2077. User can set download folder on HDD disk. Installing and/or patching can be slower but still possible.

This may not be an option for some, but 1TB SSD drives (SATA and M.2) are near $100 for good quality storage.

Even a lower speed SSD will out preform a higher end mechanical drive by 200% or more

The patch was only 14MB, but it needed a spare 70G for tmp files to patch

This is a common misconception a lot of people have about how big a patch is for a game compared to how much free disk space you need in order to install that patch. A downloaded patch file on its own takes up the size of the patch on your local storage but it is not installed into the game in a usable patched state, it is just a downloaded unapplied patch that takes up space.

This doesn't matter if you are using GOG Galaxy, downloading the installer files and patches to install things locally from EXE files yourself, or if you are doing it on Steam or some other platform. In all cases you're going to end up with an installed game and a big patch file that has to be installed that takes up space, and that needs a potentially large amount of space to reconstruct the new patched version of the game while it installs the patch.

So when the patch is actually installing, it is basically taking the original multi-gigabyte files the game has already got installed and duplicating those files on your local disk, applying changes from the patch to them as it goes. While this is happening you have the original game taking up say 60GB of disk space, plus a patch file that is say 15GB, possibly some extra space in the temp directory to decompress that patch file into a usable state for patching, then you need free space to copy the original game files and patch them with the new bits and pieces contained in the patch. Depending on just how much of the original game files the patch patches, the entire patching process could require 60GB or more of disk space on top of all of this just to be able to patch the game. Once the patching is successfully completed, the patching process can then clean up after itself and delete the original game files of the old version of the game, any temporary files it created during the patching process, and even delete the patch file it downloaded thus freeing up a tonne of space even though it needed to have all of that space in order to download and install the patch.

So a 5GB patch that downloads in a few minutes time could actually require 60GB of disk space in order to apply itself to the game files that are already installed, then free up most of that space once it is done. The end result being that the same amount of disk space is used before and after a patch more or less give or take a few megabytes, but the process of patching requires temporary disk space to do the actual work.

This is how delta patching works more or less, downloading the least amount of data and reconstructing the final version of the files from the combination of the original game files plus the delta that was downloaded. The other option which would use the least disk space would be just not using delta patching and re-download the entire already patched version of the game. That would simply uninstall or delete the current version of the game freeing up all the disk space it uses, then download the entire game already patched. The end result would be using the least amount of disk space, but burning up tonnes of Internet bandwidth redownloading tonnes of data that one technically already had installed which isn't changing.

So delta patching greatly reduces network bandwidth and speeds up the patching process at the expense of potentially using more local disk space temporarily during the patching process, and can briefly double the disk footprint of the given game in the worst case scenario.

Moving games around the system from drive to drive can further cause some idiosyncrasies that can throw a wrench in the process, but others have talked about that already I see.

TL;DR version: We all need to get bigger storage devices to embrace modern games. Now I need to go free up 40GB of space for the upcoming game patch... :)