Have you already tried installing the RAD Video Tools (direct download link) as well as this work around: http://www.gog.com/forum/messiah/to_everyone_with_frozen_cutscenes

Many thanks :)

Edit: But sad to say, no joy. Most videos still end with a rather spectacular crash.

Try opening some video in the background. Just fire up media player, launch a video (the longer the better), and mute the media player sounds.

As strange as it sounds, it worked for me and stopped the cutscenes freezing.

I recently restarted playing TLJ too, because of Chapters release, and as I last played it 10+ years ago, and I have exactly the same issue : after most, if not all, cinematic it crash.

I tried all the "proposed" solutions you find online :

Played a Youtube video (or any other video ) in the background, installed the RAD tools, tried changing the Bink DLLs with different other versions, changed the CPU affinity, use CPU Stress to keep the CPU usage above 50%, etc... but nothing helped.

The only "solution" that works most of the time for me was to disable "high quality" video in the settings, it work for the intro and most of the following cinematic. It still crash from time to time and when that happen usually switching back to HQ video for the cinematic in question does the trick. (at least until now, around the middle of the game)

Still I really hope that they will release the "improved" iOS version on PC or at least release a new PC patch correcting the cinematic issues.

I have the same issues, all the FMVs crash at the end, before switching back to the gameplay. I'm using win7 64bit. Tried all fixes, nothing works.

they're black when playing on Linux too, using the Wine API/emulator. Doesn't work on Win7 in vmware either.

I've been watching "PC Longplay The longest Journey" on youtube, just to see the story.

btw, there's a specific build of wine that runs this game under linux, cut-scenes work, but the mouse interface is a bit awkward.

Cheers- I gave up for a while, but really want to play this game. Maybe I'll end up just watching the longplay on youtube too...pity.

The only thing which works (on occasion), is to use low quality video, like Gersen said.

Hoping for a fix. Apparently the iOS-version selling really well.

I have Win 7 now but still get the same cut-scene crashes I got in 2000, although it always operates the same way: after playing some, I can watch one cut-scene without trouble, but the next one will make the game crash to desktop when it transitions back to game. The "solution" is easy though; I can load the previous savegame and hit ESC when the video starts (I have now seen it anyways, since it always crashes right after it for me) - that will skip the scene and transition back to the game without hitch. It just means I have to save a lot, which I do anyway. ;)

I have pretty much the same problem. After the first video it CTD. Win 7 64 bit. So it there any response from GOG? Or should contact support?

EDIT: Ok, the high quality video in the settings helped. Thx.

I have windows 7 64 bit and I was able to get it to stop crashing after cutscenes.

I did two things:

First, in my GPU's individual program's settings (where you set special graphics options for specific settings) which I found in my GPU's control center program (I have an Nvidia 650m, so it was the NVIDIA control panel. I don't remember exactly what I changed, but I turned everything even possibly related to anti-aliasing to OFF. (I did some searching on the internet and some reported that anti-aliasing messed it up. I didn't have anti-aliasing on, but my graphics card was doing some things related to antialiasing.

I was using a two monitor setup (the game was playing on only 1), so I also turned off the monitor I wasn't using and went for a single monitor setup. However, since it started working I went back to a multiple monitor setup and the game still isn't having any issues, so I think it was the antialiasing that was doing it.

Can't guarantee anything, but this worked for me.

This worked to fix the problem for me on a Windows 8.1 machine ...

If you are running the game on a PC with multiple cores, change the "target" in the launch shortcut to the following.

C:\Windows\System32\cmd.exe /C start /affinity 3 game.exe

(Obviously you need to make sure the paths are correct for your environment.)

This will tell the game to utilize only cores zero and one. Apparently, the game has issues with there being too many cores on modern machines. I tried using only one core and that was not sufficient. Two seems to do the trick.