But basically all Yakuza, except the newest title, i was downloading the past few days are damaged, Integrity failed.

There is a high chance, actually almost certain... this issue is caused by the GoG servers.

There is no evidence that the failure is on my side... i was checking it so many times, so it seems very certain this is a critical GoG server issue. Taking into account the high issues involed not so many days ago, its is no fairy tale to me, most likely truly a fact.

I never had a issues like this on GoG, and this problem is critical... i dunno if they notice this scale of failing.

I hope there is some solution to be found rather quick, especially that the data currently stored is now proper, i lack the trust... because all the data i was downloading the past week is useless to me; the risk of corruption simply to high. I dunno what was happening exactly but if the server is burning... i would call a fireguard and 24h of work for the most huge mess possible on a datacenter. I do not care a slow server... it may happen, but corruption? OOps... i would worry a lot if this is my datacenter.

Somehow speechless... yet still speaking.

I had a failed drive a month ago and no cash for backup drives big enough (because the entire new PC was such a expensive mess), so in order to be safe i wanted to redownload the newest data as i finally got me 2 new 20 TB drives (with the very last coins, it was simply to important to me). Yet, the issue is that i can not trust those servers anymore... because the past weeks the servers was nothing but unstable and non reliable, now this is really bad luck and guess i have to redownload everything once again.

I only wonder if this issue has finally been sorted... this is a good question it seems. As i heard comparable issues on the newest BG3 downloads. I dunno if they even notice the level of fail... i think CDPR may have to invest more into the heart of GoG; yet if there is no competent workers... no cash can help.

Did you miss the news about the catastrophical server crash?

There are several broken downloads around now. Please report to GOG so they can reupload working files. The forums is not the most certain place for GOG to see this.

Have you tried re-downloading to see if the error is repeatable. Pick one game/file and try again and see if the problem is still there.

I don't have Yakuza so I can't check, but I can confirm that Dishonoured 2 and KSP (downloaded on Saturday) were fine.

If you still have issues, make sure you raise a support ticket.

There are several hundreds of games... and the amount of failed games so huge, on a support not really working, it is just beyond any scale i can manage... my nerves. The stuff should simply work... why should users have to deal with server integrity? Seriously...
Maybe i do expect to much... i was always of the more demanding nature, therefor with lesser love achieved.

The new Yakuza 0 i just redownloaded is now working but the old one i downloaded a few days ago was corrupted, along with almost the entire series...

Now i simply have to download everything again, single check every file; i guess almost a week of work. It would be way easyer if not, at so many spots, so many things simply fail. Indeed, lately i had the highest amount of harware issues in my whole life and even the servers was failing hard; someone indeed can have bad luck.

What i want to know simply is: Is it fixed now? I am not so sure... and why it is even happening exactly... after all those years, i think they should finally start to get the hang of it "on how to manage".

In a word: Hypothetically.

It's the real world. Things go wrong. Should doesn't mean will.

GoG flagged that they had issues on the site, they flagged when they believed the issue had been resolved. It looks like you may have been downloading during this time but didn't see the information on the site (banners, pop-outs, forum posts from employees). Other than turning off downloads (which would have caused even more issues), I'm not sure what else they could have done. Some people suggested suspending sales, which would have been a terrible idea and wouldn't have stopped your problem from impacting you.

GoG believe the issue is resolved - this is why, if you do run into any issues (after trying again), you should raise a ticket. This will help them to help you - if you haven't told them about a specific problem through support, you're putting a lot of trust in their ability to independently identify and fix something.

This is fun... in a weird sense. Sometimes i got the impression there is more wrong than proper things... i think if you know "the real world" you have no need for a horror story anymore... you will get the best one for free.

I presume you are talking about the offline installer files, not the games installed through Galaxy.

Why do you need to check each and every file separately? Isn't enough to enable the integrity check when you are installing the games? Or alternatively, I guess you could use innoextract to test the installers, if you don't want to install the games.

Not sure if the GOG-provided md5 checksums can be trusted in this case, since I don't know if they were generated for the corrupted installers (if the problem indeed is on GOG's side).

Another weird thing: I checked all Van Helsing files and it seemed OK, so i was marking it as "passed". As soon as i was about to instal the instal simply was stuck...

Checked all the drives, no failures found. Downloaded another game that was suceeding the instal from the exactly same drives.

It could be a filesystem issue as the MS filesystem is really dated and it may not be able to handle "long file paths", because the only thing that changed was the path, which got about 4 more letters.

So many stuff can simply go wrong.. yet this is only guessing, i will have to find out. I use Installers... i do not enjoy a launcher for good reason, because it simply is not compatible with all the games i own (not gonna make a story yet... ).

The checksum is the only thing i can trust on, and to some extend "a working game"... as, there are not much games that will work properly if there is corruption. The data size can be identical, it got no meaning but still useful to see "if some files are entirely missing".

Sure, the Galaxy is using checksum as well, but it should be done automatically upon download. For the installers you have to do it manually in some way.

The checksum is usually provided by the uploader (upon uploading it) which means by the dev (this is the only correct way how to execute it, because you need a "starting point"). So, lets say the server is screwing up, there might be data restored but it would be highly incompetent creating "a new redundancy file" using those restored data... this will always fail but on GoG you never know...

Oh please... do not make me worried to much. If those issues are continuing i think i may even have to apply as a "datacenter manager"... else we are probably doomed.

Ah yeah, it was a filesystem-path issue... i had to cut on letters, this is happening a lot sometimes. I mean this MS filesystem is really a thing from the past, they should make a new one... it will hurt no one but finally making stuff easyer for data management.

I had to laugh almost 15 min straight as it is simply to much to handle, this entire world full of fails. I thínk, as soon as a certain point is exceeded you will stop crying... paradox.

You can disable the 260 character file path limit through regedit.

The limit is enabled by default to maintain compatibility with legacy applications not supporting long paths. I can understand this design decision as it limits the number of people who claim that "Windows broke compatibility".

"I don't understand what's going on here" (Jet Set Radio, anyone?)

Recently i had a redundancy error on the file part 16 of Cyberpunk. After re-downloading and re-checking the file involved it was able to pass the test; however... i am really not sure if this issue was caused on my hardware or the transfer of the file (on my side)... or if it was a server issue caused by some instability at this spot.

So it really will need some big investigation... and i will re-check this game many times in a row. But if i fail to see any further "failed" redundancy check, it is pretty safe to say it has been caused by the server.

In general there is 2 ways of "failed redundancy":

1. If the file itself is corrupt (we can exclude because re-download worked)
2. If the hardware is unstable, in this case it may make a failure during the reading or transfer process.

it can be on any spot, internal or external.

On top of that, my hardware load (which is critical for having stability issues, no load means almost no risk of instability) is close to zero while checking it. The only thing with high load is the SSD drive but this one is usually very reliable and not prone to any matter of instability. The server surely can be at high load and with a small chance my modem may have to be replaced at a certain point, as the modems in usual may become unstable after many years of excessive use (in my experience).

Although... every single game so far (dozens already) has passed the check... so dunno to tell if the modem is not sufficiently stable (or any other part of my hardware).

Second check of Cyberpunk (with redownloaded file) passed again... i will do this 10 times in a row in order to ensure it is not on my side.

CPU is 49 C during the check... almost idle, the fans are not audible at this temp. The SSD however will almost be burning after so many checks, if it stays stable... i say "wow".

3. check... passed.
4. check... passed
5. check... (sorry drive, i hope you are not gonna quit) passed
6. check... passed
7. check... passed
8. check... passed
9. check... passed
10. check..passed

Will take very long because the data is huge, in total 650 GB will have to pass the check.

In total ~500 GB of files have been downloaded without detectable failures... so very hard to see the spot of failure considering Cyberpunk but if i take the recent experience of other users into account... most likely server-caused.

At 60 FPS (for the TV sync) my hardware load is usually very low anyway, the CPU is just stressed during loading a game but so far it never failed doing so. As for downloading, no demand at all. The RAM (DDR5 with internal error correction) are working at certified specs and so far never any issue (with the new CPU).

I am not able to find a failure "on my end", so i have to move on and most likely make the note that the required work on the servers is surely as hot as ever.

If you care about your drives and ultimately your data, then you shouldn't download or transfer too much data at once, but do it in stages with a few minutes rest between, so basically with periods of cool downs. That includes anything intensive like verification (MD5) checks.

Drives may be more heat tolerant these days, at least in theory, but that in reality means they should suffer less during normal use, not be an excuse to stress them to the max moving huge amounts of data around.

And as always, drives can die any time, so no assurance of anything.

GOG provide two types of MD5 values for Offline Installers.

Type 1. For each installer file. This will determine whether what was downloaded matches what is on the GOG servers.

Type 2. For each file inside an installer file. This should determine if there is any corruption of an individual file, based on the MD5 record before compiling into an Offline Installer file.

Galaxy and some third party downloaders (i.e. gogcli.exe and gogrepo.py) use Type 1.

When installing a game, Type 2 is checked. Or you can do a simple, but long check (test) with InnoExtract.

Type 1 is a much quicker check, but not as reliable as Type 2.
An offline installer file can pass Type 1 but might not pass Type 2 if it was already corrupted before downloading.

Type 1 really only checks if downloading was okay and no corruption occurred during that process. Type 1 check is usually sufficient, and preferred due to speed, unless you have a lot of spare time to do the much longer check of Type 2.

Neither check is a complete guarantee, as even with Type 2, a file might be corrupted before being added to an Offline Installer file (package).