Can anyone upload it please. I dont wanna install gog galaxy again.

NO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Yes!!!!!

Can't you just verify/fix the game? I think it'll only download the missing files.

It's on your GOG Download page if you own the game.

Just open the website in your browser, and click on game in your browser
Select Classic installer, no need to ever use Galaxy.

If you don't own it don't ask for a patch here find a torrent.
I provide the patches, but only when GOG has removed them, not for what's on the site now,

Here's a pic
DOS 2 - GOG Library

What about minor April patches (74e and 74c)? It seems i can`t update to 993_LOCA and so on, without them. Could you please upload these two?

Unfortunately I missed them two, but was only awarre of the e one
Last patch I have not on GOG
patch_divinity_original_sin_2_3.0.180.158_(19075)_to_3.0.190.74_(19412).exe

Missing from my removed payches Upload
patch_divinity_original_sin_2_3.0.190.74_(19412)_to_3.0.190.74c
patch_divinity_original_sin_2_3.0.190.74c_3.0.190.74e_(20272)


On GOG Now
patch_divinity_original_sin_2_3.0.190.74e_(20272)_to_3.0.226.993_LOCA_(20799).exe
patch_divinity_original_sin_2_3.0.226.993_CN_(20821)_to_3.0.226.993_(20845).exe
patch_divinity_original_sin_2_3.0.226.993_LOCA_(20799)_to_3.0.226.993_CN_(20821).exe

If someone else uplaods the missing patches, I'll add them to the removed patches drive.

Someone correct me if I'm wrong, but I don't think they existed

They must have, or at least one as the GOG patch numbers (In Brackets) would match

patch_divinity_original_sin_2_3.0.180.158_(19075)_to_3.0.190.74_(19412).exe

Jumps to

patch_divinity_original_sin_2_3.0.190.74e_(20272)_to_3.0.226.993_LOCA_(20799).exe

With no patch linking (19412) to (20272) you can't update from one to the other.

Pater above me mentions ...74 to ...74c, and ...74c to ...74e so I assumed they knew of their existence.

If you check the logs in stuff like gogdb.org it looks like they only updated the main installers

Nothing on that site says anything of the sort
The Downloads page only lists what's currently available
Divinity: Original Sin 2 - GOG Database Beta - Downloads

As for the so called changelog, it's a total load of inaccurate rubbish
Divinity: Original Sin 2 - GOG Database Beta - Changelog

Just as one example, from the most recent batch of patches first uploaded this month.
We are told the first "added" in that Changelog is;
Added download - Patch, Patch (3.0.190.74e to 3.0.226.993 LOCA), Windows, en 2017-10-09

Six months before it even existed, the latest patch for 9th Oct 2017 was v3.0.146, not 3.0.226.

Even the Official changelog from the GOG store page cant be relied upon.
I have at least 7 patches that aren't even part of that log.

Larian may not have provided a full patch sequence, but this would be the first time.
I've seen no reliable evidence to prove that.
I have seen patches removed after only being uploaded a day or so before the removal.
So missed patches is what I'm assuming.
Until proved otherwise.

I don't get your demonstration of how GOG DB would be inaccurate.

See my point of view here (remove arobases): https@:/@/ww@w.gog.com/forum/divinity_original_sin_2/all_patches_gog_has_removed_so_you_can_update_from_the_or iginal_release/post36

In short, I believe the full installer got released as "3.0.190.74", "3.0.190.74c" then "3.0.190.74e" and now reached "3.0.226.993 CN4".

On the patches side, there was a "from 3.0.180.158_(19075)", then a "from 3.0.190.74e_(20272)" but nothing in between.

So no patch exist to reach "to 3.0.190.74c" or " to 3.0.190.74e". And the "3.0.190.74d" version never existed seemingly.

In the log, I understand that on the 2018-03-22, the GOG team released patch "3.0.180.158 (19075) to 3.0.190.74 (19412)". And that on that same day, they decided (or screwed up) that there will be no further patch from that point in the future (search the "19075 -> 19412 ⇒ None" and "None ⇒ 3.0.226.993 LOCA" patterns in this log).

Maybe you got misleaded by the log entries, that always state the newest patch name, instead of stating the patch name at the time of each entry.

The longest available path (i.e. using the oldest available patch), seem to be : "setup_divinity_-_original_sin_2_3.0.190.74e_(20272).exe" + "patch_divinity_original_sin_2_3.0.190.74e_(20272)_to_3.0.226.993_LOCA_(20799).exe" + patches from 20799

That DB looks perfectly fine.