yea first thing but it's not working properly. doesn't fully keep stretch all to way to the top or bottom
Did manage to find a widescreen mod and that works creates a 'window' but works in 4k resolutions

Shinzon, thank you so much for posting this fix over here - it works for me too :) I did some investigation on the device using pcilookup.com - although I can't find an exact match with both Vendor ID and Device ID, searching with just the Vendor ID turned up two device entires. One was from NKK Corp. - probably not relevant - but the other Vendor was Turtle Beach, and my headset is TB. Interestingly, the headset still seems to work with the device disabled - and sure enough, Myst IV launches every single time while it's disabled.

A full explanation still doesn't spring to mind - but perhaps the game is still dependent on an ancient version of OpenAL or DirectX, from a time before HID-driven audio devices existed.

Anyhow... for anyone who's curious but isn't sure how to identify these "almost anonymous" HID devices...

1. Open up Device Manager
2. Expand "Human Interface Devices"
3. Find several named "HID-compliant vendor-defined device"
4. Right-click and choose Properties
5. On the Details tab, select Hardware IDs in the dropdown
6. Note Vendor ID and Device ID (details below)
7. Visit pcilookup.com

For Vendor ID and Device ID, check the first line returned in the details. Mine looks like this:

HID\VID_10F5&PID_2154&REV_0100&MI_03&Col02

Vendor ID: 10F5 (code after VID_)
Device ID: 2154 (code after PID_)

If you see no results entering both into the PCI lookup page, try searching on just Vendor ID. This should at least return devices from a company you recognise as providing one of your own, as with Turtle Beach for me. This won't help much, aside from satisfying curiosity, and perhaps letting you know what you might lose with the device disabled.

I haven't been past the title screen just for testing - the video looks a bit rough, but we'll see how I get on with that. Thanks again Shinzon, for passing that fix over here!

Nothing to thank. Gamer helps other gamers :). It is not fix, just a workarround, i hope GOG can make a real fix.

Still having the same issue, tried all the work arounds listed in this thread.

If you have a USB headset, something to try:

1) Unplug the the USB headset (if it is wireless, unplug the dongle).
2) Disable all Playback devices in the Sound settings (at least everything that is not marked as "Not plugged in").
3) Start Myst IV.
4) Wait until you see a dialog box saying Cannot initialize Sound Driver. If you do not see it, keep following the instructions.
5) Plug in USB headset or dongle.
6) If you have the dialog box from step 4, Click Retry. Otherwise, try pressing the Enter key as it might still exist.

At this point, Myst IV should launch and you should have sound in Myst IV.

If you do try this, please come back and tell me if it works. It worked for my Corsair Void headset.

I've tried just about every fix in this thread and feel that I'm totally out of ideas, bar literally making a new admin user account and trying to run it from there. No word from GOG Support desk, either.

This is incredibly frustrating! I'm not happy that I've apparently purchased a game that doesn't even run.

I will note that one thing that seemed to have some sort of effect is installing the Ubisoft patches. I say seemed because, while that succeeds in getting the opening card to appear, it also causes me to get hit with a 'no CD' error. Which is problematic because, you know, I purchased the no-DRM version.

Get it together, GOG -_-

Isn't the GoG version already pre-patched with those?

Was able to resolve by making sure Vertical Sync is selected to ON via the NVIDIA Control Panel - Mange 3D Settings

EDIT: Only worked once. After fresh install of Windows 10 - still not working

I've also hit the Windows 10 / Myst 4 loading issue and took a look under the covers. As others have reported, this is a crash that occurs during DirectInput device enumeration. Surprisingly, I was able to reproduce this outside of Myst using the DirectX 3 SDK so this is an appcompat bug in Windows 10.

I'm working on reporting this up the chain to get it fixed; in the short term, am also working on a possible workaround.

Awesome Rafael - havn't seen you on Thurrott lately but I know your damn good at reverse engineering. Hope you solve it

On My system... and after some experimenting I have stumbled upon the source of the problem as to why the game was crashing on startup. I unplugged my Binatone headset dongle and the game ran. I have a Logitech headset as well so I plugged that dongle in and the game ran. Obviously something about the Binatone headset the game doesn't like. It might be possible the game may not like other peripheral devices. Might be a good idea to list it in the known source of problems in their readme text file

Yep, any HID device that isn't a keyboard or mouse will cause this. I've created a workaround, just polishing it up and will throw it up on GitHub/give you guys a copy.

I've also filed a bug in Feedback Hub against Windows 10
https://aka.ms/AA3931c

And as promised.

Code: Library: Plop that baby in the \bin folder and should resolve that issue, from 1.0 to 1.3 with/without NoCD.

(Had to use forum quotes to workaround silly link/rep policy.)

Wow thanks sooooo much - works a treat