I just made new Windows Terminal profiles for MSYS2, if anybody is interested, because by default it runs in MinTTY. Code: { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=CLANG64 CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0da3-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msysclang64.ico", "name": "MSYS2 clang64 (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "CLANG64", "CHERE_INVOKING": "1" } }, { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=CLANGARM64 CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0da2-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msysclangarm64.ico", "name": "MSYS2 clangarm64 (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "CLANGARM64", "CHERE_INVOKING": "1" } }, { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=MINGW64 CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0da1-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msysmingw64.ico", "name": "MSYS2 mingw64 (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "MINGW64", "CHERE_INVOKING": "1" } }, { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=MINGW32 CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0db0-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msysmingw32.ico", "name": "MSYS2 mingw32 (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "MINGW32", "CHERE_INVOKING": "1" } }, { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=UCRT64 CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0db1-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msysucrt64.ico", "name": "MSYS2 ucrtm64 (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "UCRT64", "CHERE_INVOKING": "1" } }, { "commandline": "\"C:/Program Files/msys/usr/bin/env.exe\" MSYSTEM=MSYS CHERE_INVOKING=1 \"C:/Program Files/msys/usr/bin/bash.exe\" -li", "guid": "{0caa0db2-35be-5f56-a8ff-afceeeaa6101}", "hidden": false, "icon": "%ProgramFiles%\\Icons\\System\\msys.ico", "name": "MSYS2 msys (x64)", "startingDirectory": "%ProgramFiles%\\msys\\home\\Vertex\\", "env": { "MSYSTEM": "MSYS", "CHERE_INVOKING": "1" } },
It seems, that the next VLC v3-0-22-0 will finally have arm64 version as final. The currect naming of nightly builds says it is RC1: vlc-3.0.22-rc1-winarm64-104bc872.exe
VS Installer 2017-2026 (which manages VS installations and updates) is DotNET v4-x AnyCPU, so you can run it as arm64: "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe" Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\setup.exe] "PreferredMachine"=dword:0000aa64 Although due the name it looks stupid, it won't actually cause any problems for other non-AnyCPU setup.exe-s.
Those installers above are autoupdated to the latest version of the installer, since those links are aliases.
It uses OneCore.lib thing. I am of course unable to replace it with standard kernel32, user32, gdi32, shell32, ole32 etc. calls, so it probably runs only in W10 b15035 arm32 and it doesn't run in W8-x arm32 RT. So much for Ben the coder.