The res protocol handler dislikes running from a multithreaded apartment.

gdi32: Now that we require a less ancient freetype, we can assume several other functions are also present.

msi: Don't attempt to patch files if the component action resolves to anything other than INSTALLSTATE_LOCAL.

Now, winealsa maintains its own buffer, which is written to ALSA on the
period cycle requested by the application. We also let ALSA start when
it has enough data and stop when it runs out, recovering from the
expected underruns. This seems to be more like how ALSA expects to be
used.