davidz

Jeez, it turns out that now, for version <yt-dlp_x86_winXP_2025.12.06> to work, you need this “junk” — <Microsoft Visual C++ 2019>, which has to be placed in the same folder! Since I have no intention of polluting my system with that crap, I just copied all the missing files directly into the folder with <yt-dlp_x86_winXP.exe> But here’s another question: why did version <yt-dlp_x86_winXP_2025.11.25> work perfectly fine without those extra DLLs? After all, those files are already embedded inside <yt-dlp_x86_winXP.exe>, and when unpacked, everything gets extracted into the TEMP folder anyway! So what’s the point of this “duplication” now?

Yes, I confirm: version yt-dlp_x86_winXP.exe (2025.12.06.064237) does not work on Windows XP SP3! Version 2025.11.25.144622 worked fine!

Are you also planning to switch to Python 3.13.7 for Windows XP (yt-dlp_x86_winXP.exe)?

checked 20241123's changes but no idea what breaks it So, it's useless to ask Moonchild(in upstream), considering that he is an ardent opponent of the multiprocess feature in UPX-browsers? And we'll have to put up with this bug?

Hello roytam1! In basilisk52-g4.8.win32-git-20250315 - when the multiprocess option is enabled, the 'Page Source Code' view doesn't work. (This only works in single process mode.) The problem started with the version basilisk52-g4.8.win32-git-20241123! Before that, on basilisk52-g4.8.win32-git-20241116 - everything worked fine. Steps to reproduce the problem: browser.tabs.remote.autostart", true browser.tabs.remote.force-enable", true dom.ipc.processCount", 6 When clicking on the 'View Page Source' item in the context menu, a blank page is displayed. An error is displayed in the browser console(Ctrl+Shift+J): TypeError: contentWindow is null — viewSource-content.js:226:11 Please fix this problem.