View Full Version : MKVToolnix Windows 7 "The final Countdown"


jpsdr
29th April 2022, 12:30
Hi.

I'm creating this thread to avoid poluting the Mosu thread with more posts.

We can talk here about which versions are working.

Also we know that a not working version at one time doesn't mean it's final, it just happenend.

Nevertheless, the reality is that the true final deadline is comming, and it's very near !

But, in the meantime...

The last i've tested working is 61.

New non officials QT5 builds
You can check here (https://github.com/jpsdr/MKVToolnix-QT5-Windows-7/releases/) for builds, not sure how often there will be.

Liisachan
29th April 2022, 19:52
Yeah, let's talk freely here without annoying Mosu :)

First off, I was surprised to know there are so many die-hard Win7 users, as I was thinking I was one of only few weirdos who're still using Win7.
Why are you guys avoiding Win10? Privacy concerns, or some kind of compatibility problems? If it's privacy, do you think Linux (migrating to it or using it side by side) is a realistically good option?

Also, don't just use the "lastest" MKVToolnix blindly... Generally, too new versions tend to be less reliable than tried and tested older versions, especially, experimental "continuous" builds. If you do font attachments, I'd suggest Version 57 or before to avoid the font-mime-type mess.

While MKVToolnix is a respectable project, it's not a secret that its GUI is not known for the most intuitive UI. Matroska is sometimes too powerful, too complicated, thus tools tend to become complicated & confusing.
Given that the rigorous rounding is important for Matroska (which doesn't support ntsc 24000/1001 fps explicitly),
https://matroska.org/technical/notes.html#timestampscale-rounding
the current rounding errors of mkvmerge is less than ideal, although there are workarounds. The fundamental problem here may be that MKVToolnix is practically a one-person project, not developed by a team.

But it's FLOSS, so if someone starts alt. builds (like MPC-HC & MPC-BE), things might become convenient for everyone, more flexible, and perhaps less stressful for Mosu too.

That being said, the problem here is not only about MKVToolnix. Many tools have stopped supporting Win7 already (esp. 32-bit), and more and more tools will stop supporting Win7 sooner or later... So I think Win7 users should start looking for a different option too just in case, which may mean Linux. "MKVToolnix for Win7" would be useful for the time being, though.

For many practical purposes, older versions of mkvmerge are perfectly fine. Essentially they write bit-identical MKV files as written by the newest version. So don't worry too much :)

EDIT
additional link
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix-do-they-exist

Dogway
29th April 2022, 22:05
It's a Doom9 thing (the amount of Win7 users), we are a bunch of die hard fans.
Personally I like the OS to be fully under my control, and be sleek and functional.
Things like Cortana, Windows Defender, Candy Crush, Telemetry, "Apps", unavoidable updates... are not things I want on a working environment.

Another bad thing is the lack of DWM, I read you can't disable it so you can't go into FSE anymore.
More:
You have to disable "Control Flow Guard" for extra performance (if you run NVidia Cards).
You also need to "Empty Standby Memory" regularly while gaming (maybe with a task scheduler).
I also read that there are issues with the winsxs folder, maybe due to the amount of updates but it grows very large soon.
Finally the UI is a mess, not only metro is a disaster in itself but it's half metro half classic UI mixed.

I was happy to change to Win11 as it fixes some of the Win10 problems, but then they came with the hardware requirements.

Linux... nvidia driver incompatibilities and no or very bad color management system. Enough to not look any further.

I will install Win10 regardless in a few months, at least until I buy a new PC probably around 2025.

I'm curious to know aside of a GUI what MKVToolnix has better MKV features/support than ffmpeg. To know if it's worth changing, or if ffmpeg has important issues to care about.

filler56789
30th April 2022, 00:49
Version 67.0.0.63 is O.K.

filler56789
4th May 2022, 22:43
Last_Good one = 67.0.0.76.

von Suppé
5th May 2022, 16:25
Last_Good one = 67.0.0.76.
:thanks:

Liisachan
13th May 2022, 10:17
It's a Doom9 thing (the amount of Win7 users), we are a bunch of die hard fans.
Personally I like the OS to be fully under my control, and be sleek and functional.
Yeah, you want to own your OS. You don't want your OS to own you. Forced updates would be a real downer. While you're talking about freedom, convenience, practicality, I'd use "privacy" as the keyword, but I guess we're basically saying the same thing here. I'm so ready to migrate to Linux, except I'm kind of "trapped" - some tools that run on Windows are important in my current tool chain, even though I don't need Windows itself. Maybe I could use Win10 locally so that there are no privacy concerns?

I'm curious to know aside of a GUI what MKVToolnix has better MKV features/support than ffmpeg. To know if it's worth changing, or if ffmpeg has important issues to care about.
I'm not 100% sure, but in some cases, I think ffmpeg may delay video frame time stamps to offset the audio delay, which could mess up subtitle timing (esp. karaoke).
[Edit: I say "mess up" as a typesetter, but practically, normal people can't see the difference, even if karaoke color change for one letter is off by 41 ms.]

On the other hand, some MKV writer (ffmpeg too?) can write ebml CRCs, which MKVToolnix can't. Most MKV writers (e.g. Haali's) except MKVToolnix do not have weird rounding errors, where timestamps are not rounded correctly. MKVToolnix also does automatic update checking by default, without asking, without any privacy policy (but almost every tool does that today). So, frankly, it has a few, slightly unsatisfactory elements for me. The GUI i/f is not very intuitive, tbh.

That said, MKVToolnix has a ton of nice things. For example, the --deterministic option can be very handy for debugging in some situations. Info Tool - Element Viewer (hex dump) is extremely convenient when you're studying the inside of an MKV file. And its language code (LanguageIETF) support is nearly perfect, truly admirable. In reality, probably only a few, if any, users need/use complicated language codes, though.

For something basic, like just muxing x264 and aac, perhaps other muxers are as good as mkvmerge is. But all in all, I believe MKVToolnix is the most powerful tool to handle MKV.

filler56789
14th May 2022, 02:20
67.0.0.87.

filler56789
23rd May 2022, 03:10
Looks like latest version works under Win7 again?

Yes :)

mkvtoolnix-64-bit-68.0.0-revision-001-g6a55c58d2

ssjkakaroto
23rd May 2022, 13:24
First off, I was surprised to know there are so many die-hard Win7 users, as I was thinking I was one of only few weirdos who're still using Win7.
Why are you guys avoiding Win10? Privacy concerns, or some kind of compatibility problems? If it's privacy, do you think Linux (migrating to it or using it side by side) is a realistically good option?
The mentality of change for the sake of change is plaguing the whole IT world. When I bought my PC Windows 7 was fully supported, so it works perfectly with my hardware.
Security is a non-issue if you know how to get ESU updates (https://docs.microsoft.com/en-us/troubleshoot/windows-client/windows-7-eos-faq/windows-7-extended-security-updates-faq).
Besides some programs that are forcing Windows 10 down our throats, I see no reason to upgrade from a perfectly stable system.

filler56789
9th July 2022, 21:17
mkvmerge v68.0.0.36.

manolito
10th July 2022, 01:00
Thanks for the Heads-Up...

Mosu just released Version 69.0.0 of MKVToolMix, and this version no longer works under Win7. So the version you posted seems to be the final Win7 compatible version. I did a quick test (32-bit only), and it seems to work fine.

So I updated my ToolNix Repository for ancient versions (for WinXP and Win7, 32-bit only), the link is here:
https://forum.doom9.org/showpost.php?p=1967747&postcount=1585


Cheers
manolito

hubblec4
10th July 2022, 13:13
@filler56789

Do you know if this fix is included in the last working version?
mkvmerge: HEVC ES parser: the parser will now parse at least the first full access unit before reporting that it has found all the required headers. Otherwise parsing might stop in the middle of the access unit due to the source reader not providing more data in the first call, leading to the parser not finding the "unspec62" and "unspec63" NALUs required for Dolby Vision. Fixes #3363 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3363).

filler56789
10th July 2022, 13:40
@filler56789

Do you know if this fix is included in the last working version?

I cannot check that because 1) I don't split MKV files and 2) I have never played /created /used HEVC streams containing Dolby-Vision, but my answer is:

VERY-UNLIKELY, because...

Moritz Bunkus @mbunkus added: fixed-in-version 69.0.0 — 1 day ago

source: https://gitlab.com/mbunkus/mkvtoolnix/-/issues/3363

lvqcl
10th July 2022, 15:18
Mosu just released Version 69.0.0 of MKVToolMix, and this version no longer works under Win7.

It seems that it won't work on Win8/8.1 too.

Video Dude
12th July 2022, 18:14
@filler56789
Do you know if this fix is included in the last working version?

The last working Win7 version is mkvtoolnix-64-bit-68.0.0-revision-036-g37903f25c

Look at the g37903f25c and find the corresponding commit on gitlab, which is 37903f25

https://gitlab.com/mbunkus/mkvtoolnix/-/commit/37903f25cf7ea2d0ddd381d8506fc0c2a30f5d2f


So yes, it appears that fix is included. In fact, it was the very last commit for Win7.

hubblec4
12th July 2022, 18:33
Thanks Video Dude for this info.

filler56789
13th July 2022, 03:37
The last working Win7 version is mkvtoolnix-64-bit-68.0.0-revision-036-g37903f25c

Look at the g37903f25c and find the corresponding commit on gitlab, which is 37903f25

https://gitlab.com/mbunkus/mkvtoolnix/-/commit/37903f25cf7ea2d0ddd381d8506fc0c2a30f5d2f


So yes, it appears that fix is included. In fact, it was the very last commit for Win7.

Thanks for correcting me. *THUMBS UP*

Too bad no one can trust Mosu anymore. :(

:sly:

filler56789
24th July 2022, 21:56
SOURCE: https://www.videohelp.com/software/MKVToolNix

Please, can you share those files ?

If you have the following 69.0.007 versions bearing the below SHA-1, they will work with Windows 7/8 and respective server version:
B5D5E22968F947558BFB100EF06D37A1FB3BC7C4 mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6-setup.exe
5F8BB12A7C9FA214E4B63BCFC4EF020E27186A4F mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6.7z
254911C993E8685AE514A8B7FD789C200EA6E3C4 mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6-setup.exe
86B4EEDFA42A60D74FECBE76FA55BF44A53D400A mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6.7z

jpsdr
25th July 2022, 17:24
Thanks for the tips.

jpsdr
26th July 2022, 19:23
Tested mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6-setup.exe under Windows 7 x86, not working for me.

hubblec4
27th July 2022, 11:00
for me also not.

filler56789
27th July 2022, 18:21
FWIW, and again:

from the #usercomments section for MKVtoolnix @ Videohelp dot com:

If you have the following 69.0.007 versions bearing the below SHA-1, they will work with Windows 7/8 and respective server version:

B5D5E22968F947558BFB100EF06D37A1FB3BC7C4 mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6-setup.exe
5F8BB12A7C9FA214E4B63BCFC4EF020E27186A4F mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6.7z
254911C993E8685AE514A8B7FD789C200EA6E3C4 mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6-setup.exe
86B4EEDFA42A60D74FECBE76FA55BF44A53D400A mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6.7z

BUT the greater surprise is this one :scared:

There might be one more option. There seems to be modified QT6 version for Win7 here:
https://forum.qt.io/topic/133002/qt-creator-6-0-1-and-qt-6-2-2-running-on-windows-7
I've been already able to run another QT6 based software using that (Calibre 6.1 - https://calibre-ebook.com/download).
There you need to use as well VxKex to run it - https://github.com/vxiiduu/VxKex
But MKVToolnix seems to have QT embedded in main exe, so it is not possible just easily replace those binary files like for Calibre.

jpsdr
29th July 2022, 17:10
Intersesting. Maybe someone who know how to build MKVToolnix can test make a build using this QT version instead of standard.

filler56789
29th July 2022, 19:13
Intersesting. Maybe someone who know how to build MKVToolnix can test make a build using this QT version instead of standard.

For the users of Windows 7 and 8.1, the ``ideal´´ solution would be

1) revert the change which made the CLI-executables depend on Qt
(I.O.W., make them use the file magic.mgc again)

+

2) replace the Qt-based GUI with one written in Java, or in a dot-net language, or in C++.

filler56789
30th July 2022, 05:13
OOOPS, now finally there exists a non-official build of MKVtoolnix for Windows 7 and 8.1 :eek: :scared:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix-do-they-exist#post2663774

jpsdr
31st July 2022, 11:04
According this thread, the minimal requirement build for mkvtoolnix is QT 5.9.0, so, for now, you "just" ;) have to build mkvtoolnix with this QT version, no need for tweaked QT version, just normal 5.9.0.
I, out of curiosity take a look of how to build mkvtoolnix... argh... it seems even more painfull than building x264...

Edit
Maybe finaly it's not so painfull, but still failling building... :(

filler56789
31st July 2022, 14:42
I, out of curiosity take a look of how to build mkvtoolnix... argh... it seems even more painfull than building x264...

INFINITELY more annoying than building x264, granted.
Principally because of the bloated Qt slowware.
When I managed to compile tsMuxeR, it was easy to get rid of the GUI part, which is the one that requires Qt. But MKVtoolnix is much more complex than tsMuxeR :–/

manolito
31st July 2022, 16:26
Now there is a 32-bit version which works nicely under Win7 . Have a look here:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix-do-they-exist#post2663838

Cheers
manolito

Video Dude
31st July 2022, 19:59
If we could fork MKVToolNix to GitHub and then create an Actions script to automatically compile it.

I found this about Qt5:

https://github.com/marketplace/actions/install-qt


There should also be ways to include mxe/rake in the Actions script.

Future updates could be cherry picked to commit. Most non-gui commits would not break Win7 support.

jpsdr
5th August 2022, 09:14
Building MKVToolnix with QT5 under Linux

While the minimum requirement described in the MKVToolnix home page stays QT 5.9.0, it will probably be able to build a Windows 7 version.
For now, i've not been able to build under Windows with MSYS2, the mxe package may just not be compatible with... :(
But one thing is sure: You can't build from a 32 bits Windows with a 32 bits version of MSYS2.

I'll describe what i've done, so some the paramaters/values i've used are specific to my configuration, adapt if you change things.

I've created an MKVToolnix directory in my $HOME directory.
Then, clone GIT the followings:

git clone https://gitlab.com/mbunkus/mxe $HOME/MKVToolnix/mxe
git clone https://gitlab.com/mbunkus/mkvtoolnix.git $HOME/MKVToolnix/mkvtoolnix


Now, edit the setup_cross_compilation_env.sh file in the mkvtoolnix/packaging/windows directory.
Change eventualy the ARCHITECTURE if you want to build for 32 or 64 bits.
For my setup, i've changed:
INSTALL_DIR=${INSTALL_DIR:-$HOME/MKVToolnix/mxe}

Now change the following line:
MKVTOOLNIX_DEPENDENCIES+=qt6 qt6-qtmultimedia
with:
MKVTOOLNIX_DEPENDENCIES+=qt5 qtmultimedia

Now... In the mxe/docs directory, open the index.html file in your brower, and check the necessary installed tools according your Linux version.

I was under Ubuntu 20.04, i'll now switch to install instructions specific to it.
I had to install the following:

apt-get install \
autoconf \
automake \
autopoint \
bash \
bison \
bzip2 \
flex \
g++ \
g++-multilib \
gettext \
git \
gperf \
intltool \
libc6-dev-i386 \
libgdk-pixbuf2.0-dev \
libltdl-dev \
libssl-dev \
libtool-bin \
libxml-parser-perl \
lzip \
make \
openssl \
p7zip-full \
patch \
perl \
python3 \
python3-mako \
ruby \
sed \
unzip \
wget \
xz-utils

That was for mxe. I've struggle a little to figure out what was missing to finalise.
I may have installed too much things, so, the following is my guess of what may just be necessary:
apt-get install python-is-python3 libogg-dev libvorbis-dev docbook-xsl xsltproc
You can try with just this. If it fails, add the following:
apt-get install vorbis-tools qt5-default build-essential qtcreator
On my system, both lines are installed, but as i said, i may have installed things not necessary.

Now, from within the mkvtoolnix directory, run the script:
./packaging/windows/setup_cross_compilation_env.sh
The building library part will take a LOOOT of time, without any message log displayed, so, don't panic if script seems "frozen", it's not ! But, once it's done, when you re-run the script, it will not take a lot of time.

Now... If everything went fine, it will say it and display a message with also 3 commands to execute, with rake at the last.
Copy/paste (and so execute) the 3 commands in your console.
The last, rake, will build mkvtoolnix.
You have to search within the src directory (and sub-directories) to find all the .exe.
I've been able to build a 32 bits version of 69.0.0.39, tested Ok (at leat the GUI starts) on a Windows 7 x86.

Edit
If you want to build both 32 bits and 64 bits versions, once a build is finished, you have to run "rake clean", and after changing ARCHITECTURE in setup_cross_compilation_env.sh, re-run it, don't add the PATH (it's allready done if you're still in the same console), just "hash -r" and "rake".

And then, after, you have to strip the files.

Edit 2
Collect them together in a location for stripping them all at once.
32-bit executables require the 32-bit strip.exe, 64-bit executables require the 64-bit strip.exe.

32-bit build:
Code:

{mxe}/usr/bin/i686-w64-mingw32.static-strip *.exe


64-bit build:
Code:

{mxe}/usr/bin/x86_64-w64-mingw32.static-strip *.exe

jpsdr
5th August 2022, 13:23
Build under Windows with MSYS2 is not looking good...
After solving some issues, i've been able to begin the toolchain build, but after a very long time (at least 1h if not 2h), it failed with:

configure: error: Oops, mp_limb_t doesn't seem to work

After a little search, it seems to be a MSYS2 issue, for now there is unfortunately a big chance this being a fatal blow...:(

filler56789
5th August 2022, 13:44
I have not read everything yet, BUT maybe there exists a workaround :–/

.............
The configure step fails with "error: Oops, mp_limb_t doesn't seem to work" apparently because it calls configure using an absolute path, not relative.

https://githubmemory.com/repo/wbhart/mpir/issues/189

jpsdr
5th August 2022, 14:31
Unfortunately, this is advanced Makefile/script, i'm totaly lost and have no idea of what to do (if it's even possible to do something).

jpsdr
6th August 2022, 08:15
Anyway, i have 69.0.0.39 Windows 7 working (at least, GUI start, didn't test further yet) version build under Linux, but i don't know where to put it. Any suggestion ? Create a Github ?

hubblec4
6th August 2022, 13:01
GitLab

filler56789
6th August 2022, 13:50
BOTH GitHub and GitLab. :)
Just to be on the safe side. :)
Hopefully someone will change the source-code and find a way to get rid of Qt :devil: entirely 😇.

filler56789
6th August 2022, 13:52
Anyway, i have 69.0.0.39 Windows 7 working (at least, GUI start, didn't test further yet) version build under Linux, but i don't know where to put it. Any suggestion ? Create a Github ?

You might have already shared the archive in that Videohelp thread that I opened some weeks ago.

jpsdr
7th August 2022, 10:39
Hopefully someone will change the source-code and find a way to get rid of Qt :devil: entirely ��.

This is, i think a LOOOT harder than just try to build it with a QT5 version, while the minimum is still QT5.
I'll think later eventualy for at least a github.

jpsdr
10th August 2022, 18:27
Check first post, and forget GitLab, i stopped trying to understand how it works before i wanted to kill someone... :angry:

hubblec4
10th August 2022, 22:08
Thank you. It works.

filler56789
10th August 2022, 23:19
Check first post, and forget GitLab, i stopped trying to understand how it works before i wanted to kill someone... :angry:

Many :thanks: for the alternative build. :goodpost:

=> mkvmerge
mkvmerge v69.0.0.39 ('Day And Age') 64-bit
Error: no destination file name was given.

mkvmerge -o out [global options] [options1] <file1> [@option-file.json] …

suggestion: please give better names to the releases...
we already have a ton of «vc_redist*.exes» :D in the world. :)

jpsdr
11th August 2022, 10:40
... I don't understand what you mean.
I just build, Mosu chooses the name of the releases.

filler56789
11th August 2022, 10:58
... I don't understand what you mean.
I just build, Mosu chooses the name of the releases.

I meant the filenames of the archives...
"MKVtoolnix.7z" is very UN-informative,
different from "mkvtoolnix-69.0.0-revision-039-gcea3d558a.7z",
for example.

jpsdr
11th August 2022, 20:43
Ah... Ok... I'll try to remember for the next time, and don't stop just after zip my directory.

manolito
13th August 2022, 19:00
Thanks jpsdr for your build... :D

For Doom9 users who do not regularly check VideoHelp I post the link to your build here:
https://github.com/jpsdr/MKVToolnix-QT5-Windows-7/releases/

I just tested it (32-bit only) under Win7, and it works flawlessly. Highly recommended :)

//EDIT//
I also updated the link to my legacy MKVToolMix versions here
https://forum.doom9.org/showthread.php?p=1967747#post1967747
to include this latest Win7-32bit version. Enjoy...


Cheers
manolito

jpsdr
15th August 2022, 09:34
Will not have access to a Linux PC for several weeks, so, unless someone else make a build using the method i've described, no new build for a while.
Also, MSYS2 build is in progress, but for now, only be able to get "dynamic" builds ( the .exe ask for a lot of DLLs :( ), not success on static builds yet.

filler56789
15th August 2022, 16:11
Thanks a lot for your hard work, jpsdr.

I myself MIGHT (try to) compile MKVtoolnix and share more old-Windows-compatible builds, but first I would have to ``clean´´ my HDDs and this would take some more weeks or months :–|

filler56789
15th August 2022, 21:40
Version 70 has been released. :cool:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix-do-they-exist?p=2665052&viewfull=1#post2665052

filler56789
9th October 2022, 05:03
Version 71 built by user autodidact :thanks: @ VideoHelp-dot-com.

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix?p=2669522#post2669522

WSC4
15th October 2022, 02:33
Hi manolito again. Continuity of of this post here by you https://forum.doom9.org/showthread.php?p=1976239#post1976239

Definitely no reason to become grumpy. Thank your lucky stars you did not go to the Promised Land as they say. You're still here and back on your XP machine and typing away. :) I guess your recovery and rehabilitation by your health care workers will go on for a while?

Re: the older archive with the last XP compatible version of MKVToolNix.

First of all, I need to tell you I am running Windows XP 64-bit. I downloaded your file and read through your instructions and double checked to make sure I had it right. Running mmg.exe produces this:

https://members.optusnet.com.au/wsc2/Doom9/Capture_1.gif

https://members.optusnet.com.au/wsc2/Doom9/Capture_2.gif

Because it is XP 64-bit, I wonder if any of these files in the Sources directory are causing the error.

https://members.optusnet.com.au/wsc2/Doom9/Capture_3.gif

SYSTRAY.OCX This could be the cause? Is this for 32 bit XP only? To see if the Windows directories have a copy, I searched but it is not listed. In the first error, COMDLG32.OCX is also not found in the Windows directories.

Any help on this please?

manolito
15th October 2022, 09:49
First of all, I need to tell you I am running Windows XP 64-bit.

This explains all your issues. Only the 32-bit version of MKVToolNix is supported by my tool. Of course it can be run under a 64-bit Windows, but MKVToolNix needs to be 32-bit.

What you did resulted in a mix of 64-bit and 32-bit Files in your ToolNix folder, and this cannot work. It may be possible to tweak my plugin to work with a 64-bit version of MKVToolNix, but I cannot help you with this, because my ancient WinXP computer has a CPU without the 64-bit extension.

But I do not see why you insist on using the 64-bit version of ToolNix under WinXP. I do not believe that this will offer any advantage over the 32-bit version under WinXP. If you consider using ToolNix 32-bit under WinXP 64-bit then the whole content of the WinXP folder is in my archive (the no-install version, just copy the files into the desired folder).


Cheers
manolito

WSC4
16th October 2022, 06:45
I am using your 32-bit version of MKVToolNix.

I have tracked it down to the _SmartDlg.exe file. At first it complained of the comdlg32.ocx file missing or not registered. I downloaded it and did the regsvr32 to register it. Running _SmartDlg.exe now complains Systray.ocx is not registered. I used regsvr32 and it failed to register, so I downloaded a later version of Systray.ocx and that registered OK.

Unfortunately, it still says Systray.ocx or one of its dependencies not correctly registered. I think there are .dll files missing. I did a search for SmartDlg.exe file on the Internet and found nothing about it or where it came from.

I do not use MKVToolNIx that often now, so I can put up with mkvmerge 29 and GUI 10 error box.

manolito
16th October 2022, 09:12
Yeah, my patch contains a lot of stuff which is purely cosmetic and not really needed for the core functions. I see two ways to tackle this:

1. Keep my patch (it uses a ToolNix version from 12.2018). The only difference is that you start the software with "mkvtoolnix-gui.exe" instead of "MMG.exe". This will remove all the bells and whistles, you also need to click away an error message, but it should basically work.

2. The other option is to use the latest Toolnix version which still works withoud any modification under WinXP. This is Version 10.0 from 03.2017, and you can find it here:
https://mkvtoolnix.download/windows/releases/10.0.0/

This version should work out of the box under WinXP, and you have the choice if you prefer the 32-bit or the 64-bit version.


Good luck
manolito

WSC4
17th October 2022, 02:39
Thanks a lot for your information here.

I have decided to go with your number 1 choice and patch and use those file versions 29. Removing all the bells and whistles is the main problem with me. Studying your mmg.bat file, and I realised it is that Critical Stop.wav that was driving me up the wall. Great idea with Mute_ErrorSound.reg.

I run mkvtoolnix-gui.exe now and all is silent. However, I think I had to run mmg.exe once to get this. I'll shut down and restart to see. I'll put up with that error message. Quick to flick it off.

That mmg.bat and all those files in Sources was a neat trick. :-)

shae
22nd October 2022, 19:56
1) revert the change which made the CLI-executables depend on Qt
(I.O.W., make them use the file magic.mgc again)

That's really bizarre. Any idea why they aren't plain console binaries?

Qt dependencies might explain why they are 12 MB or more each.

Why are you guys avoiding Win10?
Hassle of changing an OS, unpleasant GUI, tendencies to call home also when unasked, no benefit from upgrading.

j7n
23rd October 2022, 03:52
The last version working on WinXP is MMG v8 + mkvmerge.exe v19. Edit the version number in mkvmerge.exe right before "Brave Captain" to make the error message go away.

At the rate that the binaries are growing, you'll soon need to order a new computer from Germany just open them without any videos. There is no need to update to the latest version if you deal with "normal" last gen. videos in h.264/ac-3/etc.

I just updated to Win 2008 R2 this autumn, and it's already considered obsolete.

WSC4
8th November 2022, 13:05
Edit the version number in mkvmerge.exe right before "Brave Captain" to make the error message go away.


I downloaded version 19, fired up my hex editor and sure enough found Brave Captain way down towards the bottom of the file. I can see the version number. What do you change it to?

Can this also work with mkvmerge.exe version 29? It has "Like It Or Not" before the number.

j7n
9th November 2022, 01:22
Type over 19.0.0 and write 8.3.0. This only disables the nagging box on startup. After version 19 functionality required by the old gui that I prefer to use was removed.

WSC4
14th November 2022, 02:23
It needs to be 08.3.0 with a leading 0.

After I got that right, running the mkvtoolnix-gui.exe then produced a message box with a d3d9.dll error. This may be because I am running XP 64-bit. I did try both the 32 and 64 bit MKVToolNix 19 versions.

I then copied over and replaced mkvtoolnix-gui.exe 19 with mkvtoolnix-gui.exe 10 as manolito uses. This worked but still displays the original versions differ error box.

At the moment I'll use version 29, as that error box at start up does not bother me that much.

manolito
17th November 2022, 20:38
Version 71 built by user autodidact :thanks: @ VideoHelp-dot-com.

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix?p=2669522#post2669522

Looks like filler56789 is too busy for posting updates right now, so here is the latest build 72 by autodidact:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page3#post2672418


Cheers
manolito

kedautinh12
26th November 2022, 03:02
Better?? I seen it same??

manolito
26th November 2022, 06:39
It is not supposed to be better than Mosu´s version. The only difference to Mosu´s version is that it uses the older Qt version which still runs under Win7.

Quote by autodidact:
The author of mkvtoolnix uses qt to develop the software and recently moved from version 5 which is compatible with Windows 7, to version 6 which is not.


Cheers
manolito

kedautinh12
26th November 2022, 08:25
It is not supposed to be better than Mosu´s version. The only difference to Mosu´s version is that it uses the older Qt version which still runs under Win7.

Quote by autodidact:
The author of mkvtoolnix uses qt to develop the software and recently moved from version 5 which is compatible with Windows 7, to version 6 which is not.

Cheers
manolito
I answer comment from filler56789, he/she deleted comment :D

jpsdr
18th December 2022, 11:55
To test my Ubuntu install and if i was still able to build it, i've made a build of the 72.0.0.8, avaible on my github.

filler56789
18th December 2022, 15:42
To test my Ubuntu install and if i was still able to build it, i've made a build of the 72.0.0.8, avaible on my github.

Thanks! :thanks:

manolito
3rd January 2023, 03:50
Here is the latest build 73.0.0 by autodidact:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page4#post2676998


Cheers
manolito

kedautinh12
3rd January 2023, 04:24
Lol, very fast :D

hubblec4
3rd January 2023, 14:43
yeah very fast

ssjkakaroto
10th January 2023, 14:19
Thanks for this!

manolito
27th March 2023, 20:18
Here is the latest build 76.0 by autodidact:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page4#post2688455


Latest build here...


Cheers
manolito


/EDIT/
Looks like a lot of people are unhappy with version 76.0.
The previous version 75.0.0 is still available here:
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page4#post2685373

jpsdr
1st May 2023, 21:00
Hello.
You can find the latest build on my github.

jpsdr
17th May 2023, 17:47
Has somebody else issue with the current directory when opening adding files always going back to temporary instead of staying on the last opened with the 76 version ? This is a new issue only since the 76 version.
Made a build of the 76.0.45, but still not fixed.
Can't ask Mosu, as i don't know if it happens on all OS or only on Windows 7...

jpsdr
19th May 2023, 10:51
Made a build of the 76.0.46 (check my github), the "last opened" directory issue is fixed, thanks Mosu.

manolito
5th June 2023, 03:28
Here is the latest build 77.0 by autodidact:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page5#post2692485


Great news: The old "windowsvista" interface style is back. Thanks very much.

Enjoy...


Cheers
manolito

jpsdr
9th June 2023, 19:55
Now, on my Github, there is not just releases but the code cloned, with a Windows7 branch including the specific modifications for buidling a Windows 7 version. Vista style back is included ;).

hubblec4
10th June 2023, 12:02
many thanks for your work.

jpsdr
8th August 2023, 10:11
I've made an intermediate build, if any interested, check my github.

jpsdr
20th August 2023, 19:28
Made a build of 79, if interested, check my github.

manolito
21st August 2023, 17:46
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page5#post2702240

New version 79.0 is out. Many thanks to autodidact. Enjoy...

Cheers
manolito

jpsdr
21st August 2023, 18:59
I've made an intermediate build, if any interested, check my github.

Brazil2
22nd August 2023, 20:36
I've made an intermediate build, if any interested, check my github.
Thanks for the builds. :)
I'm interested but what is this 79.0.4 'intermediate' build ? What is the difference with 79.0.0 ? Are the commits from Mosu's repository or from your own ?

kedautinh12
23rd August 2023, 06:02
79.0.4 base commits from Mosu

jpsdr
3rd September 2023, 15:02
I've made an intermediate build, if any interested, check my github.

manolito
30th October 2023, 14:00
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page6#post2710594

Here is the latest version 80.0


Many thanks to autodidact...


Cheers
manolito

jpsdr
31st October 2023, 00:00
Made a build of 80.0.2, if interested, check my github.

jpsdr
1st November 2023, 19:35
Made a build of 80.0.7, if interested, check my github.

Koti
2nd November 2023, 06:47
Wanted to say "thank you" for your work on this

jpsdr
5th November 2023, 12:08
@Koti
You're welcome, but thanks should first go to autodidact, i'm just using what he has done.

Made a build of 80.0.16, if interested, check my github.

jpsdr
11th November 2023, 14:04
Made a build of 80.0.22, if interested, check my github.

jpsdr
20th November 2023, 21:59
Made a build of 80.0.31, if interested, check my github.

Liisachan
21st November 2023, 21:22
Thanks for doing this. I’m wondering, though… What are motivations that one might really want to use a newer version, when the output is often essentially identical, no matter which version you use (unless the version is very old or you’re doing something very experimental)?

As for font attachments, using a newer version with default settings could be even very harmful for backward compatibility!

Nevertheless, thanks again :)

oniiz86
22nd November 2023, 05:44
I for one am extremely grateful @jpsdr & autodidact over at videohelp have continued to release these builds for Win 7 users as MKVToolNix v79 build had a DTS fix that contributed to my DTS-HD MA 6.1 audio streams working correctly on my OPPO players bitstreamed to my Denon X8500H AVR, previous builds proved to be ineffective, I believe this was the bug fix that did it in the v79 release,
mkvmerge: DTS reader: if a DTS stream doesn't start with a DTS core but a sub-stream element (EXSS), the reader will now look for a core. If found, it'll start processing from there instead of from the start. This fixes the timestamp calculation if the sampling frequency in the core & in the extensions are different. Fixes #3602.

jpsdr
22nd November 2023, 18:57
One day, there will probably be a qt6 feature used impossible to switch back to qt5, but for now, there is not... And the later the better.
Also, i'm just building, thanks to autodidact who find the proper modificiations.

jpsdr
30th November 2023, 19:56
Made a build of 80.0.54, if interested, check my github.

manolito
2nd December 2023, 22:40
New version v81.0 is available. :thanks:
Download from here:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page6#post2714600


Cheers
manolito

jpsdr
3rd December 2023, 12:09
Made also a build of 81.0.0, if interested, check my github.

jpsdr
9th December 2023, 18:05
Made a build of 81.0.9, if interested, check my github.

jpsdr
10th December 2023, 12:46
Made a build of 81.0.19, if interested, check my github.

jpsdr
11th December 2023, 18:47
I didn't check the code yet, but just saw the name of the last commits from Mosu, it's the end of QT5 support. So i'll try to get only the bug fixes (if possible), but the end is close... :(

jpsdr
13th December 2023, 21:41
We are now in the Twilight Zone...
I've branched just before the end of QT5, and add some of the fixes. The version displayed will not match anymore, and now there is more risk of broken stuff.
Anyway, the "81.0.33" is on my github.

filler56789
14th December 2023, 10:33
I didn't check the code yet, but just saw the name of the last commits from Mosu, it's the end of QT5 support. So i'll try to get only the bug fixes (if possible), but the end is close... :(

Very saddening. That sucks too much, indeed.
Our only hope is, """someone""" will revert the groundless QT dependency for the command-line executables.
IF anyone wants a new GUI, this will have to be written in a dotNET language or in Java.

jpsdr
21st December 2023, 22:22
Some new Twilight Zone builds... ;)

jpsdr
1st January 2024, 14:58
A new year build :D. And happy new year.

Edit:
Just checked, nice new year gift from autodidact, who succed making a QT6 version with the QT6 modified for Windows 7.

Video Dude
1st January 2024, 17:30
Yes, it appears Windows 7 builds will continue.

manolito
29th April 2024, 00:03
New version 84.0 is available. :thanks:
Download from here:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page9#post2733416

Qt5 is still supported...


Cheers
manolito

jpsdr
29th April 2024, 17:15
There is still time to time stuff to adjust to keep QT5, but thanks to autodidact help i'm still able to follow.
And for now, the QT6 Windows 7 compatible is still also working.

manolito
2nd June 2024, 21:43
New version 85.0 is available. :thanks:
Download from here:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page9#post2738055

Qt5 is still supported...


Cheers
manolito

filler56789
3rd June 2024, 12:53
Yes, it appears Windows 7 builds will continue.


Yessss :cool: Resistance is futile :devil: :D

GMJCZP
3rd June 2024, 18:50
For a W7 32 bit user, it is appreciated ;-)

manolito
14th July 2024, 06:21
New version 86.0 is available. :thanks:
Download from here:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page9#post2742950


Cheers
manolito

filler56789
8th September 2024, 02:13
NON-OFFICIAL mkvtoolnix v87 is out.

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page15#post2749599

filler56789
20th October 2024, 03:15
NON-OFFICIAL mkvtoolnix v88.

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page16#post2754580

manolito
28th December 2024, 11:17
Here is mkvtoolnix v89.0 :)

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page11#post2761778

Many thanks to autodidact,

Cheers, and a Happy New Year...
manolito

shae
14th January 2025, 01:42
Thanks.

In the official builds, does QT6 bring any improvements?

filler56789
14th January 2025, 14:18
Thanks.

In the official builds, does QT6 bring any improvements?

Nope. Apparently the only goal of the endless QT ""updates"" is just annoy the users of the old versions of Windows.

source: https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page11#post2763793

So I did a little more digging in the code changes and found that the default font rendering had changed from GDI to directwrite starting in 6.8.0.
Of course it defaults to the Windows 10/11 version, which results in failure on Windows 7/8.

filler56789
9th February 2025, 10:36
NON-OFFICIAL version 90.0 is up and running! 🫡

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page17#post2766653

tebasuna51
13th February 2025, 07:44
Thanks, seems it is also needed with old W10 versions (https://forum.doom9.org/showthread.php?p=2014594#post2014594).

One question, if the problem is about the QT versions for what the exe's are also differents not only the GUI.

filler56789
13th February 2025, 10:16
.........
One question, if the problem is about the QT versions for what the exe's are also differents not only the GUI.

In the good old days, the command-line executables used the file magic.mgc for detecting the numerous input file contents. But some years ago, Mosu decided that Qt is "better than magic.mgc" at detecting file contents, so from that day on, the mkvtoolnix command-line .EXEs also depend on Qt.😩

tebasuna51
14th February 2025, 12:52
Thanks, seems there are other user with that build W7+W10-old

shae
12th September 2025, 15:09
Any reason to use the x64 version?

Assuming it's just data shuffling, there's no heavy processing involved, and so no real gains expected.

nevcairiel
12th September 2025, 18:42
Any reason to use the x64 version?

Assuming it's just data shuffling, there's no heavy processing involved, and so no real gains expected.

Any reason not to? Should really be the default these days.

manolito
13th September 2025, 00:04
Sorry I can't resist to reply... :p

Two clashing philosophies here.

MKVToolnix does not do any REENCODING, it just REPACKS the cource for a different container. Which is very useful. But from many years of using MKVToolnix I do know that the speed difference between the 32bit version and the 64bit version is minimal to non-existent. On a PC with low system memory it can even happen that the 32bit version is faster.

So please stop the religious fight about 32bit against 64bit. In most cases the answer is "It depends".


Just my 2 cents... :D
manolito

lvqcl
13th September 2025, 10:13
So please stop the religious fight about 32bit against 64bit.
I thought it was you who just tried to religiously defend 32bit?

huhn
13th September 2025, 10:54
Sorry I can't resist to reply... :p

Two clashing philosophies here. As nevcairiel posted recently:


LAV Filters does not do any REENCODING, it just REPACKS the cource for a different container. Which is very useful. But from many years of using LAV Filters I do know that the speed difference between the 32bit version and the 64bit version is minimal to non-existent. On a PC with low system memory it can even happen that the 32bit version is faster.

So please stop the religious fight about 32bit against 64bit. In most cases the answer is "It depends".


Just my 2 cents... :D
manolito
64 bit software decoding is massively faster. what was it 2x for h265 and 15 % for h264.
yes 64 bit software usual addresses more memory compared to the 32 bit version but that's it.

shae
14th September 2025, 18:50
Any reason not to? Should really be the default these days.
32-bit is potentially more compatible, and potentially smaller.

manolito
14th September 2025, 22:58
Correct... :p

Since MKVToolnix does not do any reencoding of the source files, there is no real acceleration when using the 64bit version. When using the GUI version MKVMergeGUI the GUI could potentially run a little faster in 64bit, but in my tests I did not get any speed increase with the 64bit version. Probably because the GUI uses the (64bit) operating system for all the mem copy and screen writing operations, so even under 32bit MKVToolnix these operations will run in 64bit.

And if you have an older computer with low system memory and a single-threaded CPU then the 32bit version will almost certainly run faster than the 64bit version.


Cheers
manolito

huhn
15th September 2025, 15:31
it does compression. and compression algorithm also benefit from 64 bit. you are usually limited by the IO speed anyway.

yes a single thread CPU with not enough memory to run the OS will benefit from a 32 bit version.
or you just get a dongle and use your smartphone instead.

the argument is pretty much the same as 32 bit version run on a 32 bit os the 64 bit doesn't.

manolito
15th September 2025, 18:05
it does compression. and compression algorithm also benefit from 64 bit

AFAIK it uses lossless compression only for subs by default. Video and Audio stays as it is. Quote from an older post by Mosu:
https://forum.doom9.org/showthread.php?p=1945234#post1945234

And all this applies only to the final remuxing, the source tracks are never decoded and then reencoded.

Cheers
manolito

huhn
15th September 2025, 18:59
yes i said compression but fair to point out.
very useful for LPCM too.

filler56789
8th November 2025, 22:26
NON-OFFICIAL version 96 has been released. :cool:

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix?p=2785998&viewfull=1#post2785998

manolito
3rd January 2026, 08:24
Here is mkvtoolnix v98.0

https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page14#post2795110

Many thanks to autodidact,

Cheers...
manolito