Did it for me with Monkey Island 2. Installed just fine.
Thank you for the solution!

encountered this bug today. 1.5 years later. just wow.

I owned both SEs back in the days, when 16:10 was still a thing, my monitor had a resolution of 1920x1200.

When I bought and started the GOG version years later, I only had a FullHD monitor.
And guess what? The games would not start anymore, I had to edit the configuration file manually to fix that.

... just in case you experience something similar.

%appdata%\LucasArts\The Secret of Monkey Island Special Edition\Settings.ini
%appdata%\LucasArts\Monkey Island 2 Special Edition\Settings.ini


This config bug might also be releated to it.

I'm on Win10, and I can'y install Monkey Island 2 SE.
The Galaxy' installation process ends with "Installation failed (E2)", and there's a retry option which doesn't help...

EDIT:
The funny thing is the files are there, and I was able to manually import the game folder so it's visible in Installed Games, but I still didn't find why the installation failed like that.

make that a 3 year anniversary

Still ongoing.

This worked for me too tyvm nnsense....legend

This also worked for me, too. Cheers mate!

4 years and counting now. Just bought Monkey Island 2 SE tonight. Online installer fails at 95% with the error "Installation failed (E4) A disk access error occurred during installation". Update after cleaning and importing fails as well with the same error. Time to get on the horn...*sigh*

In my case, the installation didn't work, and neither did the 'update trick'.

However I manage to successfully install it by going in GOG website and using the "Download offline backup game installers"

The offline installer worked perfectly (some popups came up, asking to repair or uninstall some C++2008 version -> choosing repair seemed to work ok for me)

I'm running this on WIndows 11 and it took a while to get this Game to work.


What I did:
1) Download the standalone Installer from the GOG Website.
2) install it
3) When the C++ 2008 installer pops-up accept both the Install and after that the Repair if you already have the files it'll instantly complete.
4) When Launching GOG afterward the files should be there in the installed list but you got to repair the install and it'll download an extra 336Mb.


After all that the faulty install messages (and continuous re-download of the 8.8Mb stuff) where gone for me and the game could be launched from GOG Galaxy without any further problems and the game works like a charm.

Thanks, this worked for me!

None of these suggestions worked for me on Windows 11 Home. GOG Galaxy just keeps trying to update it and it keeps failing nonstop. I just had to manually install it outside of GOG Galaxy after downloading the executable from my GOG Library. Amazing this problem is now over two years old and GOG has yet to fix it. Hopefully they will see my post and this entire thread and do something to fix the problem with this game.

It seems many are having issues with GOG installs, but sometimes is not entirely on Galaxy fault.

In my case, I experienced some issues (and not with Galaxy alone) when I upgrade my rig. The new cpu supports a feature called "adaptive voltage". Turning that stuff off (aka setting voltage to static) fixed EVERY issue I had with game crashes AND game installations (Galaxy included).

I know, for many people, this might sound crazy or far fetched, but I guarantee you that in my case, "adaptive voltage" was the culprit. With that stuff turned on, almost every game made with Unreal Engine 4 were crashing to desktop.

I guess it might be not the feature itself the problem, but the unfortunate "bin lottery" that comes with buying a new CPU. If your bin is bad (mine probabily is) that feature might cause some trouble to specific processes only.

Playing along with OC parameters can make a difference also. Your PC might be stable as a rock, but for some reason, a specific CPU voltage might cause your game to crash.

Maybe, this piece of advice will be useful to somebody.

Cheers

Just when I thought I had it an "update" rebroke it.