Leaderboard

SAB 3.9.15

StartAllBack 3.9.14 StartAllBack 3.9.13

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250823-3219d2d-uxp-e5ea29554a-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250823-3219d2d-uxp-e5ea29554a-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250823-3219d2d-uxp-e5ea29554a-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250823-d849524bd-uxp-e5ea29554a-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250823-d849524bd-uxp-e5ea29554a-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250823-d849524bd-uxp-e5ea29554a-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250823-d849524bd-uxp-e5ea29554a-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250823-d849524bd-uxp-e5ea29554a-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2837 - Implement `prefers-reduced-motion` media query. (df3b213459) - Issue #1899 - Remove MDN docs tooltip and link code from devtools. (842cc60707) - Issue #1843 - Clean up WindowsVersion.h (7af71cb345) - Issue #2847 - Extend `-moz-os-version` media query with win11. (723180132d) - Issue #2258 - Part 1: Support XCTO:nosniff when navigating. (e56e5d6cb1) - Issue #2258 - Part 2: Move XCTO:nosniff check into sniffers. (cca20ae131) - Issue #2258 - Part 3: Allow sniffing with XCTO:nosniff + empty MIME type. (707c3e3fa8) - Issue #2258 - Part 4: Clean up unused pointers. (bd734f795c) - Bug 1875345 - Report 24 instead of 32 as the colorDepth (and pixelDepth) on Linux (assuming 8 of 32 bits are for the alpha channel). (e3de626c1f) - Issue #2850 - Alias `:focus-visible` to `:-moz-focusring` (6d47d819fa) - [gfx] Guard against possible race via gfxFontEntry::GetFontTable. (7cadc57d49) - [js] Error-check pthread calls (425f38ff84) - [NSS] Avoid leak in pkcs12 decoder. (fe21538da4) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - nss: update certdata and bump ckbi version to 2.80 - Bug 1974511 - Add SwissSign 2022 Roots to NSS r=jschanck - Bug 1972391 - Add TrustAsia Dedicated Roots to NSS r=jschanck - Bug 1961848 - Remove expired Baltimore CyberTrust Root r=jschanck - Bug 1978677 - remove expired explicitly distrusted DigiNotar lookalike root r=nss-reviewers,jschanck (f5307ea861) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Info: On GitHub, the names and download links of yt-dlp for Windows XP have changed: yt-dlp_x86_Windows-XP.zip > yt-dlp_x86_winXP.exe (starting after the next release, it should be able to update with `yt-dlp -U` ) yt-dlp_x86_Windows-XP_onedir.zip > yt-dlp_x86_winXP.zip Direct links: https://github.com/nicolaasjan/yt-dlp/releases/latest/download/yt-dlp_x86_winXP.exe https://github.com/nicolaasjan/yt-dlp/releases/latest/download/yt-dlp_x86_winXP.zip For Windows Vista, new update here.

First, welcome to the MSFN forums ; I take it you are using FirefoxESR-115, now on v115.27.0esr, supposedly to be EoL'ed on Win7/8.1 with the next, last, release v115.28.0esr ... Do you, by any chance, have uBlock Origin installed in your FxESR-115 profile? If yes, there's a way you can continue accessing the full version of Discourse-based forums in FxESR-115; read this post ; basically, you'd have to create below custom filter: ! Discourse-based forums ||*/browser-detect-$script,important uBO -> dashboard -> My Filters -> add above code -> Apply changes (header of tab) -> exit dashboard then delete discourse-forum cookies (for good measure) and reload the forum page... Can you please be more specific? Which version is that exactly? Help -> About r3dfox -> ? r3dfox has recently moved into a new GitHub repo, with new Releases section ... I'll assume you currently are in v140.0.4 (not the latest, BTW) ... Did you just transplant/migrate your full FxESR-115 profile to r3dfox-140 ? Although r3dfox is Firefox-based, such big jumps between major versions are prone to profile corruption ... I would advise you start from a clean redfox profile and then, progressively, tailor it to your own needs (settings, extensions, importing bookmarks from FxESR-115, etc.) ... In FxESR-115, load about:logins (Password Manager); click the 3-dot-button (top-right) and you should see a context option to "Export Passwords"; this will save ALL your login credentials to a CSV file; via a similar, but now reverse, procedure, you can import this CSV file to r3dfox and have all your passwords restored! (Take good care of that CSV file, as it contains the passwords in unencrypted, human-readable, form). Best regards ...

New root certificates (4) from 28. 08. 2025. Edit: Corrected the date from 25. to 28. aug.

... No, they don't ; Discourse are serving a browser-feature detection script (believe it or not, this is actually the recommended way to probe a browser engine, rather than blindly block it based on its UA string) and they're looking for these features: https://arkshine.github.io/discourse-features-test/ (NB: Their announcement was recently edited to also cover "import maps" (Cr89+, Fx108+)) In a nutshell, they're dropping support for Win7/8.1 , where the last Cr and Fx supported versions are 109 and 115esr, respectively... ... Please do ; the posted custom filter blocks Discourse's browser-checking script, so your browser (FxESR-115) will be served the full-blown variant of the Discourse-based forum of interest; please be aware that while this hack currently works, it's not future proof; in, say, 6 months' time, one of the browser features they're checking for might end up in production, hence one (or more) forum function might break, to some extent ... That's the way to go , though it doesn't offer any additional clue as to why all but one of your existing logins were mysteriously removed ... Glad to know and... you're welcome ... Saluti !

28.08.2025 it says for me. Thanks!

Whew! ESR v140.20 has been released. Yay! And the latest release for the mainstream versions is v141.0.3 https://github.com/Eclipse-Community/r3dfox/releases

For the Vista lovers 😽 : yt-dlp_Py3.11_Vista.7z (password: 987123). Updated today. (the XP version does not work on Vista)

... Probably not, so let me summarise the gist of what @j7n was talking about in his recent posts: 1. The H.264 codec is probably the best choice when you're about to playback video on a system with low H/W resources (weak CPU, low-end GPU) and a legacy OS like Win7 SP1; the decoder is natively supported by the OS (not the case in XP SP3) and via implementations like WMF/MSE, an MP4 video can be played back within a compatible browser with hardware acceleration and hardware decoding (not the same things); most Win7-era graphics cards have H.264 decoding support built-in, so even when the MP4 video is being played back in a standalone media player, video decoding is performed by the GPU, not CPU... 2. Google have recently started producing their h.264 (aka avc1) youtube encodes at very low video bitrates, even for "high" resolutions, such as 720p/1080p; thus, while the h.264 YT encodes should be preferred for downloading (because they need less computer resources to be played back once downloaded), the stingy bitrate results in sub-optimal visual experiences (blurry moving images, video artifacts of various sorts, etc.). 3. OTOH, Google continue to produce their VP9 YT encodes at exceptional bitrates, especially for the FHD/UHD resolutions (>=720p); these are large files to download, to begin with, but, once downloaded, playback on low-end machines puts a heavy toll on the CPU, because VP9 is being software-decoded; I've not researched this properly, but graphics cards with integrated, native, VP9 decoding support (aka VP9 hardware decoding) only came in the later 2010s, as part of mostly Win10 machines... TL;DR: To have the best visual experience, j7n has to fetch the VP9 YT encodes, but these are detrimental to his under-resourced machine (mostly the CPU is being utilised for video playback, resulting in excess heat and energy consumption, etc.).

Supermium's password manager is working fine for me, and always has done. It is backed up to the cloud by Google Sync, so it's synchronised with my other Supermium installations on other machines, (I know, I know, but it works for me, and I don't use it for any really sensitive passwords like online banking!) I back up my whole machine locally regularly as well, of course.

I did just discover that the paypal slide mouse screen in my older version of Serpent is DEPENDENT UPON the ISP that I use. I canceled my previous ISP but it remains active until the end of my billing cycle (I only have two more days) - I get no slide mouse screen in Serpent when connected via my previous ISP (cable). I *DO* get the slide mouse in Serpent (unsolvable - checkbox turns green but page does NOT advance) in Serpent when connected via my new ISP (fiber optic).

The browser I was using was Roytam1 Newmoon28-sse browser it is recent build 2025-08-08 I will update it and a;so try with other browsers. I see a file that is maybe it's a base64 orientated which cold have all the pictures. Now understand for your thinking all the pictures should be there and showing. As the web page did download completely. After updating and trying with other browsers if I am still getting the same results I will let Roytam1 know in his thread my-browser-builds-part-5 Thanks for the info Tripredacus

Greetings :-) Thanks. Updated Python3.11.4_openssl3.5.2.zip PS. Why don't You include openssl.exe in the set? Best regards

Hello Reino (OT, but I'm really missing your Vista-compatible FFmpeg compiles ) While your OpenSSL binaries (archive "openssl-3.5.2-win32-shared-xpmod-sse.7z") may very well be XP+ compatible , they don't work out-of-the box as CPython dependency by swapping the already existing DLLs (of openssl v3.1.0-dev) inside cmalex's CPython assemblies with them; he's been using the same (quite deprecated and now rather insecure ) v3.1.0-dev DLLs in his 3.8.13, 3.9.13, 3.10.8 and 3.11.4 CPython offerings, but the thing is the libcrypto-3.dll and libssl-3.dll inside CPython work in conjunction with two Python DLLs, files "_ssl.pyd" and (possibly) "_hashlib.pyd"; the existing .pyd files are incompatible with your own openssl DLLs ... BTW, I'm on Vista SP2 32-bit, so I'm using cmalex's Vista-compatible 3.11.4 assembly; with the original v3.1.0-dev DLLs: python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl >>> ssl.OPENSSL_VERSION 'OpenSSL 3.1.0-dev ' >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> Overwrite them with your own v3.5.2 DLLs and... python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl Traceback (most recent call last): File "<stdin>", line 1, in <module> File "<redacted>\3.11.4\cmalex\Python3114-32_Vista>\Lib\ssl.py", line 100, in <module> import _ssl # if we can't import it, let the error propagate ^^^^^^^^^^^ ImportError: DLL load failed while importing _ssl: The specified procedure could not be found. >>> ssl.OPENSSL_VERSION Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'ssl' is not defined >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> I guess newer versions of "_ssl.pyd" and "_hashlib.pyd" must be provided for openssl-3.5.2 compatibility ... @nicolaasjan openssl-3.1.0-dev inside cmalex's assemblies (both 3.10.18 and 3.11.4, both XP/Vista variants) can be updated to a slightly more recent version, openssl-3.1.2, by using the OpenSSL-3.1.2 DLLs cmalex had compiled in the past for another of his projects, ProxyMII; link below: https://mega.nz/folder/68dj2YTY#As2w31IO4Smr7gy6p1ciSg/file/Pl9yzapZ Proof: python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl >>> ssl.OPENSSL_VERSION 'OpenSSL 3.1.2 1 Aug 2023' >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> NB: When using the Vista variants of py3.10.18/3.11.4 to compile yt-dlp_x86.exe for Vista, none of the wrapper DLLs (kernelxp.dll, ntext.dll, psapi.dll) are needed; because your resultant yt-dlp.exe binaries (for Vista) still contain file "psapi.dll", redundant on Vista ; come to think of it, I don't think file "ws2_xx.dll" is needed on Vista either, but I'm not dead certain; only cmalex can vouch for that ... Many thanks and praise to both cmalex and nicolaasjan for... keeping the torch lit (i.e. yt-dlp accessible on Win<8.1) ...

Greetings Python3.11.4.zip in https://mega.nz/folder/jst2WJ5B#sknEpEBamwPomx8UULWuMA Please any questions about it at https://msfn.org/board/topic/183741-python-3813-for-windows-xp-sp3/ Best regards

Discourse? On MyPal? Seriously?

I've made the uBO-legacy custom filter even more generic, because I've come across Discourse-based forums where the browser detecting script wasn't served from within an "assets" subfolder ; so, the version I'm currently using is: ! Discourse-based forums ||*/browser-detect-$script,important The now broken userscript just told Discourse's browser-feature-detection script that "CSS aspect-ratio (Fx-89+)" IS supported in UXP-based browsers; maybe Discourse are now looking for something new entirely or, besides CSS aspect-ratio, for additional (recent) features that the userscript (and, alas, UXP) doesn't support... A very savvy person would have to dissect the new version of Discourse's script, identify what new things they search for now and author a new userscript... Discourse, in March, issued the following announcement: https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131 so it's probably one or more of the new requirements there that broke things; FWIW, relative color syntax & subgrid aren't supported in UXP, probably the same applies to import-maps ... Recent upstream forum thread about Discourse's shenanigans : https://forum.palemoon.org/viewtopic.php?f=70&t=32600 Last post there is from Aug 13th, though...

Slight correction: Vista+ only, for quite some time now ... https://github.com/Eclipse-Community/r3dfox

Mozilla extended ESR v115 for 6 more months. Further extensions are also possible. https://msfn.org/board/topic/181987-list-of-software-that-doesnt-support-windows-7/page/34/#findComment-1281886

I have not been following the back-and-forth on PayPal "slide mouse". I can only report that it DOES WORK on first attempt in my OLDER version of Serpent.

Can the old navigation pane be brought back?

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20250823-69d606e5d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250823-69d606e5d-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #2837 - Implement `prefers-reduced-motion` media query. (df3b2134) (796fbddde) - ported from UXP: Issue #1899 - Remove MDN docs tooltip and link code from devtools. (842cc607) (748599a3f) - ported from UXP: Issue #1843 - Clean up WindowsVersion.h (7af71cb3) (513b16251) - import from UXP: Issue #2847 - Extend `-moz-os-version` media query with win11. (72318013) (721e8343a) - ported from UXP: Issue #2258 - Part 1: Support XCTO:nosniff when navigating. (e56e5d6c) (7c405cfe3) - import from UXP: Issue #2258 - Part 2: Move XCTO:nosniff check into sniffers. (cca20ae1) (fb7674759) - import from UXP: Issue #2258 - Part 3: Allow sniffing with XCTO:nosniff + empty MIME type. (707c3e3f) (d1fd2e3b3) - import from UXP: Issue #2258 - Part 4: Clean up unused pointers. (bd734f79) (a3d299d64) - import from UXP: Bug 1875345 - Report 24 instead of 32 as the colorDepth (and pixelDepth) on Linux (assuming 8 of 32 bits are for the alpha channel). (e3de626c) (780aa8768) - import from UXP: Issue #2850 - Alias `:focus-visible` to `:-moz-focusring` (6d47d819) (98b67440c) - nss: update certdata and bump ckbi version to 2.80 - Bug 1974511 - Add SwissSign 2022 Roots to NSS r=jschanck - Bug 1972391 - Add TrustAsia Dedicated Roots to NSS r=jschanck - Bug 1961848 - Remove expired Baltimore CyberTrust Root r=jschanck - Bug 1978677 - remove expired explicitly distrusted DigiNotar lookalike root r=nss-reviewers,jschanck (9815f4533) - import from UXP: [gfx] Guard against possible race via gfxFontEntry::GetFontTable. (7cadc57d) (5748e6157) - import from UXP: [js] Error-check pthread calls (425f38ff) (2bf79a7ff) - import from UXP: [NSS] Avoid leak in pkcs12 decoder. (fe21538d) (69d606e5d)

So did I now: https://developer.paypal.com/tools/sandbox/ so probably NOT what you're after ; if you're limited to using UXP-based browsers (on Windows XP SP3?), then am afraid they're now dead in the water with regards to PayPal; the issue needs to be escalated upstream by users of the "official" UXP browsers (Pale Moon and Basilisk, on Win7SP1+), in the hope upstream can come up with a solution, but the relevant PMForum thread hasn't seen any further activity since July 30th... OT for this thread, but you may also appeal for help to Feodor2 in MyPal's GitHub issue tracker ; if still on XP, you might try how the Supermium browser fares on PayPal these days; might prove your only recourse...

YouTube has something new on their end again. No mention of SABR at all anymore. There is new line in the app that says "Sleeping for 5 seconds as required by the site." No big deal about that. Requesting 720p or 1080p h.264 video gives extremely poor quality compared to how it was before. The bitrates for a talking head segment are 240 kbit/s and 860 kbit/s respectively. Requesting no/default format gives VP9 in extremely large size and demand for the computer. Best that they have 3840*2160 @ 30 fps, 9500 kbit/s. Google really wants to push their VP9. When nothing works, this still does.

...It wasn't working for him, but now it is : PS: The forum software doesn't send a second (e-mail) notification to thread-subscribed members after one has edited one's original post (for which an initial notification has already been sent) ... Browser profile corruption is always a possibility, so, as others have noted, regular profile back-up and back-up of important info on physical copies is always strongly recommended ... ... Probably NOT ...

@Dave-H Maybe your Internet Explorer installation is faulty. Just a guess!

Here the DNS servers I suggested: Google Public DNS. 8.8.8.8. 8.8.4.4. and Cloudflare. 1.1.1.1. 1.0.0.1. Try them! And here's another fix referring to error code 0x80072f8f I have found while researching: Open in a registry editor the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\LastRestorePointSetTime. Here you can see a date and a time (that's my idea to find a suitable point in time). Now go back to this date and time plus for example one hour. Try to access MU. Reboot. Then adjust clock to current date and time. Do a synchronization. Reboot. Then try again! The idea is to go back in time to the last successful update on MU web site and try to access the MU server. Some people had success with turning back time to solve error code 0x80072f8f. And here a screenshot of my Internet Options - Advanced referring to HTTP settings: https://imgur.com/EHW7rix

@Dave-H Ok, thanks for further details! I have compared our lists of certificates intently. If you had compared our lists of certificates intently too you would have realized that only one of them is identical. And that is the list of certificates referring to Microsoft in Third Party Root Certification Authorities. But in my list of Intermediate Certification Authorities I have 8 certificates referring to Microsoft and you only 3. Have a look! That's a big difference. If wanted I can upload these missing certificates via PM so that you can import them under Intermediate Certification Authorities. As I told you two posts above expired certificates can still be required and in use too. At last I have analyzed your Windows Update Log once again. Here the interesting lines: 2022-02-01 22:53:27:781 1856 9b0 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2022-02-01 22:53:27:781 1856 9b0 PT + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx 2022-02-01 22:53:28:796 1856 9b0 Misc WARNING: Send failed with hr = 80072f8f. 2022-02-01 22:53:28:796 1856 9b0 Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <https=localhost:8080> Bypass List used : <<local>> Auth Schemes used : <> 2022-02-01 22:53:28:796 1856 9b0 PT + Last proxy send request failed with hr = 0x80072F8F, HTTP status code = 0 . . . 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: GetConfig failure, error = 0x80072F8F, soap client error = 5, soap error code = 0, HTTP status code = 200 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: PTError: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: GetConfig_WithRecovery failed: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: RefreshConfig failed: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: RefreshPTState failed: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: Sync of Updates: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 PT WARNING: SyncServerUpdatesInternal failed: 0x80072f8f 2022-02-01 22:53:28:796 1856 9b0 Agent * WARNING: Failed to synchronize, error = 0x80072F8F 2022-02-01 22:53:28:796 1856 9b0 Agent * WARNING: Exit code = 0x80072F8F As we already know Microsoft Update 0x80072f8f error code means ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong. What does it really imply in your case? You can see it in your Windows Update Log. Look at bold text! A client fails to contact its server. In your case client is your computer and server is Microsoft Update Server. Request sent from your computer to MU failed. Synchronizing of client and server failed. Getting configurations failed. That' your problem. What is the conclusion? The connection and synchronization failures between client and server have to be fixed. At first we have to think about what we've already restored and fixed. The Windows Update Agent looks fine and you have reported that all steps of my post "Manually reset Windows Update components (KB971058)" have been performed: Have you performed step 4 too or have you skipped it as recommended? If you skipped step 4 then it should be catched up. Furthermore I added another registering of a DLL component: in step 6: Perform this registering to complete step 6. Now some settimgs: Go to IE Internet Options, Advanced and click to select the Use HTTP 1.1 and the Use HTTP 1.1 through proxy connections check boxes if not already selected. Next check if system service HTTP-SSL has system been started. If not start it and set it to Auto Start. Now reboot your computer, try to access MU again and post your Windows Update Log. If these tips don't solve the problem I have another one: Change your DNS servers to Cloudflare or Google and check if it helped. I use often DNS servers of Cloudflare but at the moment the servers of my provider. So far from me today!

@Dave-H I've read an interesting article of a person who had same error code and the solution was a missing certificate in a chain of certificates. Check if following certificate exists under Trusted Root Certification Authorities: GTE CyberTrust Global Root valid until 14.08.2018. I know it has expired but I've read that such expired certificates can still be in use. It's just a try. Furthermore I've found another tip that obviously others had helped: And one more question: Do you have a normal installation of XP or are you running it in a VM? Is your computer a clent or server in a network or a stand-alone one?

@Dave-H Yesterday I had trouble to access Google and other web sites using HTTPSProxy. What had happened? I checked and found out that HTTPSProxy's cacert.pem was faulty. I downloaded a new one manually from this link https://curl.se/ca/cacert.pem and copied it in HTTPSProxy's program folder. I deleted all certificates in certs folder and after starting the proxy I could access all sites without any problems. Updating cacert.pem in SysTray menu is working again. So what is the teaching of that? You have to check and deeply too. Comparing two files only due to size and date is not enough. A binary comparison is necessary or comparing hash values. You can do it for example with Total Commander. So download a fresh cacert.pem from link above and compare it to yours just to be sure your certs are valid and proper in your HTTPSProxy's program folder. Here is a screenshot of my Intermediate Certificate Authorities (there are Microsoft related certificates too): https://imgur.com/G2ogHnj I don't know if they are relevant, they seem to be expired. And here my Third Party Root Certificate Authorities: https://imgur.com/vY3dnq8 What is your current time server? And please upload a new WindowsUpdate.log! Maybe something has changed. A lot of Windows users have reported getting error code 0x80072f8f due to activation problems. So my next question. Is your Windows XP Professional properly activated? Do you have Windows Genuine Advantage (WGA) Validation Tool installed and what is your version? As far as I know the latest version for XP is 1.9.40.0. And I know a lot of questions. Sorry!

@Dave-H Here two screenshots how HTTPSProxy has to look if it is switched on: https://imgur.com/UhVxB46 https://imgur.com/t1dtyPZ Does it look like that?

Try it! And clear SSL cache and personal information once again! And I can't read your WindowsUpdate.log. Check it and upload it again! There is something misconfigured either in config.ini (do you use my provided config.ini for HTTPSProxy?) or in IE. Why is your WindowsUpdate.log unreadable? p.s.: Use a taskmanager to check if nothing interferes your connection to MU. I use Process Hacker, in my opinion the best.

Just to clarify Microsoft Update Search doesn't work in your Windows XP system due to never ending process. Is that right?

In the past I had similar problems but thinking the search is forever never getting a result is in most cases wrong. Such searches can last more than an hour. But no one wants to wait for such a long time so they will be abandoned by user. My tip often helps to avoid such long searches.

Thanks for your tip! In my system no interfering or problems detected. By the way did my tip help you?

@Dave-H Fine. I've added my HTTPSProxy's config.ini so you can use that or compare it to yours. https://www.mediafire.com/file/6emtdvx2vmw4iz8/HTTPSProxy_-_config.ini/file

@Dave-H Of course there are differences. HTTPSProxy ran from the very first I tried to access MU without any problems. Configuring was very easy. ProxHTTPSProxy didn't run from the very first. I had a lot of trials to get it work. Configuring wasn't easy. I had certificate problems too. In HTTPSProxy the certificate management is much easier. Beyond that HTTPSProxy is more user-friendly compared to ProxHTTPSProxy and can be accessed in SysTray at any time incl. switching on and off. By the way did you try my attached ProxHTTPSProxy's config,ini in this post? For me it is working smoothly.

@Dave-H And if you still have problems to access MU you could give HTTPSProxy a try. You can install both on your machine they are portable but do not run both at same time i.e. they may not be executed in RAM at the same time otherwise they interfere. I don't know if I am allowed to upload HTTPSProxy due to the fact that @Thomas S. hasn't been here for a long time and he is the author. What do you think?

31st of December 2020 - works cool (even with disabled remote fonts), 1st of January 2021 - all hell breaks loose . It has nothing to do with the operating system. It's the new java , scripts and remote fonts. I'm glad it is working for the creator himself though. I've been away for some time , now logged in and everything works again , except the odd squares in the menus.

here's a good read for ya , from the respected member @sdfox7 https://msfn.org/board/topic/176837-disable-web-fonts-in-google-chromemozilla-firefox/

Golden words , like . The only minor thing left , explain it to many others on here , that use yandex [!] , yes living in United Kingdom , for example , and yet using yandex . As for me , I just block tons of china-russia IPs with firewall. The same goes to google, yahoo , etc.

I still have somewhere a windows-98 compatible Fujitsu motherboard from around 2006 and it was affected by this famous capacitor plague . Capacitor made by OST went bad (bulging, leaking) , blue coloured to be precise , near the RAM slots . I had to replace it with Philips capacitor Made in Holland , from the 1980s and it worked just fine.

This may be useful for anyone else using an older than normal Windows PC. Typically after at least a decade's use (my own experience is actually 12 years) the CMOS battery on a desktop PC's motherboard will start to fail. This is characterized by occasional then more frequent PC boots direct into the BIOS settings. Eventually it will fail completely and reset to the original MB BIOS and the default settings. The problem you may have is that even after you replace the battery and reflash the BIOS, so you're using exactly the same version, it still may not boot into Windows. In my case it got to the point the Windows 7 icon starts to appear then freezes. If you try the repair options you'll be offered Windows Diagnostic tools will report all OK but one error that can't be identified or fixed. This is can set you off on a totally unnecessary diagnostic and repair path which will waste your time and probably won't find let alone fix the actual cause. This is a very minor one BUT if you don't know about it you'll quickly be tempted to go through all those hoops. The cause is that with an older MB the 'optimized' default settings actually return the HDD addressing mode to IDE (Integrated Drive Electronics) when more modern SATA HDDs and SSDs require AHCI (Advanced Host Controller Interface). All you need to do is go into BIOS, find that setting. See the screenshot below for the location of this setting with older Gigabyte MBs. Swap it back to AHCI, save and reboot. You might get a Windows Diagnostic repair screen option first time but if you just choose to boot Windows normally - with any luck, it will. Hope this helps someone here avoid the hassle I went through trying to identify the cause of the boot failure after I had to replace the CMOS battery.

For my Py3.9 build on XP no version of PyInstaller after 5.13.2 works. So, I do: python -m pip install -U "setuptools>=71.0.2,<81" pip wheel pip install -U pyinstaller==5.13.2 -r requirements.txt Where `requirements.txt` is: mutagen pycryptodomex brotli; implementation_name=='cpython' certifi requests>=2.32.2,<3 urllib3>=1.26.17,<3 websockets>=13.0 O, that is the debug (--verbose) mode of yt-dlp itself.

Thanks for your quick reply! In this case bad news are good news for me. I already thought something was wrong with my system. On the other hand I would have been a little surprised too. Usually my system works like a charme. But as advertised I will try to fix that if I can, and I do hope so.

@WULover Use Onepiece's Update Pack French version called "OnePiece Windows XP Post-SP3 UpdatePack v1.0.9 FINAL FRA - (French)": https://www.wincert.net/forum/topic/12210-onepiece-xp-post-sp3-aio-international-update-packs-final/ It was last updated on 06/22/2017.

I strongly suggest to NOT use LED monitors . Get an old CCFL one. As for the LED lamps , also not good , but if you can't avid them , do not use cheap ones and get 2700K max. As for the eye , seeing a doctor is not an option ?