nicolaasjan

@VistaLover I have uploaded an updated Vista+ compatible PyInstaller here. Could you test if the yt-dlp built with it works well on your Vista system?

With version 3.6.0 new functionality has been added (3.6.1 is mainly a security release):

Ah, I see. Then I'm good to go on my main system with my own self-compiled OpenSSL libraries used by Python. These are nowhere to be found on the web.

I would like to know how to compile this on Windows 10 with MinGW/MSYS2.

I don't need them now, but others might prefer them. What I'm wondering is, why are your dll's larger in file size than the ones from here? libcrypto-3.dll: 5.19MB vs 4.38MB libssl-3.dll: 1.21MB vs 1.01MB More features?

I don't need them now, but others might prefer them. What I'm wondering is, why are your dll's larger in file size than the ones from here? libcrypto-3.dll: 5.19MB vs 4.38MB libssl-3.dll: 1.21MB vs 1.01MB More features?

Yes, those are XP compatible. There are also binaries here, but they are Vista+.

I tried this on XP (renamed to qjs.exe), but when running `yt-dlp -v`, it throws this:

Yes, that one probably didn't include the modified `yt_dlp/update.py` file... The Windows 7 one from GitHub updates fine: yt-dlp -U Current version: nicolaasjan/yt-dlp@2026.01.29.071857 Latest version: nicolaasjan/yt-dlp@2026.01.30.064627 Current Build Hash: e13632c9721715691dbbc989030c42552301cd670c32f5388dfc39fe46aa1c15 Updating to nicolaasjan/yt-dlp@2026.01.30.064627 ... Updated yt-dlp to nicolaasjan/yt-dlp@2026.01.30.064627 No, I grabbed the two 32-bit dll's from an install of the updated OpenSSL from here. (the 64-bit ones from there are not usable, as I explained earlier in this thread) I have absolutely no idea how to compile that on Windows.

Then it's easy to add my custom builds to it. They are different. And they can be updated with `yt-dlp -U`. PS, Do you plan to update your OpenSSL page?

I let the GitHub workflow build releases (which should be identical to upstream) and when that's done, I manually add my (custom Python) compiled versions in the web interface. After that, I use a Python script to fetch all the files and generate the SHA-256 and SHA-512 checksum files locally. Then replace the ones GitHub created with these, in order to make the (custom) update function* of my versions work. (*after having synchronised my fork with upstream, I clone it locally and apply a diff to `./yt_dlp/update.py` and then use that source tree in my VM's to compile) While the workflow is still running, I grab the version number from it and use that to update it in my builds as well: Then locally e.g.: python devscripts/update-version.py -c "nicolaasjan/yt-dlp" -r "nicolaasjan/yt-dlp" "2026.01.30.064627" python devscripts/set-variant.py win7_exe python -m bundle.pyinstaller I admit it's a rather hacky procedure, but it works.

You can read all about it in the Wiki. Deno can't be used on Windows 7. Node can be used if you use this fork. Take node-v20.19.2-win-x64.zip. extract to e.g. C:\Bin\Node and add that folder to your PATH. Can also be done via CMD as administrator: setx /m PATH "%PATH%;C:\Bin\Node" QuickJS can also be used, but it's rather slow (put qjs.exe and libwinpthread-1.dll next to yt-dlp.exe). Then add to your config file: --js-runtimes quickjs Or: --js-runtimes node

My releases have just been updated.

Well, I got it from a forum from a large country that is currently under heavy sanctions. 😳 Link to post. Maybe you can wake him up?

I can get avc codec with this: --extractor-args "youtube:player_client=default,ios,-android_sdkless;formats=missing_pot" -f "bv[protocol=m3u8_native][height<=1080][ext=mp4][vcodec^=avc]+ba[protocol=m3u8_native][ext=m4a]/b[protocol=m3u8_native]" (JS runtime required)