VistaLover

I had just completed my initial testing of your latest build on this old and under-resourced Vista SP2 32-bit laptop and, thankfully , I couldn't possibly reproduce your initial miserable qjs execution times ; FTR, this machine has a (2007-era) Intel Core2Duo T5250@1.50GHz CPU and 3GiB of DDR2 RAM; I used my stopwatch to time below yt-dlp command: yt-dlp_x86 --ies youtube --js-runtimes quickjs -vF "yrcIdXBwVww" and it actually took just 43s from when I clicked ENTER to full completion: [debug] Command-line config: ['--ies', 'youtube', '-vF', 'yrcIdXBwVww', '--js-runtimes', 'quickjs'] [debug] Encodings: locale cp1253, fs utf-8, pref cp1253, out utf-8 (No VT), error utf-8 (No VT), screen utf-8 (No VT) [debug] yt-dlp version local@2025.10.27 [937b84ddb] (win_x86_exe) [debug] Python 3.14.0 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.18 30 Sep 2025) [debug] exe versions: none [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.1.0, certifi-2025.10.05, mutagen-1.47.0, requests-2.32.5, sqlite3-3.50.4, urllib3-2.5.0, websockets-15.0.1, yt_dlp_ejs-0.2.1 [debug] JS runtimes: quickjs-2025-09-13 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Plugin directories: none [debug] Loaded 1 extractors [debug] [youtube] [pot] PO Token Providers: none [debug] [youtube] [pot] PO Token Cache Providers: memory [debug] [youtube] [pot] PO Token Cache Spec Providers: webpo [debug] [youtube] [jsc] JS Challenge Providers: bun (unavailable), deno (unavailable), node (unavailable), quickjs [youtube] Extracting URL: yrcIdXBwVww [youtube] yrcIdXBwVww: Downloading webpage [youtube] yrcIdXBwVww: Downloading tv client config [youtube] yrcIdXBwVww: Downloading player 25f1a420-main [debug] Saving youtube-sts.25f1a420-main to cache [youtube] yrcIdXBwVww: Downloading tv player API JSON [youtube] yrcIdXBwVww: Downloading web safari player API JSON [debug] [youtube] [jsc:quickjs] Using challenge solver lib script v0.2.1 (source: python package, variant: minified) [debug] [youtube] [jsc:quickjs] Using challenge solver core script v0.2.1 (source: python package, variant: minified) [debug] [youtube] [jsc:quickjs] Running quickjs: qjs --script 'C:\Users\<redacted>\AppData\Local\Temp\tmpp_d3itxv.js' [youtube] yrcIdXBwVww: Downloading m3u8 information [debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto [debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec, channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id [info] Available formats for yrcIdXBwVww: ID EXT RESOLUTION FPS CH | FILESIZE TBR PROTO | VCODEC VBR ACODEC ABR ASR MORE INFO ------------------------------------------------------------------------------------------------------------------ sb3 mhtml 48x27 0 | mhtml | images storyboard sb2 mhtml 80x45 1 | mhtml | images storyboard sb1 mhtml 160x90 1 | mhtml | images storyboard sb0 mhtml 320x180 1 | mhtml | images storyboard 140 m4a audio only 2 | 3.60MiB 129k https | audio only mp4a.40.2 129k 44k medium, TV, m4a_dash 251 webm audio only 2 | 103.22KiB 4k https | audio only opus 4k 48k medium, TV, webm_dash 91 mp4 256x144 30 | ~ 3.43MiB 123k m3u8 | avc1.4D400C mp4a.40.5 WEB-S 160 mp4 256x144 30 | 801.69KiB 28k https | avc1.4d400c 28k video only 144p, TV, mp4_dash 278 webm 256x144 30 | 806.96KiB 28k https | vp9 28k video only 144p, TV, webm_dash 92 mp4 426x240 30 | ~ 5.41MiB 195k m3u8 | avc1.4D4015 mp4a.40.5 WEB-S 133 mp4 426x240 30 | 1.47MiB 53k https | avc1.4d4015 53k video only 240p, TV, mp4_dash 242 webm 426x240 30 | 1.22MiB 44k https | vp9 44k video only 240p, TV, webm_dash 93 mp4 640x360 30 | ~ 11.03MiB 397k m3u8 | avc1.4D401E mp4a.40.2 WEB-S 134 mp4 640x360 30 | 2.83MiB 102k https | avc1.4d401e 102k video only 360p, TV, mp4_dash 18 mp4 640x360 30 2 | 4.15MiB 149k https | avc1.42001E mp4a.40.2 22k 360p, TV 243 webm 640x360 30 | 2.36MiB 85k https | vp9 85k video only 360p, TV, webm_dash 94 mp4 854x480 30 | ~ 20.21MiB 728k m3u8 | avc1.4D401F mp4a.40.2 WEB-S 135 mp4 854x480 30 | 4.91MiB 177k https | avc1.4d401f 177k video only 480p, TV, mp4_dash 244 webm 854x480 30 | 4.22MiB 152k https | vp9 152k video only 480p, TV, webm_dash 95 mp4 1280x720 30 | ~ 41.07MiB 1479k m3u8 | avc1.64001F mp4a.40.2 WEB-S 136 mp4 1280x720 30 | 10.33MiB 372k https | avc1.64001f 372k video only 720p, TV, mp4_dash 247 webm 1280x720 30 | 9.39MiB 338k https | vp9 338k video only 720p, TV, webm_dash 96 mp4 1920x1080 30 | ~ 81.20MiB 2923k m3u8 | avc1.640028 mp4a.40.2 WEB-S 137 mp4 1920x1080 30 | 20.18MiB 727k https | avc1.640028 727k video only 1080p, TV, mp4_dash 248 webm 1920x1080 30 | 16.53MiB 596k https | vp9 596k video only 1080p, TV, webm_dash 271 webm 2560x1440 30 | 41.46MiB 1494k https | vp9 1494k video only 1440p, TV, webm_dash Those 43s include the time the PyInst binary took to extract its content inside the %TEMP% folder of my Windows User Account ; and this was for the FIRST yt-dlp invocation, next ones took even less ; TL:DR: QuickJS is totally workable here, thanks a lot to you, to the yt-dlp devs and to a certain GitHub member (barracuda156) who actually "fought" to have QJS included as a supported external JS runtime! Below, an actual successful DL log: yt-dlp_x86 --ies youtube --js-runtimes quickjs -vf 140 "yrcIdXBwVww" [debug] Command-line config: ['--ies', 'youtube', '--js-runtimes', 'quickjs', '-vf', '140', 'yrcIdXBwVww'] [debug] Encodings: locale cp1253, fs utf-8, pref cp1253, out utf-8 (No VT), error utf-8 (No VT), screen utf-8 (No VT) [debug] yt-dlp version local@2025.10.27 [937b84ddb] (win_x86_exe) [debug] Python 3.14.0 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.18 30 Sep 2025) [debug] exe versions: ffmpeg 5.0 (fdk,setts) [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.1.0, certifi-2025.10.05, mutagen-1.47.0, requests-2.32.5, sqlite3-3.50.4, urllib3-2.5.0, websockets-15.0.1, yt_dlp_ejs-0.2.1 [debug] JS runtimes: quickjs-2025-09-13 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Plugin directories: none [debug] Loaded 1 extractors [debug] [youtube] [pot] PO Token Providers: none [debug] [youtube] [pot] PO Token Cache Providers: memory [debug] [youtube] [pot] PO Token Cache Spec Providers: webpo [debug] [youtube] [jsc] JS Challenge Providers: bun (unavailable), deno (unavailable), node (unavailable), quickjs [youtube] Extracting URL: yrcIdXBwVww [youtube] yrcIdXBwVww: Downloading webpage [youtube] yrcIdXBwVww: Downloading tv client config [debug] Loading youtube-sts.6e4dbefe-main from cache [youtube] yrcIdXBwVww: Downloading tv player API JSON [youtube] yrcIdXBwVww: Downloading web safari player API JSON [youtube] yrcIdXBwVww: Downloading player 6e4dbefe-main [debug] [youtube] [jsc:quickjs] Using challenge solver lib script v0.2.1 (source: python package, variant: minified) [debug] [youtube] [jsc:quickjs] Using challenge solver core script v0.2.1 (source: python package, variant: minified) [debug] [youtube] [jsc:quickjs] Running quickjs: qjs --script 'C:\Users\<redacted>\AppData\Local\Temp\tmp8kc1jvmr.js' [youtube] yrcIdXBwVww: Downloading m3u8 information [debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto [debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec, channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id [info] yrcIdXBwVww: Downloading 1 format(s): 140 [debug] Invoking http downloader on "https://rr1---sn-4vguioxu-n3bz.googlevideo.com/videoplayback?expire=1761596706&ei=woD_aJTNJ_eG0u8Psu7R0AE&ip=<redacted>&id=o-ABLy9SDAL9azDltc64Qry1Wjfc2T-ukUkgAK7YIGNBjU&itag=140&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&met=1761575106%2C&mh=e1&mm=31%2C29&mn=sn-4vguioxu-n3bz%2Csn-nv47lnsk&ms=au%2Crdu&mv=m&mvi=1&pl=22&rms=au%2Cau&initcwndbps=1093750&bui=AdEuB5S9H_ZLOx4DhWandbVVoE2T23TniDsH9dzuJWA1A2BTXilW4PS4MvJfCH8rm5PYm_rkKk1bNbUl&vprv=1&svpuc=1&mime=audio%2Fmp4&ns=3j_zEDpH1UcvQ1PnFTnBiuoQ&rqh=1&gir=yes&clen=3769997&dur=232.896&lmt=1758938329553945&mt=1761574619&fvip=3&keepalive=yes&lmw=1&fexp=51557447%2C51565115%2C51565682%2C51580970&c=TVHTML5&sefc=1&txp=6208224&n=Uyc5Xoc53RETOw&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cbui%2Cvprv%2Csvpuc%2Cmime%2Cns%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&sig=AJfQdSswRAIgYqAE1n3WKMewWR3MOnwuPURtZm5QnMnZlMtNJQaTmV0CIDbOyrrvXFyR2m1kUheTy_ik6DIXA9UXoZzbOs1ffk3a&lsparams=met%2Cmh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Crms%2Cinitcwndbps&lsig=APaTxxMwRQIgGZIroMcG7xUvn-eLhnLxe3FP_A-zu5lRB5wrz3pjoEoCIQChTmzqkvfj8R_MXFuYDQ5u9h56fAQdFtIm902IyqUrCg%3D%3D" [debug] File locking is not supported. Proceeding without locking [download] Destination: Patching yt-dlp (silent) [yrcIdXBwVww].m4a [download] 100% of 3.60MiB in 00:00:04 at 782.66KiB/s [FixupM4a] Correcting container of "Patching yt-dlp (silent) [yrcIdXBwVww].m4a" [debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i "file:Patching yt-dlp (silent) [yrcIdXBwVww].m4a" -map 0 -dn -ignore_unknown -c copy -f mp4 -movflags +faststart "file:Patching yt-dlp (silent) [yrcIdXBwVww].temp.m4a" ... Which is where I pointed people to in my previous post : So, does the latest QJS (32-bit) launch on WinXP SP3? FWIW, I don't like adding stuff to PATH unless I can't do otherwise; placing the qjs.exe (with its DLL dependency) adjacent to the yt-dlp_x86.exe binary was all it took here ... And a slight word of caution: Of the four external JS runtimes supported by yt-dlp, QJS is the least secure one ; it has no sandbox, needs to write to the host machine's TEMP dir and is subject to some exploits related to Temp files: https://github.com/coletdjnz/yt-dlp-wiki-dev/blob/ejs/EJS.md#notes-3 Myself, I'd ONLY invoke it from the cmdline when I need to use YT, not permanently enable it via a config setting; call me paranoid ... Kind regards.

... Indeed ; I still keep an old (2018) version of MABS on an external disk, I used that to "strip" the DLL, $ cd ~ $ strip "libfdk-aac-2.dll" and filesize was reduced from 2.11 MiB to 1.73 MiB (but still larger than the 1.34 MiB of the "xpmod-P4" variety ) ...

1. This one does launch OK under Vista SP2 32-bit . 2. Instead of the cmdline flag/config setting "--remote-components ejs:github" you could've built the PyInstaller binary with the EJS components bundled, as will upstream do : https://github.com/coletdjnz/yt-dlp-wiki-dev/blob/ejs/EJS.md#step-2-install-ejs-challenge-solver-scripts You can install them via PyPI prior to PyInst compilation: python -m pip install -U yt-dlp-ejs and, hopefully, they'll be integrated into the produced executable, just like the rest of the default Python modules... 3. " --remote-components ejs:npm" applies ONLY to deno/bun, NOT to node used on Win7 : https://github.com/coletdjnz/yt-dlp-wiki-dev/blob/ejs/EJS.md#option-2-enable-ejs-script-downloads-from-npm 4. At the time the binary was compiled, quickjs support hadn't yet arrived, thus: yt-dlp_x86 --ies youtube -vF "yrcIdXBwVww" --remote-components ejs:github --js-runtimes quickjs => ... WARNING: Ignoring unsupported JavaScript runtime(s): quickjs. Supported runtimes: deno, node, bun. ... [debug] [youtube] [jsc] JS Challenge Providers: bun (unavailable), deno (unavailable), node (unavailable) ... [info] Available formats for yrcIdXBwVww: ID EXT RESOLUTION FPS | FILESIZE TBR PROTO | VCODEC ACODEC MORE INFO ----------------------------------------------------------------------------------- sb3 mhtml 48x27 0 | mhtml | images storyboard sb2 mhtml 80x45 1 | mhtml | images storyboard sb1 mhtml 160x90 1 | mhtml | images storyboard sb0 mhtml 320x180 1 | mhtml | images storyboard 91 mp4 256x144 30 | ~ 3.43MiB 123k m3u8 | avc1.4D400C mp4a.40.5 WEB-S 92 mp4 426x240 30 | ~ 5.41MiB 195k m3u8 | avc1.4D4015 mp4a.40.5 WEB-S 93 mp4 640x360 30 | ~11.03MiB 397k m3u8 | avc1.4D401E mp4a.40.2 WEB-S 94 mp4 854x480 30 | ~20.21MiB 728k m3u8 | avc1.4D401F mp4a.40.2 WEB-S 95 mp4 1280x720 30 | ~41.07MiB 1479k m3u8 | avc1.64001F mp4a.40.2 WEB-S 96 mp4 1920x1080 30 | ~81.20MiB 2923k m3u8 | avc1.640028 mp4a.40.2 WEB-S Best regards.

Most sadly, this is only part of the story ; probing the v20.19.2 (32-bit) binary (a whooping 61.3 MiB in filesize) with DependencyWalker, I found a total of six (6) Vista-incompatible function calls: in advapi32.dll: EventSetInformation in kernel32.dll: K32GetModuleBaseNameW K32GetProcessMemoryInfo ResolveLocaleName TryAcquireSRWLockExclusive TryAcquireSRWLockShared The first one can also be a thing on a partially updated Win7 SP1 install (see this); thank you for already raising a Vista-support issue with Vladimir ...

Breaking news: https://github.com/yt-dlp/yt-dlp/issues/14404#issue-3444474002 https://bellard.org/quickjs/binary_releases/?C=M;O=D For my Vista SP2 32-bit laptop: https://bellard.org/quickjs/binary_releases/quickjs-win-i686-2025-09-13.zip ... and: qjs -h QuickJS version 2025-09-13 usage: qjs [options] [file [args]] -h --help list options -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -m --module load as ES6 module (default=autodetect) --script load as ES6 script (default=autodetect) -I --include file include an additional file --std make 'std' and 'os' available to the loaded script -T --trace trace memory allocation -d --dump dump the memory usage stats --memory-limit n limit the memory usage to 'n' bytes (SI suffixes allowed) --stack-size n limit the stack size to 'n' bytes (SI suffixes allowed) --no-unhandled-rejection ignore unhandled promise rejections -s strip all the debug info --strip-source strip the source code -q --quit just instantiate the interpreter and quit Though, this might still mean nothing, as I haven't gotten around to actually trying https://github.com/yt-dlp/yt-dlp/pull/14157 on this machine... Wiki (WIP): https://github.com/coletdjnz/yt-dlp-wiki-dev/blob/ejs/EJS.md

Some additional details : --enable-cuda --enable-cuvid --enable-nvenc --enable-nvdec I only have an Intel iGPU which H/W decodes MPEG-2 only, no external NVIDIA gfx card either, so I couldn't possibly use those inside FFmpeg ... --enable-mediafoundation Despite Vista SP2+Platform Update Supplement (PUS) having a working form of WMF, backported from Win7 and installed as a MS Update, I've found, via using other FFmpeg builds with that flag enabled, that I can't use the WMF encoders (h264/aac) in FFmpeg for transcoding purposes; probably this specific flag requires a Win7+ OS, where the WMF feature is fully matured ... --enable-d3d12va --enable-vulkan AFAIK, these both are not compatible with/offered on Vista SP2... --enable-libvpx --enable-libkvazaar --enable-libxavs --enable-libdav1d --enable-libaom --enable-librav1e I don't see myself using the encoder part of those video codecs on this specific, under-resourced, "vintage" 32-bit machine ; however, if the decoder part of any of them can't be substituted with a native FFmpeg implementation, then, I guess, it should stay (?) ... --enable-libmysofa Well. in RL scenarios I haven't had the need myself to use SOFA files with HRTF content, however, since this is related to acoustics (audio) and assuming it doesn't add much to binary filesize, I guess it can stay enabled/included after all ... Please, keep it enabled ; the native AAC encoder isn't fully, yet, on par with the Fraunhofer one (and, correct me if wrong, doesn't allow for HE-AACv1/v2 transcoding profiles); BTW, below: https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7/page2#post2771491 I'm seeing archive "libfdk-aac-v2.0.3-158-gd8e6b1a-x86.7z" intended for Win7SP1_x86; this one affords a DLL much larger (2.10 MiB) than the DLL extracted from archive "libfdk-aac-2.0.3-158-d8e6b1a-win32-xpmod-P4.7z" (1.33 MiB) ; I've probed the former with DepWalker and it appears to be Vista-compatible, though I haven't yet used it in an audio transcoding job... In closing, I'm not the sole Vista user around here and if your Vista-compat FFmpeg offerings are to benefit a broader Vista+ community, then you can still include any external lib you see fit - I initially only requested a shared_x86 compile, my wish has been granted and I'm extremely grateful to you ! Kindest regards .

Thanks! Launches OK here: ffmpeg version N-121515-gdefd5f3f64-WINVISTA Copyright (c) 2000-2025 the FFmpeg developers built with gcc 15.2.0 (Rev8, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d12va --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-mediafoundation --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-librav1e --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libkvazaar --enable-libmodplug --enable-librubberband --enable-libxavs --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-vulkan --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libvvenc --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-libcelt --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opencl --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 60. 14.100 / 60. 14.100 libavcodec 62. 16.100 / 62. 16.100 libavformat 62. 6.101 / 62. 6.101 libavdevice 62. 2.100 / 62. 2.100 libavfilter 11. 9.100 / 11. 9.100 libswscale 9. 3.100 / 9. 3.100 libswresample 6. 2.100 / 6. 2.100 Universal media converter usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}... Use -h to get full help or, even better, run 'man ffmpeg' Some remarks: 1. The extracted .7z archive yields a folder sized 125 MiB, i.e. ca. 100 MiB less compared to using both static FFmpeg.exe+FFprobe.exe binaries ... 2. --enable-libfdk-aac : I take it this means I can still use the "libfdk-aac-2.dll" file from inside the "libfdk-aac-2.0.3-158-d8e6b1a-win32-xpmod-P4.7z" archive to enable that (non-free) audio encoder? 3. This is just an observation, but this build configuration still contains a lot of flags/libs either not applicable to my platform (e.g. --enable-d3d12va) or ones I'd never use myself: --enable-cuda --enable-cuvid --enable-d3d12va --enable-nvenc --enable-nvdec --enable-mediafoundation --enable-libvpx --enable-libdav1d --enable-libaom --enable-libmysofa --enable-librav1e --enable-libkvazaar --enable-libxavs --enable-vulkan But I see what you did there ; this is not tailored specifically to an old Vista SP2 32-bit machine with iGPU (Intel), but is a full-fledged compile (full set of libs/filters/etc.), with minimum OS requirement lowered to NT 6.0; all those extra libs can still be used efficiently on a more recent WinOS, with more powerful H/W ... 4. N-121515-gdefd5f3f64 : For those who prefer a slightly different git-versioning scheme, this is equal to n8.1-dev-891-git-2025-10-25-gdefd5f3 i.e. built from a master branch code snapshot (commit defd5f3) authored today, which is the 891st commit after tag "n8.1-dev" was cut ... Really impressive, am much obliged! The retrocomputing communities are in high need of altruistic persons such as yourself! Take the best of care...

@nicolaasjan : https://3dyd.github.io/pyinstaller-builds/ Your prayers have been answered! https://github.com/3dyd/pyinstaller-builds https://github.com/3dyd/pyinstaller/tree/6.16.0-xp

Thanks a lot for your reply ; as I wrote, Vista SP2 32-bit here; from 2016-2018 I used to use MABS (MSYS2/MinGW) to compile locally non-free ffmpeg builds; after that time, several MSYS2 components went Win7+ (e.g. "make") and by 2021, the compiler itself stopped being available for the 32-bit architecture; needless to say, latest MABS is meant for a recent version of Win10 64-bit; yes, you probably can still compile 32-bit binaries with it, but those won't run on Vista, possibly not on Win7, too ... The AnimMouse ffmpeg builds used to be Vista-compatible, but broke at some time (early 2022); as a Vista user too, you probably know those things already ... I'm not closely following current FFmpeg development ; at one time I was aware that the FFmpeg code itself continued to be NT 6.0 compatible (as opposed to NT 5.x), so that a "no-libs" compiled binary would launch normally under Vista; but a lot of the third party (external) libs built normally into FFmpeg are the main culprits for breaking Vista-support (x265 comes to mind, with its NUMA Win7+ functions ) ; it must be quite an enormous task today for you to restore NT 6.1/6.0 and even 5.x support on your custom FFmpeg builds; you are to be highly praised for this feat ... On a 32-bit, under-resourced (by today's standards ) machine, I practically have little use of most of those extra libs (especially video encoders); I rarely do video transcoding here, mostly audio transcoding is being performed; it's those many optional external libs that inflate static binaries' filesize and are the cause for broken NT 6.0 support, for all I know... Thanks for your intention! User Reino here (now on Win11) used to offer both static+shared 32-bit builds, targeting WinXP SP3 and an SSE-only CPU, ca. every 4 months ; it'd be very sweet from you if you managed to offer something similar, but for more recent CPUs (e.g. SSE2+) and on Vista+... FWIW, this thread started a long while ago and mentions "winxp" in its title, but is actually frequented now by members of various WinOSes ; so I hope you posting Vista+ FFmpeg builds will be OK ; of course, there's always that ... "Willing to test? " -> Simply throw "them" at me ... Best regards.

Many thanks, indeed ; my OS is actually Windows Vista SP2 32-bit, my CPU can go up to SSSE3 instruction set, iGPU; so, I have to make do with XP-targeting builds ... I see the linked files are hosted on VideoHelp.com and, after searching, found out you do have an account on: https://forum.videohelp.com/ Is there a specific FVH.com thread that you announce/publish your FFmpeg XP/Vista builds in? There's https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7 but, as one would expect, the 32-bit compiles posted there do not run on Vista SP2 32-bit (as they target NT 6.1 +) ; I know it'd be a lot to ask already, but do you see yourself publishing shared FFmpeg_x86 builds compatible with Vista SP2 / XP SP3 ? yt-dlp actually wants BOTH the ffmpeg.exe+ffprobe.exe binaries for postprocessing; static builds of them have now exploded to ca. 110 MiB each, I find it too much to use 220 MiB of disk space just for remuxing purposes ... Thanks for your efforts so far, much appreciated ...

... Be that as it may, I've witnessed the same thing on my own (i.e. on clips other than the one mentioned in the linked GH issue), e.g. on "SxVNOnPyvIU": yt-dlp_x86 -vF "SxVNOnPyvIU" => 95 mp4 1280x720 24 | ~23.64MiB 754k m3u8 | avc1.4D401F mp4a.40.2 WEB-S 136 mp4 1280x720 24 | 8.67MiB 277k https | avc1.4d401f 277k video only 720p, TV, mp4_dash 247 webm 1280x720 24 | 9.30MiB 297k https | vp9 297k video only 720p, TV, webm_dash 398 mp4 1280x720 24 | 9.48MiB 302k https | av01.0.05M.08 302k video only 720p, TV, mp4_dash 96 mp4 1920x1080 24 | ~64.60MiB 2060k m3u8 | avc1.640028 mp4a.40.2 WEB-S 137 mp4 1920x1080 24 | 30.06MiB 958k https | avc1.640028 958k video only 1080p, TV, mp4_dash 248 webm 1920x1080 24 | 25.13MiB 801k https | vp9 801k video only 1080p, TV, webm_dash 399 mp4 1920x1080 24 | 16.68MiB 532k https | av01.0.08M.08 532k video only 1080p, TV, mp4_dash ca. 300kbps for the video track for a 720p24 resolution is just too little, if you ask me; likewise for the 1080p24 resolution; notice how the Web Safari (WEB-S) formats have twice the bitrate of the TV_client (TV) formats ... FWIW, I don't consume that much of YT myself ; perhaps @j7n can share more on this ... Regards.

Well, both these missing DLLs are referred to as "dependencies" of wrapper DLL "kernelxp.dll"; but @cmalex has never provided them in his custom, XP-targeting, CPython assemblies, e.g. https://mega.nz/folder/jst2WJ5B#sknEpEBamwPomx8UULWuMA/file/igNWhbCb so he should know better ; in fact, I have tracked those wrapper DLLs (kernelxp.dll, ntext.dll, psapi.dll, ws2_xx.dll) inside below folder: https://mega.nz/folder/KxExlAiC#L9rAQ5kTCtlHgZUwaxMpgw/folder/Os1DmLgL and the accompanying README simply states: In any case, PyInstaller just issues WARNINGs, no fatal errors, and the resultant packages function as expected; so, these warnings can be regarded as "red herrings" and can be safely ignored; just my 2c ...

Well, it has come back again here ; I have to re-launch yt-dlp several times repeatedly to have the "tv_client" streams appear; most of the time, I simply get: WARNING: [youtube] ero26lcWXjo: Some tv client https formats have been skipped as they are missing a url. YouTube may have enabled the SABR-only or Server-Side Ad Placement experiment for the current session. See https://github.com/yt-dlp/yt-dlp/issues/12482 for more details WARNING: [youtube] ero26lcWXjo: Some web_safari client https formats have been skipped as they are missing a url. YouTube is forcing SABR streaming for this client. See https://github.com/yt-dlp/yt-dlp/issues/12482 for more details ... WARNING: [youtube] ero26lcWXjo: Some web client https formats have been skipped as they are missing a url. YouTube is forcing SABR streaming for this client. See https://github.com/yt-dlp/yt-dlp/issues/12482 for more details Well, this "poor quality" problem has now come back, but this time also affecting the vp9+av01 encodes ; an issue has been filed on GitHub: https://github.com/yt-dlp/yt-dlp/issues/14636 Nothing can be done from a yt-dlp standpoint ...

; starred and watching ... Confirmed : yt-dlp_x86_win7 -v [debug] Command-line config: ['-v'] [debug] Encodings: locale cp1253, fs utf-8, pref cp1253, out cp1253 (No VT), error cp1253 (No VT), screen cp1253 (No VT) [debug] yt-dlp version nicolaasjan/yt-dlp@2025.10.15.061641 (win7_x86_exe*) [debug] Python 3.14.0 (CPython AMD64 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.18 30 Sep 2025) [debug] exe versions: none [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.1.0, certifi-2025.10.05, mutagen-1.47.0, requests-2.32.5, sqlite3-3.50.4, urllib3-2.5.0, websockets-15.0.1 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Plugin directories: none [debug] Loaded 1839 extractors Usage: yt-dlp_x86 [OPTIONS] URL [URL...] yt-dlp_x86: error: You must provide at least one URL. Type yt-dlp --help to see a list of all options. Splendid job!

I'm sorry. I have no idea... ... At least I got this figured out, as it was seriously bugging me ; the "what" is hidden inside a changelog: https://github.com/adang1345/PythonVista/blob/master/CHANGELOG.md Your v2025.09.23.052315 yt-dlp_x86_win7.exe binary has been compiled with a flavour of 3.13.7 which, at that time, supported only Win7+ ; Vista support for 3.13.7 came on Sep 25th, 2 days after v2025.09.23.052315 was built, but in time for the v2025.09.27.071342 to be built with a Vista-enabled 3.13.7 interpreter (this assumes you manually updated to the Vista-compat flavour of 3.13.7) ... What is still unclear to me is: a) were both versions built on the same OS (Win7 SP1 ?) ? b) were both versions packaged with "official" PyInstaller-6.16.0 ? v2025.09.27.071342: [debug] yt-dlp version nicolaasjan/yt-dlp@2025.09.27.071342 (win7_x86_exe*) [debug] Python 3.13.7 (CPython AMD64 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.16 11 Feb 2025) and v2025.10.05.061237 [debug] yt-dlp version nicolaasjan/yt-dlp@2025.10.05.061237 (win7_x86_exe*) [debug] Python 3.13.7 (CPython AMD64 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.16 11 Feb 2025) have been both compiled on a 64-bit OS, with the 32-bit build of Vista-compatible 3.13.7; why, then, is the next v2025.10.13.80600, built on a Vista-compatible 3.14.0, broken on actual Vista SP2 32-bit? I have a hunch, based on adang1345's notes: https://github.com/adang1345/PythonVista/blob/master/README.md So, the same 3.14.0 CPython will behave differently when run on a Win7 machine to when run on a Vista machine; likewise for the PyInstaller-packaged resultant yt-dlp_x86_win7.exe binaries; but this theory doesn't explain builds v2025.09.27.071342+v2025.10.05.061237 (which run OK on Vista), unless they were also compiled on a Vista SP2 64-bit VM ... FWIW, adang1345 has made a new release of 3.13.9 less than an hour ago, https://github.com/adang1345/PythonVista/tree/master/3.13.9 and issued a re-release of 3.14.0 along with the above: https://github.com/adang1345/PythonVista/tree/master/3.14.0 His changelog only mentions the addition of 3.13.9, though ... This one launches OK: [debug] yt-dlp version local@2025.10.13 [eafedc218] (win_x86_exe) [debug] Python 3.14.0 (CPython AMD64 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.18 30 Sep 2025) Was a Vista SP2 64-bit VM used in this case? And which PyInst version? This one launches fine : yt-dlp_x86_win7.exe -v [debug] Command-line config: ['-v'] [debug] Encodings: locale cp1253, fs utf-8, pref cp1253, out utf-8 (No VT), error utf-8 (No VT), screen utf-8 (No VT) [debug] yt-dlp version nicolaasjan/yt-dlp@2025.10.13.080600 (win7_x86_exe*) [debug] Python 3.14.0 (CPython AMD64 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.0.18 30 Sep 2025) [debug] exe versions: none [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.1.0, certifi-2025.10.05, mutagen-1.47.0, requests-2.32.5, sqlite3-3.50.4, urllib3-2.5.0, websockets-15.0.1 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Plugin directories: none [debug] Loaded 1834 extractors Usage: yt-dlp_x86_win7.exe [OPTIONS] URL [URL...] yt-dlp_x86_win7.exe: error: You must provide at least one URL. Type yt-dlp --help to see a list of all options. Less puzzled now , but still with unanswered questions ... Time to call it a night, regards...