Keep getting error message with the latest version of mkvtoolnix - The procedure entry point SetThreadDescription could not be located in the dynamic link library
Already installed the latest version of Microsoft Visual C++ Redistributable, but it does not resolve the issue.
Welcome!
Yeah, Windows Server 2016 is problematic & not really supported anymore. Sorry.
Honestly, I don’t quite understand why MKVToolNix, as a video track processing tool, imposes so many restrictions on the operating system, to the point that even the command line can’t run. In theory, these functions only involve reading video and audio streams from files and re-muxing them, which shouldn’t involve much system-level stuff, right?
MKVToolNix uses the Qt library not only for the UI, but for various other things as well, including regular expressions. Qt has certain limitations. Personally I have further limitations wrt. how much time & effort I’m willing to spend on various OS. And there’s the security aspect of using current, supported, well-patched libraries for products I offer users. Those things combined mean that I will not bend over backwards for OS support.
Thank you for your response and your efforts. What I mean is, as a layperson, I can’t understand why MKVToolNix, as a video muxing tool, has such a deep dependency on the operating system, even if this dependency stems from Qt6. In fact, Qt6 is helping Microsoft implement planned obsolescence through TPM 2.0, phasing out older hardware. If this is the case, is it possible to use a framework other than Qt6 to develop this tool, such as an older version of .NET or Qt5? Could you briefly explain, for MKVToolNix specifically, what practical features Qt6 offers over Qt5, aside from facilitating planned obsolescence?
I am not interested in arguing with or explaining myself to someone claiming an Open Source project is in cahoots with Microsoft in order to screw over users & make more money.
The point is not to discuss aiding Microsoft in profiteering, but rather, as an open-source software, whether it’s possible to consider older systems more, especially with TPM 2.0 as the boundary, and avoid mandating the latest Microsoft system unless absolutely necessary. If feasible, try to ensure that older operating systems can still run the software.
I’m not interested in that wrt. Windows. You can use modern Linux distributions on older hardware, and MKVToolNix is fully available on Linux. You have options. I’m just not interested in providing support for the specific one you want me to provide for.
Ubuntu 22.04 is not an extremely outdated system, yet it is no longer compatible with the latest version of MKVToolNix and can only run version 88, which is older than the version available for Windows (Windows Server 2016 supports up to version 89). If there is a mandatory requirement to use Ubuntu 24.04 (which also requires TPM 2.0 hardware), will there be any significant improvements compared to Ubuntu 22.04? Is it possible to downgrade the Qt version in order to alleviate the forced upgrade requirement for the operating system?
I also provide an AppImage you can use on older versions.
No. Neither is switching to other libraries. Just stop with that line of thinking.
Here’s the translation:
I tried running the AppImage on Ubuntu 22.04, but I received the error message: error while loading shared libraries: libboost_filesystem.so.1.85.0: cannot open shared object file: No such file or directory.
That’s not how you use an AppImage. You don’t extract & install it. You make it executable (chmod +x MKVToolNix*.AppImage) & then run that file. The magic of an AppImage file is that it bundles all but the most basic system libraries, which include Boost.
