[edit] This issue has been solved with a recent patch.

What it says on the tin- I own both DLCs, however when I try to enable More Slugcats Expansion in the Remix menu it tells me I need to buy the DLC and opens the Steam page for it.

I've tried installing it via Galaxy, via Heroic Games Launcher (both assure me both DLCs are installed) and by manually downloading and installing the installers&patchers. The result is always the same, I can enable The Watcher, but More Slugcats, Expedition and Jolly Co-Op remain locked and asking for DLC.

+ 1, having the same problem.

Pretty sure this same issue happened before on the GOG version of Downpour and they eventually fixed it in a patch.
Certainly frustrating.

I also have this problem. Could probably get Downpour back by reverting to previous version in galaxy's installation management. But then of course Watcher isn't going to work. It's a bit of a mess.

Can confirm the exact same thing happened two years ago, it's kinda impressive how they messed up like this twice, iirc it took them a few days to fix this through a patch last time. Fortunately, I don't think the Watcher is connected to any of the Downpour mods (I certainly hope so, I've been playing without them). Worst case scenario, I checked and you can in fact get them back by reverting to a previous version, so at least there's that

SAME HERE! After buying the latest 2025 DLC .

Same problem. I own the Downpour DLC and have been playing on it for months. Once I downloaded the Watcher DLC, the Downpour DLC became inaccessible and I get the message that I must purchase the Downpour DLC in order to access that content.

Thanks for confirming that! Can you describe exactly what you need to do to accomplish running an earlier version where Downpour works? Like which offline installers to use.

I'm trying to deal with the same issue as everyone here for my kids and it's very frustrating. I hope GOG is aware and fixing it quickly.

They literally just updated the Downpour installer from 6MB to 1.5GB, and it works now (fingers crossed)

Can confirm, the new patch has fixed this issue.