Leaderboard

UPDATE [June 7, 2019]: Post-SP4 Update Pack released! This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net.

Well it turns out that Microsoft .NET Framework 4.7.2 can also be installed on Windows Vista using the same installation method for 4.6.2 Final, and it can also be patched using the .NET 4.6 security updates for Server 2008! In addition, ShareX still works with this version installed, and no dependency errors are present: Now, I could not find an application that specifically required this version of .NET Framework, but it appears that ShareX is able to use it without any issues, in contrast to .NET Framework 4.8 Preview... As such, I have also added this version of .NET Framework to the list Also, this is irrelevant to .NET Framework, but Twitch Desktop App recently dropped support for Windows XP and Vista, so it has been removed from the list

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190525-315ffd563-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190525-315ffd563-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190525-315ffd563-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190525-315ffd563-xpmod.7z Official repo changes since my last build: - Unhook Unboxed Objects option (3ded48cbe) - remove unboxed code chunk (wip1) (9a3141515) - Remove initial chunk of Unboxed Objects machinery part 2 (3b36a43e8) - Remove Unboxed Objects in ScalarReplacement (d40bcc350) - Remove unboxed objects from GC (5fd4b8726) - Remove unboxed object code from iteration. (8feffe707) - Remove array header (a5c2961c4) - Remove Unboxed Objects from vm/ Part 1 + fix deprot (543fa1674) - Remove unboxed object code from jit, Part 1 (fa8bfa1a0) - Remove Unboxed Objects from vm/ - Part 2 (201d8ee48) - Implement array.flat and array.flatMap (162e22a7d) - Implement Symbol.prototype.description (41731a7f3) - Issue #971 - Fix browser.link.open_newwindow functionality in Pale Moon (f9dc4e8cc) - Merge pull request #1097 from FranklinDM/pm_external_sametab-work (a1f96f11d) - Merge pull request #1091 from MoonchildProductions/remove-unboxed (be8d03cf1) - Remove a stubbed telemetry function from app AUS. (bb5e0a1be) - Enable double buffering when using XRENDER. (2fd300786) - Merge pull request #1100 from Ionic/bugfix/xrender-flicker (372fccddf) - Issue #1104 - Set the browser's opener when adding a new tab - This modifies `loadOneTab` and `addTab` to accept an opener - This code was adapted from Basilisk's copy of tabbrowser.xml without the refactored code changes (which is a lot more involved as it divides addTab's functions into multiple functions) (797697e26) - Issue #1104 - Pass an opener to loadOneTab in the openURI function (10318170b) - Issue #1101 - Support gzip-compressed SVGs in OpenType+SVG fonts (73f9b2c70) - Merge pull request #1108 from g4jc/svg_opentype (f8157b8a6) - Merge pull request #1105 from FranklinDM/pm_uri_tabbrowser-work (f0e357608) - Merge pull request #1099 from adeshkp/remove-telemetry-func (315ffd563) My changes since my last build: - ported changes from mozilla upstream: bug1351303, bug1352235, bug1371508, bug1430268, bug1352734

alright it works. new Saturday binaries will work with 1.3 compat mode.

I've changed my mind. I'm going to keep it up. Y'all have inspired me to not give up. So, XP x64 will remain my main OS for a long time; I can still squeeze more life into it.

I have always thought that having the latest is never the best. The latest operating system (or now version of Windows 10) is the worst thing you can have for security. Computers must be updated but not to the latest version. For example, it is better to have Windows 1803 updated than 1809 updated. Microshit uses our computers as a test bench and the correct updates are passed on to companies after 4 months or more. The proof of this is in the Windows 10 itself, update options and selection of the download semi-annual channel.

Sorry for the inactivity all- finally got around to updating the topic! Now to post the latest Summary of Changes... SUMMARY OF CHANGES TO THE LIST FOR JUNE 11, 2019: Updated Vivaldi 1.0 entry to 1.0.435.46. Added Vivaldi 1.1.443.3 Developer to "Web Browsers" -> "Chromium-based" section. Added Adguard to "AntiVirus/Security software" section. Updated information about Telegram Desktop: the software will stop supporting Windows XP/Vista on Sept. 1, 2019. Fixed broken download link for Adobe Reader X v10.1.16. Added FineReader 14 to "PDF Viewers/editors" section. Updated WPS Office 2016 entry to WPS Office 2019. Updated link for VLC Media Player 3.0.7 to point to the final version instead of the beta version. Added ArtWeaver Free and Pro 6.x to "Video/Photo Editing software" section. Updated information about Krita - no longer ONG; added 4.1.7 as the last version to work with Windows Vista (newer versions do not work due to missing Win7+ DLL functions). Updated information about Sony Sound Forge - later versions up to 13.x can be ran on Vista by using the Portable version of the software (thanks to @artomberus for finding this). Fixed broken download link for Microsoft Virtual PC 2007. Added new section - "Language Translation software" Added Promt 18 to "Language Translation software" section. Added Nero 2019 Platinum (unofficial repacked version) to "Optical Disc Media Management software" Added SuperTuxKart to "Games" -> "Active Development" section. Added Adobe AIR 29.0.0.112 to "Software/game development" section. Fixed broken download links for Java 9.x. Fixed broken download link for Notepad3 4.18.512.992. Added OpenVPN 2.4.6-I602 to "VPN Clients" section.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190608-19c0f5e9f-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190608-19c0f5e9f-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190608-19c0f5e9f-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190608-19c0f5e9f-xpmod.7z Official repo changes since my last build: - Revert "Improve origin-clean algorithm" (f47d45be4) - Improve `origin-clean` algorithm based on our previous changes. (3f1ef7a67) - Remove e10s force-enable/-disable prefs and a11y considerations for starting in e10s mode. (19c0f5e9f) My changes since my last build: - Change help link for unofficial branding (Serpent) (65bd689bd) - Point release notes to author's Web page (fb327115f) - Update Help link to point to msfn.org (a9836cb56) - Remove palemoon.org from New Moon branding (9e4dfbda3) - Merge pull request #2 from Mathwi/Mathwi-patch-2 (9cee045fd) - Merge pull request #1 from Mathwi/Mathwi-patch-1 (7a5bba6f8) - Redirect support URLs away from palemoon.org (1de2444bc) - Redirect browser.feedback.url from palemoon.org (426aef14c) - Update app.support.baseURL pref again (7254c3400) - Merge pull request #2 from Mathwi/custom (a7ad0dde7) - Revert "Remove e10s force-enable/-disable prefs and a11y considerations for starting in e10s mode."

Artweaver 6 unofficially works on Vista. It can be installed without any tricks.

I wanna tell you something that happened to me. I have a network populated by Windows XP machines, all patched and with Avast and they are all connected to internet and they use it on a daily basis for any sort of stuff. There are other machines in the network that are running other OS like Fedora Linux with Nod32 antivirus and Android with Avast as well. Last but not least, there are virtual machines with Win10, Win98 and other versions of Windows for testing purposes, but they are not accessible from the outside world. Recently we decided to setup a test bench in bare metal, running Windows Server 2019 and connect it to internet and the outside world. We've got an email from the ISP stating that one of our machines has probably been compromised as it has been used in an attack. Later on, we found out that the attacker managed to get access to the machine by using a vulnerability in the RDP protocol of Windows Server 2019. The machine had all the latest updates installed, but no antivirus or firewall other than the default Microsoft ones (it was a test bench after all). It's funny how someone who attacked a network full of Windows XP machines just ignored them, went straight to the one running Windows Server 2019 and managed to compromise it... It surely makes you think...

The latest version of Qihu's 360 Extreme Explorer (v11.0.2086.0, released May 16th 2019 - its default UA declares a Chromium 69.0.3497.100 compatibility ) will also pass the test : But this is on Windows Vista SP2 32-bit, not on XP SP3 32-bit (hence, one of you XP users would have to test... ) EDIT: Make sure in "flags" that chrome://flags/#tls13-variant is set to "Enabled (Final)"

The support may be over, but this doesn't mean that people stopped using XP. Today I've been to the dentist and he is using XP. When I asked him why, he said that XP is connected to the sensors of the tools he uses on a daily basis and that he upgraded to Windows 10 months ago as he changed his computer, however the technician he called spent hours trying to make it work with those sensors but he failed, so he reverted to Windows XP. "I've been using these things since 2005" he said, "I'm gonna keep using XP until I'll change the whole thing, its tools and its sensors, which is unlikely to happen anytime soon". Since I wasn't able to take a clear shot, I told him about the Windows XP Spotter group and I quickly told him that we take pictures of XP running in businesses 'cause we are fan of the OS, so he kindly let me take this picture:

An update about the Wayback Machine saving process. I finally got some courage and, after thinking, searching, reading and even asking for help (a big thank you to them! ), wrote a Python script that automates that said saving process. It's sloooooow but restartable (i.e. will continue with the first link left unprocessed), so it will take a while to go through the links @ED_Sln posted before. But rest assured that, eventually, all those links will appear on the Wayback Machine! Right now (at the time of writing), 284 links had been processed

I can control myself, therefore no public download links! Honestly, MS can integrate even more censorship modules and other nonsense in their current "permanent construction site", which goes past me. I continue to use Windows XP!

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190615-c9edf588e-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190615-c9edf588e-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190615-c9edf588e-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190615-c9edf588e-xpmod.7z Official repo changes since my last build: - Add Atomics.notify instead of Atomics.wake according to revised spec. (284b4cffd) - Add Yandex (ru) search plugin (c9edf588e) My changes since my last build: - import change from mozilla upstream: Bug 1384330 - Blocking the mozAddonManager when pref 'privacy.resistFingerprinting.block_mozAddonManager' is true. r=arthuredelstein,mossop (f05d85ff6) - Move app.feedback.baseURL pref to branding (a7d2a6260) - Move app.feedback.baseURL into branding prefs (f4b8b0d90) - Move app.feedback.baseURL here and point to MSFN (8584b233f) - Merge pull request #4 from Mathwi/custom (044e258d9) - revert "Remove e10s code from browser widget. (083d322b7)" to keep e10s useful. (ef715102e)

JRE 9 and JDK 9 x86 - https://mega.nz/#F!gD41iCjQ!YMoTWKGtiJyym7bWDuj7kQ jre-9.0.4_windows-x86_bin.exe and jdk-9.0.3+9_windows-x86_bin.exe :)

Or the update was posted by mistake. If this is so, then it means that updates for XP are released, but they are simply not published anywhere.

I am opposed to the idea that RT should have to 'worry' about some 'internalized' ADD ON working with his Browsers. It seems like that ADD ONS (LEGACY) can 'stand on their own' -- so LET them do that. (Evil Humor) And, @VistaLover enjoys solving SOME riddles related to 'Ghosts in the Old Machines' https://o.rths.cf/boc-uxp/ RT has some ADD ONS (*.xpi files) listed for download at his above URL for BNAV Browser. https://legacycollector.org/firefox-addons/ This above URL has Firefox LEGACY ADD ONS too. Just a straight forward download, no install involved. https://legacycollector.org/firefox-addons/722/index.html NoScript Security Suite

Time Zone Update released DST changes in Windows for Morocco and the Palestinian Authority KB4501226! Download via Update Catalog http://www.catalog.update.microsoft.com/Search.aspx?q=xp embedded KB4501226 http://download.windowsupdate.com/d/msdownload/update/software/uprl/2019/06/windowsxp-kb4501226-x86-embedded-enu_708fe12ecfbbb070821a87fd538af3b6b6fd3084.exe

This appears to be from some German speaking country.

It looks like VLC 3.0.7 stable was released today.

I agree that someone from MCP coming onto this thread and striking a disagreeable attitude, making threats, and generally being unpleasant, doesn't exactly predispose folks here to try to accommodate their wishes. And it's also true that to the extent there are "branding" issues with unofficial builds, they are the fault of MCP themselves, not @roytam1. So I can sort of understand having a spiteful attitude toward MCP and their demands. But I think we already decided we weren't undertaking a full rebranding of New Moon or Serpent anyhow. At this point, all we're talking about is getting rid of the "you've successfully upgraded" Web page and redirecting a few Web pages that come up when users of @roytam1's browsers use the Help menu. It's just not that big of a deal, and it's worth doing anyhow for the benefit of New Moon / Serpent users (not to mention msfn.org, which stands to gain a few more members). If it eases tensions with MCP a bit too, so much the better. (And if someone's really stubborn about it, they can switch all their prefs back in about:config anyhow.)

uB0-legacy has just been updated to version 1.16.4.11; those without uB0 updater installed, should download and install manually: https://github.com/gorhill/uBlock/releases/tag/firefox-legacy-1.16.4.11 Also, latest NM28-compatible language-packs have been (recently) updated to v28.6.0_RC2 : https://github.com/JustOff/pale-moon-localization/releases/tag/28.6.0_RC2

I think @VistaLover has a point, here. Changing both app.support.* strings to default straight here to this thread on MSFN is easy to do and might be a good 1st step. This @roytam1 might implement already in his next installment of the compiled versions of all browsers he's providing modded versions for XP. It's much simpler than rebranding, uncontroversial and breaks nothing, while being an incontrovertible proof something is actually being done to proactively prevent people from going to PM forums for support.

He's gonna see whether you are a Winnie the Pooh fan and judge you. xD https://www.theguardian.com/world/2018/aug/07/china-bans-winnie-the-pooh-film-to-stop-comparisons-to-president-xi

Well, the title of this thread (in the form of a question) is a tad misleading ; if the real question was Can you establish TLS 1.3 connections under Windows XP? then the answer, of course, is YES . Both UXP browsers (New Moon 28, Serpent 52.9.0), the Moebius fork (Serpent 55.0.0), the Tycho fork (New Moon 27) and probably other @roytam1's forks all support the final TLS 1.3 draft (RFC8446), as well as all three cipher suites associated with TLS 1.3: TLS_AES_128_GCM_SHA256 (0x1301) TLS_AES_256_GCM_SHA384 (0x1302) TLS_CHACHA20_POLY1305_SHA256 (0x1303) ; you can test TLS 1.3 support of these browsers with https://tls13.pinterjann.is/ https://swifttls.org/ https://cert-test.sandbox.google.com/ (and a few other test URLs...). BTW, the NSS library in these browsers was recently downgraded from v3.44 Beta to v3.43 stable release; perhaps @roytam1 could share a word (or two ...) why that was necessary ... Additionally, I was recently informed that the excellent project ProxHTTPSProxy by @heinoganda has indeed achieved TLS 1.3 support under XP for the type of browsers (IE8, Google Chrome 49 and, possibly, earlier) that don't come with their own TLS support but rely upon system libraries for secure connections; so TLS 1.3 in itself shouldn't be an issue... But what is indeed specific is the configuration of linked test server, https://tls13.1d.pw/ It is no coincidence that a Russian member of this forum brought this up, because, it turns out that, the administrator of said test server is a Russian guy, Александр Венедюхин ! In fact, he maintains a blog where he documents this project and the TLS 1.3 test configuration of the server; original articles can be found at: https://dxdt.ru/2018/08/05/8597/ https://dxdt.ru/2019/01/26/8672/ As I'm not at all fluent in Russian (), I had to enlist the help of (evil ) Google, but what the heck... : https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ I don't consider myself proficient in the field of cryptography and/or secure connections, but what I gathered from the translated text was that the server is configured to send a special HelloRetryRequest response to force a renegotiation of connection parameters; the implementation of Encrypted Server Name Indication (ESNI) along with non-ECDH manifested a bug in Mozilla's NSS library, so that is probably why the Firefox forks won't connect currently to that specific test server! (they yield a SSL_ERROR_RX_MALFORMED_SERVER_HELLO error code ). Hopefully, the reported bug will be fixed in a future NSS version, if/when that is applied to UXP, we'll have successful connection in the UXP forks... Frankly, TLS 1.2 is still predominant, but with 1.3 steadily gaining ground; this specific connection test is but a margin case where 1.3 is involved, so I won't be losing any sleep over it...

Nanobot informs me elsewhere, that DoaJC_Blogger guy is working to bring Chromium 76 to Win Xp: https://browser.taokaizen.com/forum/viewtopic.php?p=3219#p3219 https://browser.taokaizen.com/forum/viewtopic.php?t=2766

Some months ago I complained about the poor performance of Hotmail after their last update became final. They gave me an URL to access the older version, which works much better with XP compatible browsers. It also solves the problem with Chrome 49. https://outlook.live.com/owa/?path=/fb

... As it finally turned out, it is yet again another case of intentional/artificial block of Vista by M$ ; the blocking code lies somewhere inside the compiled .EXE setup, but it's obviously absent in the unpacked .MSI installer.I do wonder if it's still possible to install 4.6.2 Final by running the Setup.exe file (86.1KB) that exists inside the (unpacked) directory; an inspection with Resource Hacker reveals it does indeed support Vista in its manifest: <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!-- Windows 10 --> <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" /> <!-- Windows 8.1 --> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" /> <!-- Windows 8 --> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" /> <!-- Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" /> <!-- Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" /> </application> </compatibility> I guess if that doesn't work, on a 32-bit platform one should run netfx_Full_x86.msi (in the unpacked directory); as mentioned by Osman, in the root of the unpacked setup one can see prerequisite windows updates for Win8 (KB3151804), Win8.1 (KB3151864) and Win10 (KB3151900), but, surprisingly, not for Win7 (and, of course, none for WinVista, which the package doesn't officially support) - in any case, it should be stressed that the (somewhat unorthodox) 4.6.2 install shouldn't be attempted on a Vista system which isn't fully updated (SP1+SP2+all subsequent updates at least until EoS on April 2017), just for good measure... All in all, a very positive outcome from a joint effort, started by @Osman Kovan and joyfully concluded by @WinClient5270! Cheers PS: I couldn't help noticing how a 59.1 MiB file (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) blows up to more than 1.62 GiB (!) when expanded!

GOOD NEWS EVERYONE! Thanks to @Osman Kovan for figuring out how to install Microsoft .NET Framework 4.8 on Windows Vista, I was able to use that same method to install Microsoft .NET Framework 4.6.2 Final on Windows Vista. I just extracted the setup .exe file with 7zip and ran the .MSI installation file contained within it, netfx_Full_x64.msi: After installing, I then tested ShareX Portable to see if it gave the same missing dependency errors that it does when running it with .NET Framework 4.8 Preview installed, and to my delight, it works just fine in Vista with 4.6.2 Final! Remembering what @VistaLover asked me to try with 4.6.2 Preview installed, I then decided to try the latest .NET Framework 4.6.x security rollup for Windows Server 2008 to see if it would patch .NET Framework 4.6.2 Final on Vista, and, lo and behold: It works! This means that .NET Framework 4.6.2 Final CAN be installed and patched on Windows Vista using @Osman Kovan's installation method, and then by downloading the .NET 4.6 patches for Server 2008 manually from the Microsoft Update Catalog. As such, Microsoft .NET Framework 4.6.2 Preview has been replaced with the final version on the list: Special thanks to @VistaLover, @Osman Kovan, and @artomberus for helping make this possible!

@artomberus ... Actually, the very last build of Vivaldi on the stable (release) branch that would run on Vista SP2 is 1.1.453.59, based on Chromium 50.0.2661.102 source code: The screengrab is actually from an unofficial portable installation (in PAF format); search for it on the web... Official link to the v1.1.453.59 (32-bit) installer: https://downloads.vivaldi.com/stable/Vivaldi.1.1.453.59.exe The very last build of Vivaldi on the snapshot (dev) channel that would run on Vista SP2 was indeed 1.2.470.11, based on Chromium 50.0.2661.89 source code: (... again, this is a portable installation in PAF format). The relevant vivaldi blog entry is: https://vivaldi.com/blog/snapshots/snapshot-1-2-470-11-editable-gestures-2/ but, as you found out, ALL binary links are 404'ed now... TBH, both builds date to May 2016, which means they are probably unsafe to browse today's web with, not to mention that many sites have dropped long ago Chromium 50 compatibility; YMMV, but poor site/page rendering is highly probable ; if you plan to install uB0, 1.16.18/1.16.20 is the last one (but hard to find as a .CRX file) that successfully works with those old builds... I only have on disk the 32-bit version of Vivaldi 1.2.470.11[dev] (file Vivaldi.1.2.470.11.exe, dig. sig. of Wed, May 4th 2016, 17:08:01), but I am unsure as to whether I am allowed to share it here... Don't have time currently to search exhaustively for an archived link for it (sadly, web.archive.org doesn't appear to have salvaged it )...

Where's @Bersaglio? I assume we can just change "192" to "207" in the links below. I'm about to give it a try anyway. Edit: Apparently works fine. (Avast did scan "plugin-container.exe" for me, but didn't find any malware!)

@Mcinwwl Try it with the help of "https://web.archive.org". For this I found a website where the original links of Windows Live Essentials 2009 are available (https://xhavitks.de.tl/Messenger.htm). Now take the desired link, for example from "Download Windows Live Essentials (Messenger) 2009 - Polish (full)" (http://g.live.com/1rewlive3/pl/wlsetup-all.exe). Insert this link into the search of Wayback Machine, I found the best in 2014 (Jun 6). Give the process some time. I've downloaded 41 languages myself, but I have no way to upload them permanently. If anyone has a chance I can upload them, so you can send me a PM.

Great news! @WinClient5270 will not have to edit the listings for AVG and Avast to add, "Works on build 6002 but causes BSODs on build 6003." (However there could be other build 6003 incompatibilities lurking out there.)

A big fat thank you, Microsoft! So you do love us, after all. Why am I thanking Microsoft? Well, it's because contrary to what they said in 2018 and reiterated in 2019, they have released the new Microsoft C++ Redistributable 2019 x86 and guess what? They are XP-Compatible. This is a very good news as it means that programmes compiled with Visual Studio 2019 will be able to run on XP without targeting the old deprecated v141_xp but using the new one. Thank you, Microsoft, thank you!! https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190601-363bfeb2c-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190601-363bfeb2c-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190601-363bfeb2c-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190601-363bfeb2c-xpmod.7z Official repo changes since my last build: - add main thread only cache for nsIAtoms to speed up atomization dom/base (a3434ba00) - add main thread only cache for nsIAtoms to speed up atomization xpcom/ds (ddff63b2d) - remove unnecessary spaces (58ff91d97) - make HTML parser to use faster atomization in main thread (a371a69a7) - Lots of time spent maintaining nsDisplayLayerEventRegions (#1116) (622ad88c5) - Add missing NS_AtomizeMainThread(nameToUse); (7214f0814) - Fix architecture flag for PPC64 (e24e6346b) - Issue #1102 - Disable ＜meta http－equiv＝set-cookie＞ (ca9e6a4fa) - change for nsNodeInfoManager.cpp (c0c64138c) - Merge pull request #1114 from g4jc/disable-meta-cookie (722607270) - Merge pull request #1115 from win7-7/NS_Atomize-cache (915ffc660) - Make nsFind::Find handle empty string searches. (b89570e31) - [libpng] Backport an upstream libpng patch. (80eb8e08d) - NodeInfoManager should use a local cache (449cb277d) - [js, ARM] Always check error return from BufferOffset::diffB. (a24d62130) - [IndexedDB] Call SendFailureResult if the actor has been destroyed. (9dfb9401a) - Avoid some useless ForgetSkippable handling while we're already dealing with snow-white objects. (57e5655e8) - [Basilisk/Pale Moon] Update region.properties. (764e2a624) - use memcmp for nsIAtom Equals to improve performance xpcom/ds (733f6b770) - use memcmp for nsIAtom Equals to improve performance parser/html (bf1e5431f) - Issue #246 - Revert "Revert "Remove unwanted newtab page code"" (1eca3c3a6) - Issue #246 - Remove more of compact mode and newtab junk from Basilisk (73d1087fc) - [media] Rewrite AudioConverter::DownmixAudio (c4e345b6d) - Merge pull request #1121 from win7-7/nsHtml5PortabilitylocalEqualsBuffer-pr (1f239f817) - Merge pull request #1119 from win7-7/NodeInfoManager-local-cache (02b10f4bd) - Add commit message style guidelines (#1117) (a5bef2b46) - Issue #246 - Remove "enhanced" newtab code from toolkit (8db31d536) - Issue #246 - Remove "enhanced" newtab code from Pale Moon (97477c1e9) - Bump platform version for primarily #1112 and #1061 (104cd501a) - Merge pull request #1122 from adeshkp/remove-newtab-basilisk (63d677035) - [Pale Moon] Fix event.stopPropagation is not defined when clicking the show/hide tiles on about:newtab (a38cc1a2f) - [places] Prevent some abuse of smart queries. (5b5743eee) - Port an upstream Skia fix. (47c52f2dc) - Improve origin-clean algorithm (fb1b45e5f) - Update HSTS preload list (c7138e3b9) - Ensure we AddRef prior to early return in MediaType::Assign. (b3632493a) - Disallow res external protocol handler. (65991dc1f) - Make extra sure Compositables don't refer back to layers after reassignment. (9b655e366) - Tweak some NSPR variables for Darwin. (66b55fbc0) - Improve efficiency of (C++) heap allocations related to BytecodeEmitter::code. (6cc615bbe) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (678a41b29) - Perform a size check when dealing with clipboard data to be sure. (1fe365eba) - Fix #1091 deprot (50062bdfc) - Make nsFind::Find actually use a string type as input. (d873bd969) - Treat *.jnlp as an executable class file, like *.jar (21495c589) - [WebGL] Enable size limit on Linux. (231155288) - Show the update UI instantly instead of after 10 minutes of inactivity (cee913be9) - [Pale Moon] Update the check for updates menu item logic for already staged automatic updates (d197e65f4) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (363bfeb2c)

Even when "Automatic Updates" is turned OFF in the Control Panel, which has been my selected setting since at least 2007, there is an eponymous sevice which is set to "Automatic" by default, which I've always kept untouched. I'm disabling it right now. It might solve the issue in an easily reversible way, IMO, being an alternative to removing the POSReady key. Let's see what happens... Cross your fingers!

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190525-8e9351569-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190525-8e9351569-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190525-8e9351569-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190525-8e9351569-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - initialize webp with different mode depending on endianness (c47ba6f6e) - pointer style (09a5f12ee) - Bug 1139983 - Fail the alloc if the nursery is full in NoGC (a85408eef) - Bug 1135963. Allow JS_InitializePropertiesFromCompatibleNativeObject to deal with objects that have different prototypes. (ec8d1799b) - Bug 1066233 - Part 1: Parser suppoert for ES6 ClassExpressions. (04e536bb6) - Bug 1066233 - Part 2: Emitter support for ES6 ClassExpressions. (7e141d412) - Bug 1066233 - Part 3: Reflect.parse support for ES6 ClassExpressions. (30595e6df) - Bug 1066233 - Followup: Address a forgotten review comment. (836b26f59) - Bug 1066233 - Tests. (5df23d2e6) - Bug 1143106 - Fix construction of singleton objects during parsing when unboxed objects are in use (1749494c6) (44d5f1a6a) - ported change from mozilla upstream: bug1430268 (7bd4b2d31) - import change from rmottola/Arctic-Fox: - Bug 1143256 - Store object metadata using a weak map (38a6dc237) - Bug 1143513 - Make nsFrameList compatible with range-based syntax and utils. (2c69cf891) - Bug 1149854: Use range-based for loops when iterating over child frames in nsFlexContainerFrame.cpp. (5c1e258db) (8e9351569)

A possible future vulnerability based on that code. It may be that it doesn't even work on Windows XP. Interesting is the possibility offered by Novirusthanks OSA which has 2 specific rules:

@Nojus2001, you're definitely not alone. A weather forum I used to visit that closed sometime late last year or early this year was revealed to be running on Server 2003 until the bitter end. I'm sure that it's found itself mired into tonnes of big corporate networks too. It makes a wonderful workstation OS as well. And this is my 15-hour-old XP x64 install: :

I prefer my browsing habits sent to China than to Google anyway. And I never keep logged in to it... just for Gmail, if at all, when needed.

It does seem to also work on Windows XP x64 SP2 with 360 Extreme Explorer, therefore it should work on all Windows XP editions.

The invite link is invalid, however I'm gonna contact him via the advanced Chrome Forum. There's no reason to have two backported version of Chromium when we can have a joint project and share what we achieved. I'm gonna send him everything we have done as soon as I have the chance to have a word with him, then perhaps this time we will really have Chromium running on XP.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190518-c72afc3c8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190518-c72afc3c8-xpmod.7z Official repo changes since my last build: - When using XRENDER, create Xlib-based offscreen image surfaces. (996887f40) - Issue #1084 - Add null check for URL Bar in the writePlaceholder() method (8b7d91e51) - [PALEMOON] buildHelpMenu() is executed by the shared help menu but not all windows have the AppMenu (f857efc35) - Update sync clear history function to use new clear() API call. (a53ab3f34) - Merge pull request #1086 from zootboy/master (70c5719dc) - Remove deprecated appending of #-moz-resolution from Pale Moon and left over from nsMediaFragmentURIParser.h (c7dc667e6) - Merge pull request #1060 from Ionic/bugfix/scrolling-regression (413ba3bad) - Rip broken telemetry out of the app AUS. (1595ee7da) - Fix scroll bar orientation on MacOS (06f7a03ff) - Map IntersectionObserver rect to the correct viewport. (34d5483ac) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (f932fb94d) - Implement String.prototype.trimStart and trimEnd. (354c6dcee) - Add nullcheck. (c72afc3c8)

Yes, I tried the final version of .NET 4.8 on Vista just now, and while it could be installed, it unfortunately displays the same behavior as 4.8 Preview: This means that .NET 4.7.2 is the final version that can be used on Windows Vista without these issues, seemingly I did just that, and here are some of the files I got: I then modified the .MSI file with Orca like @artomberus did, and received the same error message when attempting to run the program after installing it... However, this limitation is pretty easy to circumvent using @blackwingcat's PEMaker tool: After modifying and recompiling the .exe file using this tool, that eliminated the "not a valid win32 application" error but sadly, my success was short-lived: So it looks like Paint .NET is a no-go on Vista As far as SP1 goes, .NET Framework 4.7.2 does "require" this, but there is no mention of the Platform Update "requirement" on Microsoft's .NET OS compatibility chart here. Bearing this in mind, the software likely calls for functions introduced in Windows 7's Platform Update, which would explain why it doesn't work in Vista even with .NET Framework 4.7.2 installed... Sadly, no. Downloading the installer and attempting to run it does not work, and extracting it provides no .MSI installer to use/modify, nor are there any available elsewhere on the web, from what I've found:

@Blados, no, both architectures are supported. But the developers, when they throw support for Vista, complained that the code was very different and difficult to maintain. Due to hardware acceleration. I tried to run the MSI file - it sends to setup.exe . Setup.exe requires Windows 7. I modified the MSI file and installed it. With .NET 4.7.2 is installed. ... is not Win32 application. Alas.

Yes - all vulnerabilities exist regardless of whether or not they are exploited. Disabling RDS doesnt patch the code (remove the vulnerability) - the insecure code is still there, just not active: as soon as RDS is enabled, the (unpatched) vulnerability can be exploited. There is a significant distinction between vulnerabilities and exploits - vulnerabilities are actual defects (bad code/code design) in the software (Window's RDP/RDS implementation) - exploits are the specific tools/processes that use the vulnerabilities for effect (DoS, privilege escalation, remote access, etc). The article you cited ambiguously references this distinction - the exploit tool ("the most common version of wannacry") was coded/designed in a way that that was mostly ineffective against XP remotely (locally it was just as effective). In other (specific) words, XP had the same SMB code vulnerability(ies) as later versions of Windows , but the specific implementation of EternalBlue via the most common WannaCry code was, ironically, buggy and defective relative to XP's SMB implemention, and thus was relatively ineffective (especially when executed remotely). This might have even been "intentional", since at the time of WannaCry XP's market share was in the single digits and the code may have been optimized for 7/8/10/2008/2012 (covering more than 90% of Windows installs). Buggy/flawed/defective exploit code is just as common as buggy/flawed/defective vulnerability code and often serves as a limiting factor in the propagation and spread of malware - going back as far as malware has existed, long prior to the existence of networks or the internet. In fact almost every "internet worm" of note was/has been vastly limited in its propagation and damage due to this often un/der-reported "buggy malware" fact. Malware/exploit authors are just as (if not more so) prone to write/design buggy/flawed/defective code as the original target code authors - and we can be thankful for that. Just imagine if malware authoring was an industry where highly efficient/effective exploit coding services were up for bidding by corporations, governments, criminal syndicates...oh..wait..never mind.

Dentists using XP should make discounted rates because they have not incurred upgrade costs Looking for an XP dentist starting today

Not sure if I can post this here, but... Here's the list of updates I've installed for .NET Framework 4.7.2: Not sure if that's all of them. It's based on my list of previously installed .NET 4.6.1, also have tried installing the older ones I had before, but all of them gave me the "not applicable to your system" error so I don't think there are any more updates to install, aside from the possible May 2019 ones, which I have yet to install. Also, it seems you can't install Language Packs since doing it the normal way yields yet another "not applicable to your os" error, and unpacking the installer with 7-zip and running the other installer (forgot its name) tells you to use setup.exe instead... Note: These are security and quality rollups, I don't know the update numbers for security only updates.

So, if this update is so crucial, why exactly aren't they pushing these updates automatically? Last I checked, Windows update service still works on Windows XP.