Leaderboard

... Where the exact same changelogs (as the ones posted here) are also printed just below the download links ... This has been conveyed/explained time and again: ALL major development, both upstream and here, takes place at the platform level (i.e. UXP) Upstream (platform): https://repo.palemoon.org/MoonchildProductions/UXP/commits/branch/master Upstream (application=Pale Moon) https://repo.palemoon.org/MoonchildProductions/Pale-Moon/commits/branch/master Upstream (application=Basilisk) https://repo.palemoon.org/Basilisk-Dev/Basilisk/commits/branch/master Roytam1 (custom branch - consists of cherry-picked development commits from upstream UXP+PM+Bk) https://github.com/roytam1/UXP/commits/custom I agree that most of the committed code is in "developer's speak", but if you make it a habit of quickly browsing over it every Saturday, you start understanding more as time goes on - in any case, "Enable WebComponents by default in the platform." is human-readable enough, isn't it... Upstream make official monthly releases, with announcements in their Forum, https://forum.palemoon.org/viewtopic.php?f=1&p=237830&#p237830 in their application code repo: https://repo.palemoon.org/MoonchildProductions/Pale-Moon/releases/tag/32.1.0_Release as well as in a dedicated Releases page in the PM site: https://www.palemoon.org/releasenotes.shtml OTOH, the development model of roytam1 is akin to a "nightly" release channel, with a weekly frequency of binary distributions - these are not tagged/"official" Roy releases, just "unstable/weekly" ones; the "norm" in such cases is to provide changelogs in the form of git-compare, e.g. : https://github.com/roytam1/UXP/compare/6f99b97...85f6a49 lists the source code changes between the latest UXP builds (by Roy) and the ones he released some 10 days ago... It's the way it has been for years... Of course I can be wrong, as much as anyone can ... And I'm not in the habit of "lying to myself", or to others, for that matter... In fact, being past 50 has taught me that it's telling the truth to others that will get me to trouble more often than not... I'm simply volunteering here, my free time is as precious as yours or anyone else's inside this community... Roy's making the hardest sacrifice to keep our old H/W and OSes usable by providing his browsers, I consider it a form of payback (to him) to occasionally offer "my services" here, with the deep knowledge I'm not "pleasant" to ALL readers... Best regards...

The latest Chromium 113 build runs on Windows 8.1.

Updated 360EE v9, v11, v12, v13, DCB, and both MiniBrowser browser's files. - Rebased chrome.dll (and chrome_child.dll where it applies) to address 0x10010000. non-rebased DLLs are kept just in case. https://archive.org/download/360EE_Modified_Version Cheers.

Agreed. Plus, "se" and "ee" are two different branches. 360Chrome has basically had three different v86 engines - 86.0.4195.1 86.0.4240.112 86.0.4240.198 As far as a true scientific quantitative approach goes - The .1 engines were the FASTEST. The .112 engines saw a very slight performance degradation. The .198 engines (everything newer than v13.0 build 2206 and all of the v13.5 builds) saw another very slight performance degradation.

I fear that many/most users here are not interested in reading these release notes, unfortunately. Only technically interested people, coders or developers will read or check these release notes in detail. And I agree it's a pity, of course. But this kind of disinterest and volatility is the way of things nowadays and can be observed in many situations, everything quick, quick, quick ... and reading? Too exhausting! Anyway! I do appreciate these additional information and am grateful to @roytam1 for his incredible effort and endeavour in all that he does.

Because they're commit logs comprehensible mostly to those involved in development. Most of those mean nothing to me either. Most people won't notice the effects of seemingly many changes behind-the-scenes, but they'll notice buggy/broken/slow rendering of certain web pages. I'd rather read a good book, though I'm indeed too exhausted. Maybe when I'm retired. Oh who am I kidding, we're going straight to the grawe! I'm sure he'd make a great technical support technician!

Avast v18.8 antivirus products are still getting virus definition updates. Here is a link where you can even download offline virus database updater called Avast VPS update: https://www.avast.com/download-update#pc Cheers, AstroSkipper

@Rod Steel and, possibly, many others : Please be kind enough to check below FAQ: i.e. TL;DR: If a certain "feature" (Web Compatibility-related, or otherwise) has made it onto an official Pale Moon (and/or Basilisk) "proper" release, then, in all probability, it's already extant in the Roytam1 UXP-forks preceding those "official" releases ... Notable exceptions: a) The "feature" breaks < Win7 compatibility in "our" forks, hence hasn't been included ... b) (related to "a)" in an indirect way:) The "feature" is currently incompatible with the compiler used to build the forks c) "Upstream" have updated their source code (platform and/or application) on a day after Saturday and have rushed a new binary release immediately after, before coming Saturday's scheduled releases by Roytam1 ; in that last, rare, case, wait for a few more days until the Roytam1 releases have been published in the known "outlets" ... And that concludes it, I hope ... Best wishes to all!

ESET, Bitdefender and TotalAV don't support XP anymore. And Guard.io is more of a browser extension than an antivirus. VIPRE won't install on XP, as stated in the "NOTE:" section.

since there are some follow-ups still not landing, I don't think it is good to make such a statement. and since the nature of my builds, usually I don't make these announcements, but I may update FAQ in first page from time to time to reflect codebase changes.

Ok. And what about researching a little bit first and posting then? I found the exact date of Avira's support end in a few seconds.

Your welcome.

Thank you, Mina

I always appreciate your volunteering (and I'm sure others do too). I actually smile when I read your posts. Keep it up! I completely agree with this, especially the first part. I appreciate @roytam1's work on the browsers, even if I don't update them.

so it supports it but also does not support it? I'm confused then does it work on xp? Webroot SecureAnywhere 9.0.27.49 is supposed to be the last XP-compatible version according to the manufacturer. Whether the virus definitions can still be updated must of course be checked. Webroot SecureAnywhere 9.0.33.35 is supposed to be the most recent version and does not support Windows XP anymore. You need Windows 7 at least.

The version number is 9.27.49, and the date created is 2019/11/04. (November 4, 2019)

One additional information in terms of this Webroot mess. Here is an official link to the last XP-compatible version of Webroot SecureAnywhere given by their support: https://answers.webroot.com/Webroot/ukp.aspx?pid=17&vw=1&app=vw&solutionid=1847 When I am at my desktop computer, I will check the version number and date of this file. It seems to be an online downloader due to its small size. But as I already mentioned, I am definitely not interested in this program.

okay ill try and do that from now on

I'm very sorry you're feeling like that.

I did not know that. However, turns out i already use for a 14 days this March version of New Monn, where WebComponents is included. That's not accurate statement. I usually download new versions from here: https://rtfreesoft.blogspot.com/search/label/browser And i usually read whats new in "Official Pale-Moon changes picked since my last build:" and "Official Basilisk changes picked since my last build:". Because i expected that the most critical changes will be mentioned there. The reason why i miss mention about WebComponents, is because it is written as casual change in the middle of long list named: "Official UXP changes picked since my last build:" Here is examle of issues from there next to important WebComponents announcement: I usually not read this because i don't understand meaning of this. I wAS expectING more BIG announcement about WebComponents enabled, then getting it lost in the list of super-complicated issues that 99.9% of people do not understand. I Like how the Pale Moon guys did it: They openly said - "hey guys, we now enabled WebComponents by default, major change, long awaited, how cool is that!!!" So i notice that. But if you think i will read every - Issue #OVER9000!1111 - you simply wrong and you lying to yourself. I deeply respect work of roytam! and often like and up-vote his posts here,

where always here to help you if you need it (: ive been going thru the same type of thing recently so I know how it must feel

Same here!

I agree with both of these you both make me smile (:

Good call, I edited the updated dates on the first post and in the Internet Archive item.

Here is a screenshot taken from CAupdater after successfully updating the root certificates: Cheers, AstroSkipper

seems to work: String eingabe = ""; // Evtl. vorhandenes (trainiertes) NN laden: File f = new File("or_perceptron.nnet"); if (f.exists() && !f.isDirectory()) { System.out.println("Soll or_perceptron.nnet geladen werden: "); eingabe = scanner.nextLine().toLowerCase(); System.out.println(""); if (eingabe.equals("y") || eingabe.equals("j")) { System.out.println("or_perceptron.nnet laden... "); neuralNetwork = NeuralNetwork.createFromFile ("or_perceptron.nnet"); } } ... // while (true) { while (! eingabe.equals("save")) { } neuralNetwork.save ("or_perceptron.nnet");

Could someone confirm that the legacy Avast v18.8 antivirus products for Win XP and Vista (available for download from the July 2018 Avast announcement End of Support for Windows XP/Vista) are still getting regular virus definition updates? WinClient5270 recently updated their original post in Last Versions of Software for Windows Vista and Windows Server 2008 (most of the the antivirus programs listed there are also compatible with Win XP SP3) that would indicate that legacy Avast / AVG v18.8 products are still receiving virus definition updates, but I came across a recent post <here> in the AskWoody forum from a Win XP SP3 user who believes that their Avast Free Antivirus v18.8 is no longer working and is looking for a replacement. I believe they'd prefer to stay with Avast Free Antivirus if a clean reinstall would fix their problem, but I don't want to suggest this if virus definition updates for this legacy product have stopped.

The file WSATemp.exe inside of this msi file from the link above is only 4,901,160 Bytes, so it must be an online installer. Its version number is 9.0.27.49 and its date of creation is 04.11.2019. The current version of Webroot SecureAnywhere seems to be 9.0.33.35, released 19.09.2022 and is no longer XP-compatible. Here is a link: https://www.webroot.com/us/en/support/support-consumer-release-notes Maybe, the last XP-compatible version 9.0.27.49 is still able to get definition updates. I can't test that. And I don't want it, either.

Do you found that the date on this topic dos not update?

There is another candidate which might run under Windows XP. It is SecureAnywhere® AntiVirus from WEBROOT. It is commercial.Here is the link to its German homepage: https://www.webroot.com/de/de/home On their German website, this program is listed as Windows XP compatible. And here is the link to its English homepage: https://www.webroot.com/us/en/home/products/av Strangely enough, on their English website, this program is not listed as Windows XP compatible. Different versions? Wrong information? Frankly, I never used this program, and I am not really interested in, either. Maybe, someone knows more about this program. I won't investigate that any further. I listed it here just for your information. Cheers, AstroSkipper

I think it's just a " change skin game", in China , we used "put old wine in new bottle" to called this operation...

I've been working on updating windows 7 with as many updates as I can that are marked as 'importent' and have gotten every update thru windows update but how do I get the rest of the updates not listed in windows update? if anyone could help with this it would be much appreciated-legacyfan (I'm also on 64bit if that help)

The thread is about preferred versions of W10.... In the case of Windows 7, there isn't even much to choose between, well maybe between build 7600 and 7601 (SP0/SP1) Personally at this moment I am using Windows 10 21H2 LTSC on my main computer, I have never been so happy with W10

Most of these websites provide badly researched information. To find out what the system requirements of the advertised programs are, you have to do your own research on the homepage of each product.

But actually, the idea of this thread is to do that without having to ask about it. Just posting antivirus or security programs which still work under Windows XP!

Sal, a very, very good TV show for you would be the third season of Twin Peaks 2017 ! I trust you'll get to 100% soon !

Recently seen? The engine and signatures updates for Avira Antivirus products running on Windows XP were abandoned on 08.04.2016. That is almost seven years ago! Where have you been the last seven years? FYI, here is a link with their product lifecycle archive: https://www.avira.com/en/support-product-lifecycle-archive Actually, everyone knows that Avira was one of the first that has turned its back on Windows XP. Anyway! So much for Avira! No option!

And my question is: Where have you been? Upstream's native WC implementation has been backported to UXP-based browsers by roytam1 (these, of course, include New Moon 28 - but NOT NM27) since the builds released on the first weekend of March: https://msfn.org/board/topic/184051-my-browser-builds-part-4/page/55/#comment-1239941 ... Roy spends considerable free time composing and putting up those Release Notes every Saturday but it appears, in practice, they go totally unnoticed by the majority of users here ; and it's a pity, TBH ... TL;DR: Grab yourself last Saturday's NM28 build and you'll see "what you really want to see"; BTW, since the native WC implementation is still being perfected, don't forget to update to the future NM28 releases as they become available ...

... AFAIAA, you need install neither (for simple tasks), because, if you're on a very recent and powerful browser (e.g. ChrEdge x64), you can do most GitHub stuff on-line, via their native on-line File Editor - also, you can try their "New Code Search and Code View" feature: (not 100% compatible with latest UXP, but mostly works ), which can also take you to their "new", powerful, repo managing tool (aka "Web Editor") served from "github.dev" (this is NOT compatible with UXP, as it uses the "??=" operator ): https://github.dev/UCyborg/palefill/blob/master/bootstrap.js Thanks ...

actually I tried to dig bugzilla (right now, using some non-productive time) and found upstream's upstream (i.e. mozilla) did the same thing: https://hg.mozilla.org/mozilla-central/rev/89c8025537a5 BTW I can't install user script with VM, getting "Error: Type error for parameter createProperties (Property "openerTabId" is unsupported by Firefox) for tabs.create."

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 http://o.rthost.win/basilisk/basilisk55-win32-git-20230318-d5e530bc0-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230318-d5e530bc0-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2135 - Follow-up: Check for aElement not being null (2249fbdf) (46178281d) - ported from UXP: Issue #2137 - Part 1: Modify :not() selector to accept a complex selector list (82fa9fb8) (e4c4f6a98) - import from UXP: Issue #2137 - Part 2: Implement SelectorParsingFlags and use it to pass info around (3bb3c193) (d85ee7571) - import from UXP: Issue #2137 - Part 3: Don't always use the internal pseudo-class for handling negations (b257a71c) (14afecdb0) - import from UXP: Issue #2137 - Part 4: Fix namespace regression (ef36c565) (6ba842009) - import from UXP: Issue #2135 - Destroy the host frame and restyle when there are content changes (18e69346) (e8b80ad7c) - import from UXP: Issue #2078 - Follow-up: Ensure empty selector lists aren't iterated when serialized (2be0261d) (49cf067e6) - import from UXP: [Basilisk] Add useragent override for instagram port of MoonchildProductions/Pale-Moon commit d641959f15cb1172f6f39130b579ccf6111a6f2f and 6d41a6139440a9c396308deca1725b0db823e127 (76cd3dfa) (16be7b5fb) - Reverting rev b1214c8d and 1d47bb34 again since I can still get a crash in `RegExpShared::finalize(FreeOp* fop)` (1b968eb1a) - import from UXP: Issue #2046 - Follow-up: Fix deprot in builtin/intl (a2d6260c) (6f4f99b6f) - Revert "Reverting rev b1214c8d and 1d47bb34 again since I can still get a crash in `RegExpShared::finalize(FreeOp* fop)`" (3cfac3f0f) - import from UXP: Issue #2160 - Initial support for notarizing during DMG package. Added --with-macbundle-idenity configure option to set a codesign identity. If no identity is set or cross-compiling from Linux no codesigning will be done. Currently doing a full deep bundle v2 sign, instead of limited v1. (3d2a4f40) (cac5e1f4c) - import from UXP: Issue #2148 - Don't null out RegExpObject -> RegExpShared pointer on GC. (ad8d9639) (ebab231f1) - import from UXP: Issue #2148 - Discard RegExpShared data tables when discarding regexp JIT code. (cdd91edd) (a2edee56f) - import from UXP: Issue #2148 - Make Vector not use AlignedStorage for its inline element storage (0365f940) (965181305) - import from UXP: Issue #2148 - Shrink Vector from (usually) four pointers in size to three when no inline storage is used. (48106904) (d5e530bc0)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230304-3219d2d-uxp-33981efb4-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230304-3219d2d-uxp-33981efb4-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-20230304-3219d2d-uxp-33981efb4-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.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230304-d849524bd-uxp-33981efb4-xpmod.7z Official UXP changes picked since my last build: - Issue #2117 - Part 1 - Update Mac DMG platform names to intel64 for Intel and arm64 for Apple Silicon. (8bacb52ca) - Issue #2117 - Part 2 - Revert "Follow up to d0eee8f01 - Run precomplete cmd during package staging" (cbc529bb0) - Issue #1382 - Part 1: Remove assertion that GetPreEffectsVisualOverflowRect is called only by frames whose parent is an anonymous block (691afc8c8) - Issue #1382 - Part 2: Add crash test (ebe27baa2) - Issue #1593 - Follow-up: Fix :host selector matching (edc45f684) - Issue #1344 - (Parser: Java) Don't reset containsHyphen value after finding one (d9b7057ff) - Issue #1344 - (Parser: C++) Don't reset containsHyphen value after finding one (55100bb28) - Issue #2118 - Part 1: Update gfxUtils YuvColorMatrix functions to match upstream mozilla code more closely. (beef43760) - Issue #2118 - Part 2: Add support for Identity YUVColorSpace (3e62b1fc9) - Issue #2101 - Part 1: Add mColorRange info to YCbCrBuffer (c0c76cd45) - Issue #2101 - Part 2: Use stdint.h types instead of uint8 and friends (42f329689) - Issue #2101 - Part 3: Update libyuv (a4d1f57b9) - Issue #2101 - Part 4: Add color range support to gfx/ycbcr (b5f9e9abb) - Issue #2101 - Part 5: Add ColorRange support to video decoders (e59e8c3b2) - Issue #2101 - Part 6: Plumbing of ColorRange between video decoders and YUV convert (2b88f2c9a) - Issue #2101 - Part 7: Add color range support on GPUs (687733f9d) - Merge remote-tracking branch 'origin/tracking' into custom (7c0ddca06) - Issue #1375 - Follow-up: Remove shadow tree hacks in the frame constructor (6a26ce345) - Issue #1375 - Follow-up: Get the insertion point right when reconstructing direct children of a shadow root (b40c87a59) - Issue #1361 - Enable WebComponents by default in the platform. (9b2520249) - No Issue - Enable MSE for WebM on all platforms. (87b94f83c) - No Issue - Remove speech recognition pref and enable TTS API by default. (2d7d00b75) - Issue #1375 - Part 1: Allow moving a reference into nsInterfaceHashtable (53e2e5d8d) - Issue #1375 - Part 2: customElements.define must upgrade custom element in shadow-including tree order (6781f5b6c) - Issue #1361 - Enable WebComponents' getRootNode by default. (52dbe9733) Official Pale-Moon changes picked since my last build: - [Basilisk] SSUAO - Use native mode for Zoho (cf80fbdb7) - [Basilisk] SSUAO - Add pale moon addons slice (b7aac7342) - [Basilisk] Bundle fonts on GTK platforms, not just Linux (42c8c7ff1) - [Basilisk] Remove dailymotion override (3c54aa7eb) - [Basilisk] Fade out tab label on overflow instead of ellipsis (89dd425fd) Official Basilisk changes picked since my last build: - [Pale-Moon] Issue #1908 - Fade tab titles instead of using ellipses (21f0c3de6) - [Pale-Moon] Remove DailyMotion override (apparently no longer needed) (021d76f3a) - [Pale-Moon] Update SSUAOs for known sites no longer needing workarounds. (889dfd882) Update Notice: - You may delete file named icudt58l.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.

Hello again. The instructions in the first post should work for Vista x86, but since you are running Vista x64, you need to make 2 more registry changes as mentioned here: https://msfn.org/board/topic/177994-tls-1112-and-vista-issue-no-options/?do=findComment&comment=1157010

Windows 98 Simulator is one of the most accurate 98 look a like's around. It's in 16x9, has a modern web browser and media player, just look at it! Internet Explorer has been updated, You can even play YouTube videos. Video: Top Gear Media Player has also been updated, Having MP4 and other file type support. Windows 98 Simulator also keeps it's intergration with Android, having a app list and allowing you to access it's file system. Application. (Android Only) If your a 98 Diehard, I think you'll be impressed by it! -Nerdulater

Always! But the simulator is for phones that can't run 98 using dosbox or limbo

PrivacyTests.org No. 6 Open-source tests of web browser privacy. Updated 2021-11-24: https://privacytests.org/

For the more observant among you, you might've noticed that @Dylan Cruz 's last screengrab contains one additional IE9 cipher suite [TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13)] that is absent on my IE9 SSL Labs Client Test! In fact, on a TLS 1.0+1.1+1.2 enabled Vista SP2 machine, IE9 supports the below twelve variations of cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Forward Secrecy 128 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Forward Secrecy 256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Forward Secrecy 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Forward Secrecy 256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x32) Forward Secrecy(2) 128 TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x38) Forward Secrecy(2) 256 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13) WEAK 112 TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK 256 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK 112 TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 (2) Cannot be used for Forward Secrecy because they require DSA keys, which are effectively limited to 1024 bits. At some point, I had removed support for half of them, deemed to be extremely WEAK/insecure: Removed: *TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128 (TLS1.1) *TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK 256 (TLS1.1) *TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK 112 (TLS1.2) *TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13) WEAK 112 *TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 *TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 which currently leaves me with TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Forward Secrecy 128 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Forward Secrecy 256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Forward Secrecy 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Forward Secrecy 256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x32) Forward Secrecy(2) 128 TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x38) Forward Secrecy(2) 256 NB: The last two do not support FS, so I might remove them, too... PS: On my 32-bit system I used Disable_RSA_Ciphers_RC4-128-128_3DES-168.reg : Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\PKCS] "Enabled"=dword:00000000 A computer restart is needed before these changes take effect! Reference: https://support.microsoft.com/en-us/help/245030/how-to-restrict-the-use-of-certain-cryptographic-algorithms-and-protocols

The Protocol Support section of the SSL Client Test available in browserleaks.com also fails for me here in IE9 32-bit: ... while, at the same time, the Handshake section is displayed correctly: Perhaps they're using some CSS/JS code in the first failing section that the deprecated IE9 rendering engine can't cope with... (?) For IE9 specifically, you may want to use the SSL Labs Client Test, https://www.ssllabs.com/ssltest/viewMyClient.html :

Auto Screen Capture supposedly needs at least Windows 8. It turned out that application doesn't depend on anything that only newer systems have. Here's the fixed version that will happily run on XP/Vista/7 (.NET Framework 4.0 required). These were required code changes.

Page saved for posterity in the webarchive: https://web.archive.org/web/20170810231809/http://www.msfn.org/board/topic/176902-enabling-tls-1112-support-in-vistas-internet-explorer-9/ @Ruan Welcome to MSFN (apparently a little too late ) Thanks for your kind words...