https://bugs.winehq.org/show_bug.cgi?id=48337
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- (In reply to Artem S. Tashkinov from comment #5)
(In reply to Alexandre Julliard from comment #4)
This doesn't make sense, there's no native/builtin distinction in Windows. And there's nothing special about .local, it's an alternative to using a manifest or putting dlls in the app directory, having it behave differently would be weird.
I felt like Wine DLL overrides and Windows .local file + application directory DLLs work the same way but maybe I don't understand fully understand how native/builtin is handled by Wine. I've always assumed it was just a way of finding and loading libraries, i.e. native/builtin means try to find and use a DLL in the application directory and if it's not found then use the one which comes with Wine.
No, that's not how it works. Builtins are always used by default, no matter what files are found on disk (or even if the files don't exist at all). This is necessary because some apps come with broken versions of system dlls, and others install their dlls in the system directory.