Leaderboard

Conspiracy theory (meaning, don't take this seriously): Google has a secret agreement with CloudFlare to force users to update to the latest Chrome by breaking older browser versions as soon as Google releases newer ones. Happens to affect Chromium too, but most users are on official Chrome or ChrEdge.

I saw that "WARNING" only once (but I don't fetch YT that often ) and put it down to a transient "glitch" on YT's side; BTW, it was specific to the "ios-downgraded" YT player client (see below) ... The "ios-downgraded" YT player client (m3u8 formats) had a very short lifespan , as it was removed in https://github.com/yt-dlp/yt-dlp/commit/c3674575faa23b20e97be8b73f68b9f7b4cea9ab (https://github.com/yt-dlp/yt-dlp/pull/15786) as a result of https://github.com/yt-dlp/yt-dlp/issues/15782 The sample YT clip on that issue was geo-blocked (Vietnam-only), so I couldn't test/replicate myself (and I do wonder whether the devs could, either); but the firm conviction (by the devs) that the IOS client is "unreliable" led to "ios-downgraded" being unceremoniously axed (and the issue was later locked, due to OT chit-chat) ... The last official master build with that client enabled was 2026.01.31.224855; the last nicolaasjan build with that client enabled was 2026.01.30.064627; the fact your log mentions "ios downgraded player" means you're on one of the "older" builds... The removal of the "ios_downgraded player" means that currently, without enabling a JS runtime (and without a YT account), ONLY the "android_vr" formats are available (no m3u8, though); with a JS runtime enabled, you'll also get the few WEB-S (web_safari) m3u8 formats offered... FWIW, for me (in my part of the world), the "ios_downgraded" yt-client formats (ALL m3u8) still work as I write this; so, I try to locally revert c367457 and make use of them: yt-dlp -vF "cnX5zJ_qGz0" => [debug] Command-line config: ['--ffmpeg-location', 'FFmpeg', '--downloader-args', 'ffmpeg_i:-hide_banner -v 8 -stats', '-vF', 'cnX5zJ_qGz0'] [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 master@2026.02.21.201720 from yt-dlp/yt-dlp-master-builds [646bb31f3] (zip) [debug] Python 3.11.14 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 (OpenSSL 3.6.1 27 Jan 2026) [debug] exe versions: ffmpeg n8.1-dev-630-N-121254-g635cb45 (setts), ffprobe n8.1-dev-630-N-121254-g635cb45 [debug] Optional libraries: Cryptodome-3.23.0, brotli-1.2.0, certifi-2026.01.04, mutagen-1.47.0, requests-2.32.5, sqlite3-3.51.2, urllib3-2.6.3, websockets-16.0, yt_dlp_ejs-0.5.0 [debug] JS runtimes: none [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Plugin directories: none [debug] Loaded 1864 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 (unavailable) [youtube] Extracting URL: cnX5zJ_qGz0 [youtube] cnX5zJ_qGz0: Downloading webpage WARNING: [youtube] No supported JavaScript runtime could be found. Only deno is enabled by default; to use another runtime add --js-runtimes RUNTIME[:PATH] to your command/config. YouTube extraction without a JS runtime has been deprecated, and some formats may be missing. See https://github.com/yt-dlp/yt-dlp/wiki/EJS for details on installing one [debug] [youtube] Forcing "tv" player JS variant for player 4c5cf06a original url = /s/player/4c5cf06a/player_es6.vflset/en_US/base.js [youtube] cnX5zJ_qGz0: Downloading android vr player API JSON [youtube] cnX5zJ_qGz0: Downloading ios downgraded player API JSON [debug] [youtube] cnX5zJ_qGz0: ios_downgraded client https formats require a GVS PO Token which was not provided. They will be skipped as they may yield HTTP Error 403. You can manually pass a GVS PO Token for this client with --extractor-args "youtube:po_token=ios_downgraded.gvs+XXX". For more information, refer to https://github.com/yt-dlp/yt-dlp/wiki/PO-Token-Guide [youtube] cnX5zJ_qGz0: 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 cnX5zJ_qGz0: 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 0 | mhtml | images storyboard sb1 mhtml 160x90 0 | mhtml | images storyboard sb0 mhtml 320x180 0 | mhtml | images storyboard 233 mp4 audio only | m3u8 | audio only unknown [en] Untested, Default, low, IOS-D 234 mp4 audio only | m3u8 | audio only unknown [en] Untested, Default, high, IOS-D 139 m4a audio only 2 | 6.36MiB 49k https | audio only mp4a.40.5 49k 22k [en] low, ANDR-V, m4a_dash 249 webm audio only 2 | 6.56MiB 50k https | audio only opus 50k 48k [en] low, ANDR-V, webm_dash 140 m4a audio only 2 | 16.89MiB 129k https | audio only mp4a.40.2 129k 44k [en] medium, ANDR-V, m4a_dash 251 webm audio only 2 | 15.25MiB 117k https | audio only opus 117k 48k [en] medium, ANDR-V, webm_dash 602 mp4 256x144 12 | ~ 11.26MiB 86k m3u8 | vp09.00.10.08 86k video only Untested, IOS-D 269 mp4 256x144 24 | ~ 22.13MiB 170k m3u8 | avc1.4D400C 170k video only Untested, IOS-D 160 mp4 256x144 24 | 9.00MiB 69k https | avc1.4d400c 69k video only 144p, ANDR-V, mp4_dash 603 mp4 256x144 24 | ~ 16.84MiB 129k m3u8 | vp09.00.11.08 129k video only Untested, IOS-D 278 webm 256x144 24 | 8.15MiB 63k https | vp9 63k video only 144p, ANDR-V, webm_dash 394 mp4 256x144 24 | 6.96MiB 53k https | av01.0.00M.08 53k video only 144p, ANDR-V, mp4_dash 229 mp4 426x240 24 | ~ 40.49MiB 310k m3u8 | avc1.4D4015 310k video only Untested, IOS-D 133 mp4 426x240 24 | 19.12MiB 147k https | avc1.4d4015 147k video only 240p, ANDR-V, mp4_dash 604 mp4 426x240 24 | ~ 28.77MiB 221k m3u8 | vp09.00.20.08 221k video only Untested, IOS-D 242 webm 426x240 24 | 17.28MiB 132k https | vp9 132k video only 240p, ANDR-V, webm_dash 395 mp4 426x240 24 | 16.42MiB 126k https | av01.0.00M.08 126k video only 240p, ANDR-V, mp4_dash 230 mp4 640x360 24 | ~ 95.31MiB 731k m3u8 | avc1.4D401E 731k video only Untested, IOS-D 134 mp4 640x360 24 | 36.77MiB 282k https | avc1.4d401e 282k video only 360p, ANDR-V, mp4_dash 18 mp4 640x360 24 2 | 78.17MiB 599k https | avc1.42001E mp4a.40.2 44k [en] 360p, ANDR-V 605 mp4 640x360 24 | ~ 68.00MiB 521k m3u8 | vp09.00.21.08 521k video only Untested, IOS-D 243 webm 640x360 24 | 37.60MiB 288k https | vp9 288k video only 360p, ANDR-V, webm_dash 396 mp4 640x360 24 | 29.57MiB 227k https | av01.0.01M.08 227k video only 360p, ANDR-V, mp4_dash 231 mp4 854x480 24 | ~136.31MiB 1045k m3u8 | avc1.4D401E 1045k video only Untested, IOS-D 135 mp4 854x480 24 | 69.02MiB 529k https | avc1.4d401e 529k video only 480p, ANDR-V, mp4_dash 606 mp4 854x480 24 | ~ 99.78MiB 765k m3u8 | vp09.00.30.08 765k video only Untested, IOS-D 244 webm 854x480 24 | 57.32MiB 440k https | vp9 440k video only 480p, ANDR-V, webm_dash 397 mp4 854x480 24 | 51.08MiB 392k https | av01.0.04M.08 392k video only 480p, ANDR-V, mp4_dash 232 mp4 1280x720 24 | ~185.82MiB 1425k m3u8 | avc1.4D401F 1425k video only Untested, IOS-D 136 mp4 1280x720 24 | 127.01MiB 974k https | avc1.4d401f 974k video only 720p, ANDR-V, mp4_dash 609 mp4 1280x720 24 | ~181.16MiB 1389k m3u8 | vp09.00.31.08 1389k video only Untested, IOS-D 247 webm 1280x720 24 | 106.76MiB 819k https | vp9 819k video only 720p, ANDR-V, webm_dash 398 mp4 1280x720 24 | 89.03MiB 683k https | av01.0.05M.08 683k video only 720p, ANDR-V, mp4_dash 270 mp4 1920x1080 24 | ~611.50MiB 4689k m3u8 | avc1.640028 4689k video only Untested, IOS-D 137 mp4 1920x1080 24 | 307.65MiB 2359k https | avc1.640028 2359k video only 1080p, ANDR-V, mp4_dash 614 mp4 1920x1080 24 | ~304.82MiB 2337k m3u8 | vp09.00.40.08 2337k video only Untested, IOS-D 248 webm 1920x1080 24 | 175.33MiB 1344k https | vp9 1344k video only 1080p, ANDR-V, webm_dash 399 mp4 1920x1080 24 | 161.10MiB 1235k https | av01.0.08M.08 1235k video only 1080p, ANDR-V, mp4_dash 620 mp4 2560x1440 24 | ~ 1.20GiB 9395k m3u8 | vp09.00.50.08 9395k video only Untested, IOS-D 271 webm 2560x1440 24 | 613.49MiB 4704k https | vp9 4704k video only 1440p, ANDR-V, webm_dash 400 mp4 2560x1440 24 | 513.02MiB 3934k https | av01.0.12M.08 3934k video only 1440p, ANDR-V, mp4_dash 625 mp4 3840x2160 24 | ~ 2.39GiB 18784k m3u8 | vp09.00.50.08 18784k video only Untested, IOS-D 313 webm 3840x2160 24 | 1.56GiB 12253k https | vp9 12253k video only 2160p, ANDR-V, webm_dash 401 mp4 3840x2160 24 | 948.58MiB 7273k https | av01.0.12M.08 7273k video only 2160p, ANDR-V, mp4_dash and then: yt-dlp -f 232+234 -N 2 "cnX5zJ_qGz0" => [youtube] Extracting URL: cnX5zJ_qGz0 [youtube] cnX5zJ_qGz0: Downloading webpage WARNING: [youtube] No supported JavaScript runtime could be found. Only deno is enabled by default; to use another runtime add --js-runtimes RUNTIME[:PATH] to your command/config. YouTube extraction without a JS runtime has been deprecated, and some formats may be missing. See https://github.com/yt-dlp/yt-dlp/wiki/EJS for details on installing one [youtube] cnX5zJ_qGz0: Downloading android vr player API JSON [youtube] cnX5zJ_qGz0: Downloading ios downgraded player API JSON [youtube] cnX5zJ_qGz0: Downloading m3u8 information [info] Testing format 232 [info] Testing format 234 [info] cnX5zJ_qGz0: Downloading 1 format(s): 232+234 [hlsnative] Downloading m3u8 manifest [hlsnative] Total fragments: 189 [download] Destination: Your RAM Is Fake. The Moon Broke Timezones. And Your Compiler Is Guessing. [cnX5zJ_qGz0].f232.mp4 [download] 100% of 132.64MiB in 00:03:59 at 567.14KiB/s [hlsnative] Downloading m3u8 manifest [hlsnative] Total fragments: 189 [download] Destination: Your RAM Is Fake. The Moon Broke Timezones. And Your Compiler Is Guessing. [cnX5zJ_qGz0].f234.mp4 [download] 100% of 17.02MiB in 00:00:44 at 393.03KiB/s [Merger] Merging formats into "Your RAM Is Fake. The Moon Broke Timezones. And Your Compiler Is Guessing. [cnX5zJ_qGz0].mp4" Deleting original file Your RAM Is Fake. The Moon Broke Timezones. And Your Compiler Is Guessing. [cnX5zJ_qGz0].f234.mp4 (pass -k to keep) Deleting original file Your RAM Is Fake. The Moon Broke Timezones. And Your Compiler Is Guessing. [cnX5zJ_qGz0].f232.mp4 (pass -k to keep)

not very "every week" now as upstream doesn't as active as before.

Re: Forcibly reinstalling uBO, I agree with NHTPG. Unfortunately the author appears to have missed the point: Re: the first point, I would too! On today's Internet, I'd never browse without an ad blocker, and uBO is the best IMO. But there's a difference between installing uBO by default, and reinstalling it if the user intentionally uninstalls it, effectively making it an unavoidable part of the browser! I don't think the author fully appreciates the gravity of forcibly installing a third-party's add-on, no matter how good that third party may currently be. What if some hypothetical company (which I'll call "Poogle") makes gorhill an offer he can't refuse to exempt Poogle ads from being blocked by uBO? Or what if gorhill gets hit by a truck, and his heirs aren't software developers, have no interest in continuing uBO development, and just sell it to Poogle outright? (As for having uBO always available when testing, the author could add it to his own policies.json; that doesn't mean it has to be in the distribution for everyone.) As to the second point, editing a .json file is a bit beyond the ability of the average user. There needs to be a way for non-techies to do this. But in any case, it appears the author has no intention of addressing this issue.

Palemoon win64, basilisk win64, xp64 Table does not load, only the inscription "loading" is displayed and we wait indefinitely e.g. https://www.sejm.gov.pl/Sejm10.nsf/Glosowanie.xsp?posiedzenie=49&glosowanie=1 https://www.sejm.gov.pl/Sejm10.nsf/Glosowanie.xsp?posiedzenie=51&glosowanie=1

I seem to recall that the developer has publicly asked for assistance and nobody stepped up to the plate. Granted, at the time, that request was in reference to XP/Vista support. The userbase (my opinion) has grown INCREASINGLY impatient with the "release schedule". You can find Reddit posts asking if r3dfox is "abandoned" if it goes so much as ONE MONTH without a new release. ONE MONTH !!! There are also requests for NIGHTLY BUILDS !!! And every time a Firefox ESR "security bulletin" is posted, the board jumps to life BEGGING for an update. Begging, Begging, Begging! Personally, in my humble opion, this is where A.I. should become everybody's "best friend". The compile process takes roughly 1/2hr and while that may not sound like much, most everybody does have LIVES. Not everybody is a "robot / machine" dedicatingly programmed into a "ritual" of posting software updates each and every week. Let's be honest, not many of us are WILLING to dedicate the amount of TIME out of our LIVES that folks like @roytam1 does every week! A.I. could do all of this for us! And we'd have that "nightly" version of r3dfox. If a young programmer wants to "make a name" for him/herself, the INSTRUCTIONS on how to build r3dfox is publicly posted. No takers so far! We can all read into that what we will.

Does this also happen with the latest release?

not really, just I don't install latest certstore here. you can see the analysis here: https://www.ssllabs.com/ssltest/analyze.html?d=msfn.org

... Well, why? 1. 32-bit apps run perfectly fine on a 64-bit OS 2. Do you expect a huge performance boost if you ran a 64-bit variant of yt-dlp ? Well, this app isn't, say, a browser with a voracious RAM appetite; I've been using it on a 32-bit OS myself for close to a decade, never ran into memory issues... 3. The one practical advantage of running it under 64-bit, the ability to install the curl_cffi optional dependency (necessary to circumvent CloudFlare's antibot/AI filters on many popular services) is nullified under WinXP, because the lib it uses internally (curl-impersonate) requires at least Win7(8?) x64 ... In any case, this is probably a "no-can-do", because @nicolaasjan relies on a third-party CPython-3.11-win32 implementation to compile his 32-bit WinXP-compatible builds; specifically, this was a py3.11.4 "assembly" kindly offered by our Ukrainian member cmalex , which uses several DLL wrappers from OCA/Wine/ReactOS and it was provided solely as a 32-bit variant (which should cover probably 95% of XP users ) ... Regards.

No new Easter egg from me! Either I've been just a bit too careless while writing and correcting or it is due to a kind of senility! Thanks for reporting again! I'll correct that immediately, of course! No, the fixed version of cacert Updater can be downloaded from first post in my thread in section Downloads: The changes are minor indeed and can be done simply by applying cacert Updater Fixed. BTW the AIO package has been created by @Windows7fan from MDL. Therefore maintaining of it isn't my job. And I totally agree, if actions are performed manually, users get full control because one knows what has been done and what has to be performed next. Very important if verifying of each step is necessary.

That would be great! In the case of publishing I will mention you for html creation, of course. I have a lot of respect for people doing things manually especially using programming languages like HTML4 and CSS. Once again, my honest respect! Nowadays I am more a batch programmer, more often a person modifying and fixing files, although I did more smaller projects in the past when I was much younger. Especially mathematical ones. But for now, kindest regards, AstroSkipper

As I wrote in my guide, everything can be done manually. That's how I did it. By doing things manually you have full control of what you do and verifying is much more easier. Here is the changelog to AIO Update version 1.2.1: "Version 1.2.1 3/6/22: Updated cacert.pem to the latest version. This improves compatibility with most websites including Windows Update." This is a quotation taken from MDL.

I am so sorry! Truth to be told I really thought you are female because of your name Mina (read in forum "Introduce Yourself!") meaning "heaven". Once again, I have to apologize to you! Do not be angry! Appearently I am not a Sherlock Holmes. Wow! You are the only one who has found my easter egg! That means you have really read my guide carefully! Thanks for reporting! Good luck! Hope it will work this time! Kind regards, AstroSkipper

Thanks for your point of view! English isn't my native language too, I am German. But I try to do my best in writing. And truth to be told there is an option called "Google Translator", therefore bad language skills are no acceptable reason to write in poor English strings. Or isn't it?

Hi @maile3241 What do you think about people asking for assistance but being too lazy or whatever in writing reasonable posts? I don't understand that and it annoys me. We all do that to help other people just for fun. But in these cases there is no fun! Apart from that, it is also a question of respect and that's really lacking in some cases, in my opinion!

Too less information and posting of one sentence comment again! The next one I will ignore! I looked into your log. You had and have a lot of problems relating to your Windows Update client. Do carefully following steps of my guide again: 9, 10 and 11. Steps 14 and 15 only if necessary as described in my guide. And I'm serious, no more one sentence comments with nonsufficient information! "here is the log" is nothing! The next one I will ignore definitely! A complete screenshot of ProxHTTPSProxy's log window while accessing MU only (no other connections to whereever) plus information about your system and what you have done so far, are missing too.

Sorry, no! Truth to be told it's not really ok. In an very old OS you are using a very old unsupported version of IE6 and an unsecure version of ProxHTTPSProxyMII due to lacking of SHA256 capability of signing. Just for fun on some very safe sites for testing purpose only, it's ok. But for more it's just a no go. In this case you need a more recent and secure browser which supports Windows 2000. But anyway, congrats for restoring access to MU web site! The impossible is possible as you can see!

You are using an unsecure proxy version. ProxHTTPSProxyMII 1.3a (20150527) should only be used to access MU. For surfing you need a more secure browser. For more information about these proxies you can read my article:

If you want to disable SFC in future times, you have to do in this way: https://www.neowin.net/forum/topic/85098-how-2-disable-windows-2000-sp3s-file-protection/?do=findComment&comment=996683 There are a lot of those guides in the WWW.