Leaderboard

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190105-23937c6-uxp-7fcb7f544-xpmod.7z Browser-only Suite Win32 (removed due to request) source patch (excluding UXP): (removed due to request) Official repo changes since my last build: - [PLATFORM] Update commit pointer (56a95eb) - [PLATFORM] Update commit pointer (04bdb5d) - [PLATFORM] Update commit pointer (1c49fe8) - Update MacOS-files.in (5336c75) - Update Info.plist.in (b1bbad9) - Update Mac icons (3ea3912) - Update Mac icons (36a1864) - Update Mac icons (82bc1c4) - Merge pull request #61 from wicknix/TRUNK (0d6fdb4) - [MAIL] Attempt to add close.svg for macintosh (065f531) - Create README.md (faa1af7) - [PLATFORM] Update commit pointer (23937c6) For UXP changes please see above.

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190105-7fcb7f544-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190105-7fcb7f544-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20190105-7fcb7f544-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20190105-7fcb7f544-xpmod.7z Official repo changes since my last build: - [PALEMOON] Bug 1115369 - Use notifications instead of getViewItem for DownloadsView (a970e88a1) - [PALEMOON] Bug 1115971 - Don't fall back to the Places title for downloads without the target file name annotation (1b414c2b9) - [PALEMOON] Bug 1115972 - Don't fall back to the Places icon for downloads without the target file name annotation (8bd13f3a2) - [PALEMOON] Bug 1120429 - Remove unused code handling nodeAnnotationChanged (1eab01b24) - [PALEMOON] Bug 1115421 - Simplify download annotations handling in the Library (81265fae3) - [PALEMOON] Bug 1115983 - Keep only minimal state information in the DataItem (e666c9a8e) - [PALEMOON] Bug 1116176 - Create DownloadsHistoryDataItem and HistoryDownload objects (ac3159f02) - [PALEMOON] Bug 1115379 - Streamline DownloadsViewItemController construction and remove now unneeded identifiers (927853bde) - [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (f2f700514) - [PALEMOON] Bug 1117139 - Move code controlling the "download.xml" binding to a common place (downloadsViewCommon.js) (df852eca4) - [PALEMOON] Bug 1117141 - Part 1 of 2 - Bypass all the DownloadsDataItem properties (462332eee) - [PALEMOON] Bug 1117141 - Part 2 of 2 - Refactor notifications and remove the DownloadsDataItem object (d6c976bf6) - Fix typos (761b6eb25) - [PALEMOON] Bug 1127867 - Use the new back-end property to get the size of downloads asynchronously (beeede618) - [PALEMOON] Bug 1195279 - Fix typo in allDownloadsViewOverlay.js following landing of bug 1127867 (8cc3f3616) - [PALEMOON] Bug 1129896 - Part 1 of 2 - Keep cached metadata for history downloads indefinitely (0b15a2b89) - [PALEMOON] Bug 1129896 - Part 2 of 2 - Convert the shared front-end code to a JavaScript code module (551c6ff04) - [PALEMOON] Bug 1135348 - Fix about:downloads by adding missing XPCOMUtils imports (909c3ee13) - [PALEMOON] Initialize the search service asynchronously when calling 'BrowserSearch.addEngine()' (accd61429) - [FFmpeg] Use new decode API with recent FFmpeg version. (515e0794f) - [FFmpeg] Don't define AV_CODEC_ID_VPx with libavcodec 58 (68acfbb14) - Merge pull request #921 from trav90/media-work (5920c1dc6) - Avoid redefined macro warning in MediaFormatReader (7a39cd52e) - Merge pull request #922 from trav90/media-work (626d40774) - Merge pull request #920 from JustOff/PR_nsIBrowserSearchService_async_init_2 (bcf3df362) - Merge pull request #917 from janekptacijarabaci/_testBranch_pm_downloads_rewrite (78ad9498a) - Dont rely on 'this' staying alive long enough for getting favicons. (8a10092b5) - Add Comodo IS < 6.3 64-bit to the dll blocklist (517f50298) - Update UXP Coding Style guideline document (WIP) (eec3d00bb) - Update UXP Coding Style guideline document (WIP) (7a22921c2) - Update UXP Coding Style guideline document (WIP) (da0d462d6) - Use getElementBoundingRect and element.ownerGlobal in FormSubmitObserver (f543892e4) - Update HSTS preload list (483267ba9) - Make MAX_CSS_VAR_LENGTH unsigned to avoid warnings. (dfce7fa7b) - Remove proprietary constructor on AudioContext. (7fcb7f544) My changes since my last build: - update libaom to git rev c07e9d6ccf340843e8899e7da6b15a0893007bd5

Can confirm. I happened to have, miraculously, a copy of Steam from before the countdown update which still works with the servers. For now. Really hoping Valve doesn't pull a dick move and block access to the servers for older versions. Though I suppose they could still technically be used to run XP-friendly games as Steam does offer to run offline if it can't connect. It's true that some of the games on Steam which once supported XP get updates that cease compatibility. I've noticed this happen with some of the titles I own, to my chagrin. However, it's still worth it for the games that don't get such updates, especially for offline games. I'm currently having a problem with my computer (one of the motherboard RAM slots isn't keeping the chip secure and it's throwing bad data ... My hand may be forced and I may have to overhaul my desktop now) but once I can confirm my other RAM is working fine and my hard drive data is still valid, I'll see about preparing an archive if no one else does.

Since there's not much info out there on the web unless you spend a considerable amount of time googling, I thought i'd post the solution so more people can find it quickly. Update Late 2019: Several months after i posted this Microsoft fixed the problem but I believe it was a side effect of them updating their certificates due to an industry shift, so there’s no guarantee they will continue work in future also in the last update i mentioned a batch file, I ended up getting busy and my adhd made me forget, I’ll still post it once I get organised and find it again as it’s useful. Update: The latest problem with activation affects both XP and Vista however it’s relatively easy to fix, you need to update your root Certificates (The same issue causes problems browsing the net too) I have created a Batch script that will download and update the Root Certificates accordingly but it will be a couple of days before I can post it. Below is the Original Fix I posted Turns out it's exceedingly easy to restore Windows XP Online Activation Open the Start Menu Right Click on Internet and choose "Internet Properties" Goto the Advanced Tab Scroll down near the bottom to the Security Section and uncheck both: "Check for publisher's certificate revocation" "Check for server certificate revocation" Now you can activate online as normal or use the "Windows XP Product Key Change Tool" I would reccomend re-enabling both options afterwards even if you dont use Internet Exploder (which you REALLY REALLY should not be) If you’re still having problems: I highly recommend downloading the “Windows XP Product Key Change Tool” it’s an official Microsoft tool and you should be able to download it from majorgeeks worked in every other instance for me where the built in one didn’t. (And in think it also lets you use different type of keys from the media the OS was installed from, such as Retail on OEM and such) Also make sure your clock is set correctly (A common source of TLS problems)

I have gathered a large variety of updates, tweaks, other software / addons for XP x64 / 2k3 x64; of which I believe will or can be useful depending on the users needs. Now, I can't guarantee that I have all the updates are here but, I can at least offer what I have managed to collect. I hope that this collection helps some of you from at least having to hunt down some updates / software yourself. I have updates ranging from 2014 & lower, plus 2015 & 2017 along with some other enhancements, tweaks, and software. To clarify, I am absolutely not responsible for damages or incorrect usage of software / updates from this archive. PLEASE be careful & always make backups before proceeding with anything! Good luck! Sincerely, XP-x64-Lover Download Link: https://www.mediafire.com/file/q2d8qhynwdr6ad4/XPx64_%26_2k3x64_Updates_+_Tweaks_+_Other.7z/file Download Link (Screenshots of Archive contents): http://www.mediafire.com/file/50yi737yalhlaj3/Files_List_Screenshots.7z/file

Original January 4, 2019 post title was "Update IE8 to TLS1.2 for (nearly) Last Skype 7.36.0.150 on Windows XP". Update title changed May 1, 2019. Readers wanting Skype-specific info should page or find down to the ORIGINAL INTRODUCTION. UPDATE INTRODUCTION: This compiled procedure, Instructions To Add TLS1.2 To Windows XP OS & IE8, turns out to be useful for non-Skype purposes, and may now be obsolete for the intended purpose of running Windows XP Skype 7.36.0.150 (see posts below). For convenience of other readers, I've reorganized the original post so that the procedure steps now start near the top. I've also edited OS registry variations in steps 9A and 9B, made a change in step 11, and added a 12th procedure step, each helpfully noted by posters below. ----------------------------------------------------------------- INSTRUCTIONS TO ADD TLS1.2 TO WINDOWS XP OS & IE8 (Compiled from MSFN source posts credited) ----------------------------------------------------------------- 1) If not already updated, download and install Microsoft's updated Windows Installer 4.5 (KB942288-v3) from https://download.microsoft.com/download/2/6/1/261fca42-22c0-4f91-9451-0e0f2e08356d/WindowsXP-KB942288-v3-x86.exe 2) Set a System Restore point marked, say, "Spoof POSReady ID registry edit" 3) Put the following POSReady spoof text (omit the hyphen lines) in POSReady.txt, rename to POSReady.reg, right-click Merge, Yes. ---------- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 [<-- BLANK LINE] [<-- BLANK LINE] ---------- 4) Navigate to: https://www.catalog.update.microsoft.com/search.aspx?q=kb4019276 5) Find down to POSReady, Windows XP Embedded versions of KB4019276 Click Download button for that version. Click English in the opening language window (or other language). 6) Navigate to: https://www.catalog.update.microsoft.com/search.aspx?q=KB4230450 7) Find down to POSReady, Windows XP Embedded versions of KB4230450: Click Download button for that version. Click English in the opening language window (or other language). 8) For each KB file: click, accept install, reboot. (Both create restore points just in case.) 9) Edit the following Windows XP registry entries in 9A and 9B to read as shown. If you aren't sure how, look up Regedit 5 editor instructions. For convenient automatic registry edit-merge, these lines may be pasted into Notepad text files, renamed .reg ,then just click the file after closing it (expect no response). (But to be careful, I edited them manually with Regedit 5.) 9A) After navigating the chain of registry keys, click the key TLS1.1, in the right panel, right-click "OSVersion", click Modify, enter the Value data already shown (not sure why), click OK. (I had to change "3.6.1.0.0" to "3.5.1.0.0" shown in obvious German in the source.) (EDIT: Other posters report below that if this key is absent, this step may be safely skipped.) ---------- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"="3.5.1.0.0" ---------- 9B) Next click the key TLS1.2, in the right panel, right-click "OSVersion", click Modify, enter the Value data shown above, click OK. (Likewise I had to change "3.6.1.0.0" to "3.5.1.0.0") (EDIT: Likewise, if missing, skip this step.) ---------- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"="3.5.1.0.0" ---------- 10) Click Start, hover Control Panel, click Internet Options, Advanced tab, pull the thumb bar all the way down. You should see new checkbox options for "Use TLS 1.1", "Use TLS 1.2". (KB4230450 will install these checkboxes, but they won't work without KB4019276.) 11) Check "Use TLS 1.2". Leave unchecked "Use TLS 1.1" (already obsoleted by TLS 1.2; and, TLS 1.3 was approved in 2018). (EDIT:) Leave checked "Use TLS 1.0". Click OK. The TLS 1.0's AES component is not insecure. TLS 1.0 may best remain checked for legacy websites needing AES or 3DES. (See explainers in posts below.) 12) (EDIT:) The following registry edits disable TLS 1.0's insecure cipher suites: DES, RC2, RC4, plus the insecure MD5 cipher hash. 3DES may be disabled optionally, but legacy websites without AES may need 3DES (Triple DES). TLS 1.0's secure cipher suite AES remains enabled, unchanged (no edit shown). Edit the following registry entries to read as shown: ---------- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\DES 56/56] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 128/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 56/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128] "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\MD5] "Enabled"=dword:00000000 ---------- You may need Triple DES (3DES) at websites which don't (yet) support AES. Here is the optional edit (not yet recommended) to disable 3DES (0's mean Not "Enabled", equals Disabled): ---------- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\Triple DES 168/168] "Enabled"=dword:00000000 ---------- The above registry edits (manual for transparency) are included in a larger set of one-click automatic edits in a download .reg file posted below. Pardon any source text compiling errors. If you have problems, try reading the sources (long). Source posts credited: ● https://msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/ POSReady 2009 updates ported to Windows XP SP3 ENU By glnz, March 19, 2013 in Windows XP ● https://msfn.org/board/topic/177500-upgrading-ie8-to-tls-12/ Upgrading IE8 to TLS 1.2 By Thomas S., June 9, 2018 in Windows XP ● https://msfn.org/board/topic/178087-update-ie8-to-tls12-for-nearly-last-skype-7360150-on-windows-xp/ Update IE8 to TLS1.2 for (nearly) Last Skype 7.36.0.150 on Windows XP By Mathwiz, January 4, 2019 in Windows XP ---------- ORIGINAL INTRODUCTION: I'm posting a step-by-step fix to add TLS1.2 to IE8, so that Skype 7.36.0.150 (for a few months did) run on Windows XP-SP3. (While 7.41.x.x may be actual "last" for WinXP, it may or not nag you to "update", requiring a separate fix or version downgrade. My version 7.36 didn't get the nag, and 7.40 was also reported to lack the nag when it mattered before April 12.) I've compiled pieces of the fix puzzle I found elsewhere on MSFN, because the complete fix isn't obvious to WinXP Skypers searching from elsewhere on the web. The fix isn't that difficult, but the usual warnings that novices should back up the registry before editing it, do apply. The download KB file installs, and each set their own restore points. I hope just setting a Restore point before starting the edit will be adequate. I haven't used my desktop PC WinXP-SP3 Skype (mostly chat) for months while the power supply was down. Yesterday I fixed it. To my surprise, Skype errored with "Sorry, we couldn't connect to Skype. Please check your Internet connection and try again." But the internet was ok. Many Skypers aren't techies, and most of the posted complaints about "Sorry, we couldn't connect to Skype", don't have a fix other than get a new OS like Win7, or use web Skype. For good reasons, we don't want to give up WinXP, at least as a backup to Win7 (or even Win8.1 for my keytablet). I've thoroughly tested Win10, but I'm not interested in that control-freak bugfest. One elsewhere-posted answer with no fix, helpfully explained that Skype had switched to using the more secure https encryption protocol TLS1.2. Skype for WinXP uses the SSL/TLS protocols built into Internet Explorer 8, which is the last Internet Explorer version for WinXP. IE8 normally has a maximum version of TLS1.0. Skype servers apparently turned off insecure TLS 1.0 sometime after I had to quit using this Skype last year (2018). So the fix is to add TLS1.2 to IE8, and it did work for me. At MSFN I found the bitter-end holdouts on WinXP, same website where I found the Win98 bitter-enders. (Btw, one poster at MSFN said the famous Windows OS bitter-ender AXCEL216 aka MDGx aka George, is still alive!). One or more MSFN gurus noticed that Microsoft is still updating Windows XP embedded OS for computerized cash registers (etc.), a WinXP variant known as "POSReady" (POS= Point Of Sale). They figured out how to spoof WinXP-SP3's identity, so that it will pose as, and accept POSReady updates, including those which to add TLS1.2 to IE8. (If still relevant to Skype readers, do the procedure above. Even if another post-April 12 Skype for XP fix is found, this procedure will likely be needed as well.) When I did this procedure (in January of 2019), the "we couldn't connect to Skype" error went away. However, a new sub-login dialog appeared that only allows a Microsoft school or business account. This dialog went away after I clicked on an existing chat account. (See new Skype 7 login obsolescence described in posts below, first reported elsewhere as of about April 12, 2019.) I hope this helps. Al

Of course.

vt6212,VT6202, there is other chips tho besides that one that VIA made that work on 98 and osr2.1

... I can reproduce; I had to temporarily switch to the default theme (am using Dark Moon 2.3.0 otherwise) to notice it more clearly: for a fraction of a second, the embedded search bar (in the middle of about:home) appears truncated (i.e. shorter) when about:home is loaded for the first time, but then auto-resumes its normal length... NB that when DDG is set as the default search engine (which is the default setting), the search bar is shorter, because it is prepended by the DDG icon (at least in the default theme); when other search engines are user-selected, these come with no icon and an elongated search bar... The changelog between buildID=20181221223321 and buildID=20181228225818 (for 32-bit) is: https://github.com/MoonchildProductions/UXP/compare/ba81aaf...83cd966 The one relevant commit that easily stands out appears to be: [PALEMOON] Initialize the search service asynchronously from 'about:home' and 'about:newtab' : https://github.com/MoonchildProductions/UXP/commit/cb2f0f614362d3e986d585d6d1b4a2eaa20a1365 Hope your query is answered

With all due respect, let me tell you what: ProxHTTPSProxyMII (available from @heinoganda by request via PM) provides full certificates (ciphers) and TLS 1.1/1.2 (although the latest updates have now solved the TLS issue) for both IE8 and other browsers (esp. Chrome 49). Thence, Chrome 49 / ProxHTTPSProxyMII fully solve the HTML5 issue. @roytam1's New Moon and Basilisk/UXP (best, IMO) also do solve the HTML5 and cipher issue, not requiring the addition of ProxHTTPSProxyMII. So I think we're pretty well covered on this matter. IMO there isn't any real HTML5 / cipher / TLS issue with XP at the moment. Moreover, @heinoganda also has been providing a certificate updater for the root cerificates and a flash updater specific for Chrome 49, allowing it to remain easy to use and functinal. Using IE8 just for MU/WU and either the latest Basilisk/UXP or Chrome 49 / ProxHTTPSProxyMII has provided me a fully satisfactory browsing experience up to now, and I bet it'll continue so for as long as @heinoganda and @roytam1 kindly keep on supporting the community with their awesome work.

Windows 8.0 sure doesn't get any love... To remedy this, I've got a big repository update for ya! Brace yourselves, it's gonna be a big post. Here's the usual: Replaced Monthly Rollup with the new KB4471330 (located on the root directory of the repository) Replaced Flash Player Security update with KB4471331 (located on the root directory of the repository) Added Security Only Update, KB4471326 (located in the folder "/Security Only (Post September 2016)") Replaced Internet Explorer Cumulative Update KB4483187 (located in the folder "/Security Only (Post September 2016)") Replaced .NET Framework Security and Quality with: -KB4470629 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security and Quality Rollup") -KB4470623 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security and Quality Rollup") -KB4470638 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security and Quality Rollup") Added .NET Framework September Security Only Updates: -KB4470601 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates/Security Only Updates") -KB4470492 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates/Security Only Updates") -KB4470492 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates/Security Only Updates") Also decided to install Server 2012 on a VM where I installed all of Windows 8.0 EOL updates and searched WU for the remaining updates. This was the result: A bunch of non security updates that I didn't include on my repository! I have fixed this, so here's a more detailed list: KB3055343 - Stop error code 0xD1, 0x139, or 0x3B and cluster nodes go down in Windows Server 2012 R2 or Windows Server 2012 KB3102429 - Update that supports Azerbaijani Manat and Georgian Lari currency symbols in Windows KB3125424 - LSASS deadlocks cause Windows Server 2012 R2 or Windows Server 2012 not to respond KB3137061 - Windows Azure VMs don't recover from a network outage and data corruption issues occur KB3137726 - "VSS_E_PROVIDER_VETO" error occurs when VSS restore fails in Windows Server 2012 KB3137916 - "0x00000027" Stop error and unexpected restart in Windows Server 2012 KB3138378 - Update for Journal.dll binary in Windows KB3147071 - Connection to Oracle database fails when you use Microsoft ODBC or OLE DB Driver for Oracle or Microsoft DTC in Windows Do note that even though the description for these updates makes it seem as these are fixes specific to Server 2012 they also apply to Windows 8.0 (in some of the KB they specifically say it also applies to Windows 8 Embedded, not to mention some of the updates are also available for W7 and W8.1) There's also an important update I didn't include in the list, because I thought it is too important to not be mentioned exclusively. That is: KB3140245 - Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows As you can see, adding support to new security protocols seems important in keeping Windows 8.0 relevant and up to date. You do need to do a few extra steps to fully enable the update's functionality, so I've included a folder with everything you need in the repository. All of the updates I've mentioned so far are in the Extras folder, in case you want to install them. Available in both x64 and x86 flavors https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ

You mean ReactOS? You can try it, but it's nowhere close to a proper fully functional and updated OS, as its compatibility is Windows 2000/Windows XP, while it should really be at least Win7 to be considered functional these days. Anyway, I do understand that it's really difficult for developers to develop ReactOS without infringing any copyright, that's why it's very much based on Linux implementations like Mono and Wine that have been developed for years, but are still far from being perfect. An antivirus software that does its job is required as well. Whenever other people connect to your computer for any kind of reasons (like p2p) or whenever you visit a new website that you don't know or whenever one of your friends/coworker/family members/existing human being plugs in a USB Stick/Hard Drive there's a chance you can get infected. I strongly suggest you Avast, which will cover up any eventual new security issue, but keep in mind that an antivirus is not a cure for security vulnerabilities: if a new vulnerability is found and support is over, it will never be patched, which means that the Antivirus will try to block any threat that tries to use that vulnerability, but if it doesn't, the threat will successfully exploit it. There are rumours about the Microsoft Premium Support program. This type of support is aimed to keep businesses secure with constant support from Microsoft engineers and updates for the products used (to a certain extent). Will it include Windows XP and Server 2003 machines? It's likely Microsoft will continue to support XP and its derivatives as they are already supporting it (remember that businesses using XP weren't able to apply the POSReady registry entry and they are paying Microsoft for the Premium Support). In a nutshell: - Will Microsoft still support XP? Yes, it's very likely they will via their Premium Support program. - How much will it cost? You can ask Microsoft yourself by requesting a price quotation for your business at Microsoft, but it seems that it's going to be around $15000 per year. - Can a private and not a business apply? I have no idea, ask Microsoft. - Is it worth it? For private people who don't own a company like us, I think it's not. - Are there going to be exceptions? There might be exceptions if the security vulnerability found is really important and they might release an update for us all for free as they did for WannaCry. (But this is my assumption, so there's no guarantee they will). - Is there a chance that updates will be leaked by a hero wearing a cape? Very unlikely, as it would mean the immediate loss of support by Microsoft, a significant fee and prosecution. Nobody would be so stupid to risk it and even if some miracle patch appears by someone unknown, would you trust it? (I wouldn't). Last but not least, the main problem for XP users will be the compatibility with newer protocols like TLS 1.3, certificate handling like ECC, the new version of the .NET Framework, the .NET Core and so on. These are highly unlikely they'll ever be ported on XP, despite the fact that Microsoft said that they were working on supporting ECC months ago, but they kept it quiet and they didn't really talk about it, which makes me think that something went wrong down the road. I'm an encoder and a developer myself and I find incredibly difficult to support XP nowadays unless you are using C++ or using old version of a programming language like C#. For instance, I generally develop Windows programmes in C# using Windows Form and targeting .NET Framework 4, which is XP compatible, but not only new features of C# and SQL don't support XP, Microsoft doesn't even encourage to develop using it anymore as it wants you to use UWP with C# and XAML, using the .NET Core and Blend (for design) for cross platform compatibility at the expense of breaking compatibility with old version of Windows 10 (Legacy Windows like Win8.1 and lower are not supported). I've been recently asked to develop a programme this way so that they were able to distribute it as an App for tablets and phones. What about XP? Well, it will die a slow death as you will still be able to use it up to a point in which it will become unusable as nothing will work on it and even opening a simple internet page will almost be impossible.

I don't think so.... XP' market share was big enough when they dropped the support for XP. I'm not afraid for the lack of Windows updates. without support a web browser becomes totally unusable like IE6

Steam still works without changing the date or -noverifyfiles for me

The end of official support doesn’t render the operating system unusable. As long as you’re connected to the Internet behind a router with a firewall, and browsing the internet responsibly on an updated browser, there is no reason why you can’t continue using XP without an issue. I have no intention of giving it up any time soon.

Lets hope MSFN XP Masters will port Server 2008 updates on XP and it would live on for more. I never had a chance to eXPierence XP on its heyday since i was a Windows 7 user...

I just came back to XP this year, as I’ve become jaded by the direction MS is going in with Windows.

For Steam: Source: (It says wine on the page but the fix is the same)

I'm running Steam on my Windows XP x64 machine, using -noverifyfiles command since Valve break x64 support in Steam in mid-2017 (64-bit games like "Cities: Skylines" stop working in june-august 2017). Its working fine now, exept some bugs in Store, but you can always use Steam-web.

Unnecessary Post.

I have been away for quite some time, due to being ill but, my health is improving and I hope to be more active on here in the future. For now, I have written a simple Step By Step Guide for you. I claim absolutely no responsibility for incorrect use of my instructions resulting; in damage of any kind. It is up to you to be careful; there is always risks involved when installing or setting up anything. Please do be careful. First before all else, make at least one backup image of your Windows XP Professional x64 Edition install; if you don't know how I would be happy to show you ways in which to do so. One way in particular is to use a program called MiniTool Partition Wizard Free, Or any other partition software that allows you to make bootable image backups of your Operating System. You will be needing an extra HDD or SSD handy to copy it over to but, you can use USB interface or SATA / E-SATA or whatever interface you believe will work to copy it over. SATA / E-SATA is typically faster and is the most compatible in most cases. You should do this on a previous computer you have around though. To do this using MiniTool Partition Wizard Free you launch the application then select your bootable Windows XP Professional x64 Edition disk from the list. After that you need to click on Migrate OS to SSD/HD Wizard; then you select option B "I would like to move my operating system to another hard disk. And keep the original hard disk in my computer." Although, if you have multiple partitions on your disk, then select option A otherwise go with option B. After that you simply select the destination SSD or HDD you want to copy your bootable system image to. The destination disk will obviously be overwritten so keep that in mind. Make sure to backup any files you may have on it before you start the system disk copy. So, today I'm going to explain how I personally managed to get Windows XP Professional x64 Edition running on the ASUS SABERTOOTH x99 Motherboard with the on board SATA AHCI / RAID enabled. This Guide is intended to be rather simple and I do hope it is helpful to you. To speculate, it should boot through regular IDE with the default IDE drivers within the Operating System, as long as you have IDE enabled; although in this case it is not totally relevant to AHCI / RAID because we need them to be enabled within the Operating System in order to install the drivers via a special method below. Although, It may be possible to have IDE enabled on one of the two storage controllers and have AHCI enabled on the other; with the boot device plugged into the IDE mode storage controller. Then you'd install the AHCI driver within the Operating System that booted through IDE mode; after that you switch your boot device to the AHCI controller and simply go into the BIOS / UEFI and change the IDE mode to AHCI. Although, I cannot say this with certainty but, it could theoretically work if done correctly. This is mainly in case you can't afford another SATA Card or desire an alternative method. I have not truly tested the IDE method. The only current way I've managed to get it to boot via AHCI / RAID is to use a previous install of Windows XP Professional x64 Edition. (It may ask you to activate Windows again though, so make sure you are prepared for that in advance). If you have a Volume License copy of Windows XP Professional x64 Edition then you need not worry about being prompted to activate at anytime. Now, in order to get the Intel AHCI / RAID drivers to work, you must first have an extra SATA controller; you can do this by using a third party PCI-E x1 SATA Card by Marvell or any other SATA cards compatible with Windows XP Professional x64 Edition. (I used Marvell SI-PEX40065). Now, the drivers for the Third Party SATA Card must be installed before you can boot from it. To do this, simply use your previous computer or any handy / compatible computer you got nearby. Make sure to install the Third Party SATA Card Drivers once you have booted into your previous / other computer. After that, shutdown and then put your boot device (HDD or SSD). back into the computer case with the ASUS SABERTOOTH x99 Motherboard; then plug your boot device into the Third Party SATA Card. After that is done, turn the computer on and go ahead and enter your BIOS / UEFI using either the delete key or the F2 key. From there you'll navigate to Advanced then to PCH Storage Configuration; next change SATA Controller 1 to AHCI or RAID depending on your needs, in this case I recommend using AHCI if you've never setup a RAID before or are unsure on which to use for simply booting your device. For beginners I recommend AHCI; and if in the future you want to build a RAID then do so wisely. (I have a RAID setup for my two SSD's in RAID-0, it was fairly painless to setup but, I employ you to always have one or even two backups of your original Operating System aka Windows XP Professional x64 Edition. Then scroll down more and also change SATA Controller 2 to AHCI. (The second Intel Storage Controller does not support RAID). This Guide and it's steps also can apply to Windows XP Professional 32-bit and other 32-bit versions of Windows XP. Although, make sure to use the correct 32-bit Drivers for your devices to avoid issues; and as always backups are essential. Now, once you've booted into the Operating System yu'll notice 'New Hardware' to be installed, what yu'll do next is simply use Device Manager to manually install the SATA Controller Drivers from the SATA Drivers I provided you; the ones in which correspond to AHCI for now. Then yu'll need to restart but, in this case shut down instead; so that you may unplug your boot device from the Third Party SATA Card and then plug it into the one of the two On board Intel SATA Controllers. Also, be sure that your boot device is set for first priority booting, otherwise the BIOS / UEFI may not boot it. Plus, yu'll need to make sure CSM is enabled and configured for legacy boot. I do hope this simple Guide was helpful in some way; and if not please do let me know what you need explained further. Also, I hope you all have a great day and rest of the year on; take care! Good luck & Enjoy!! Sincerely, - XP-x64-Lover