Leaderboard

@roytam1 and feodor2 are taking the trouble to compile and keep up-to-date and debugged the only real options of browsers for Vista and XP. And they're doing it for free (= gratis) just because they want to help and support the people's right to choose their OSes freely. If there is sheeple willing to ignore that and move on, despite their generous gifts, it's too bad for those sheeple, but I, for one, think neither ought to give half a damn about that. Just my 2¢, of course.

you will need either KB3020369 or KB3177467 servicing stack update installed first before installing newer updates beyond the KB3035131 and KB3033929 updates. go with KB3177467 as that one supersedes / replaces KB3020369. KB3035131 is an obsolete update as it is superseded / replaced by the KB3071756 update (MS15-085) for Win7 KB3071756 replaces KB3067505, KB3063858, KB3046049, KB3045999, KB3035131 updates

Naw I hear ya!

you want to download windows update mini tool and add it to control panel, you can find it on the mdl forums as well as other sites, but they are probably less trustworthy. disable auto updates and update when a full windows build goes public, that's what i do, i stopped bothering with updates sometime ago as they do not install properly on my machines, they always fail after the reboot with the annoying failure configuring updates error, been like that since 8.1, up to 8 updates usually installed fine without errors, only a few failed. Then something changed and updates fail to install, happened when ms switched to big chunky updates rather than small hotfixes.... the odd small update installs fine.

Well that's cool. I'll try some things later, maybe even test with XP too with some things. An 'extended kernel' or wrapper thing for Vista to make it use 7 functions, which could be probably easy to port, would be a great idea... just there's not enough demand I guess and I can't do anything as I barely know PHP lol

Yep, It took my PC BELOW TWO MINUTES to look for updates, and about 50 minutes to install 'em all with no error on the way. I'm glad it's fixed, I'm sad that just as POSReady updates are about to end. Good what ends well

@FranceBB Thanks for the info, will complement the entry in the config.ini for future updates on HTTPS proxy. This information helps to improve the functionality for all users of HTTPS Proxy. Annotation: Alone I can not test all websites / programs in this world for the function with HTTPS proxy.

Uau, Server 2008 now recieves Monthly Rollups and Security Only updates just like the rest of the big boys? I'm actually surprised! Now only Windows POSReady 2009 (XP) recieves individual updates. This actually makes my job easier Here's the page with the updates info: https://support.microsoft.com/en-us/help/4343218 More info on the subject: https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/ My theory - they changed the updating scheme to be like the rest of the supported Windows versions because of the paid support they're providing for any company who sticks with Server 2008 (https://aka.ms/eos-offer-faq) Anyway: Added Monthly Rollup, KB4458010 (located on the root directory of the repository) Added Security Only Update, KB4457984 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update KB4457426 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4457043 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4457038 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4457035 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Framework Security Only updates: -KB4457054 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security Only") -KB4457030 for .NET 4.5.2 (located in "/NET 4.5.2/Security Only") -KB4457027 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security Only") I think that's everything... Let me know if I missed anything! https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w

Also, looks like Firefox derivatives have already begun to drop support for Vista with the EOL of Firefox 52 ESR: https://www.torproject.org/download/download-easy.html.en Tor Browser v8.0 now requires Windows 7 or later as it is now based on Firefox 60 ESR. Probably won't be long before SeaMonkey (stable) drops support as well. If anyone is still using these browsers on Vista/XP, there's no better time than now to switch over to one of @roytam1's browsers, such as New Moon... Crazy to think that these are pretty much the only browsers that still receive updates on Vista/XP...

What you report does not sound "right" in the sense that if the USB has no drive letter, it should not be possible to install from it. Anyway you can usually pre-assign the USB stick drive letter, however, i.e. make it so that the USB gets - say - drive letter U: via migrate.inf, this is one among the many "special" features that some of the methods talked about here: https://msfn.org/board/forum/157-install-windows-from-usb/ provide, but nothing prevents you to use the same approach "manually". You will find details in the "historical" thread: but essentially all you need to know basically is here (via Wayback Machine): https://web.archive.org/web/20091125065150/http://www.911cd.net/forums//index.php?showtopic=19663 jaclaz

I am sorry to be the bearer of bad news, but if you're asking specifically for the Windows XP SP3 OS and the Spotify web player on a Mozilla type browser, there exist several serious reasons this isn't possible! 1, Spotify is one of the commercial media outlets that heavily use DRM for content protection; on Firefox and its forks, content decryption is delegated to CDMs (Content-Decryption-Modules), which are closed-source modules ("blackboxed") bundled with the open-source browser, to satisfy user watching/listening needs. 2. Mozilla had first incorporated Adobe Primetime CDM for the decryption of DRM'd content (a CDM familiar to XP users, as it is currently being "exploited" to enable h264/aac decoding support in the FxESR 52.x.x browser (... and some of its forks); this is not, however, a use intended initially by the Mozilla devs ), but that CDM was abolished in Fx 53.0+ in favour of the universally accepted, Google-owned, Widevine CDM. 3. As you probably know, all Mozilla browsers come without native support for patented decoders, like h264 (for video) and aac (for audio); if Mozilla went the "Google Chrome" way and bundled these decoders with Firefox, they'd have to pay annually huge sums of money as license fees to the patent holders (namely to the MPEG-LA group); they opted for a far less costly solution, that is to rely on system decoders (the ones bundled with the actual OS). 4. Speaking of Microsoft and the Windows OS, the first iteration of Windows with native h264/aac decoders came with the launch of Windows 7 OEM, though its predecessor OS, Windows Vista, was, too, equipped with similar support (be it less refined) when "Platform Update Supplement" for Vista SP2 was released via Windows Update.... Microsoft chose not to bestow h264/aac decoding support to Windows XP which is, in a way, the deal-breaker in your query... 5. Widevine CDM inside Firefox (or one of its forks) only executes decryption of the DRM'd media streams, the decrypted stream has then to be properly decoded to video and/or audio; Widevine in Firefox has been programmed to search for decoders only in the OS level (not the browser); remember that it is (very) closed source, this assumption is the result of tests only, no actual code for Widevine is, of course, publicly released... 6. Since Windows XP lacks native system decoders (and no, installed codec-packs don't work for Widevine), the Mozilla devs have disabled Widevine on XP, and only enabled it on Vista SP2 upwards; hence, minimum system requirements for services that employ Widevine on Firefox is WinVistaSP2+; however, since Vista has been EOL'd by Microsoft, this is currently read as Win7SP1+... 7. Specifically in the case of the Moonchild Productions' Pale Moon fork, because of their opposition to the closed-source nature of CDMs, they have purposely disabled DRM (CDMs) in the browser, so it's currently impossible to use DRM'd services (e.g Netflix, Amazon Prime etc.) in that browser, regardless of OS; the same holds true for New Moon 27+28, both Pale Moon forks... 8. Certain services that rely on Widevine did implement, at least in the past, a workaround when WV was absent in the browser, and that was to use the Microsoft owned Silverlight NPAPI browser plugin for both decryption+decoding; Silverlight has been deprecated by Microsoft and NPAPI plugins (except Adobe Flash) have been deprecated by all the major browser vendors, so using Silverlight in a browser as a WV fallback is pretty much a moot point; I am not subscribed to Spotify, so I can't be 100% sure it doesn't support Silverlight in Pale Moon (ergo New Moon); this chance is very bleak, if you ask me, though... 9. Of the rest of the "roytam1" browsers, excluding KM-Goanna and FxESR 45, only Serpent 52.9.0 and Serpent 55.0.0 were compiled with Widevine support, but, as stated previously, only if you are on Windows Vista SP2 or later; on XP, WV is disabled and doesn't show up inside about:plugins... (NB: Widevine on Serpent 55.0.0 on Windows Vista was initially non-functional (worked OK in Win7+), but this was rectified in https://github.com/roytam1/basilisk55/commit/cbc95b1 ; many thanks @roytam1 ) I wrote this analysis not only as an answer to your own query, but as a point of reference for other XP users... On XP, the only remedy I possibly see is trying to work things out with the last working version (49) of Google Chrome there; GC comes with its own version of patented decoders, and, AFAIK, has Widevine v1.4.8.903 inside; perhaps install an extension to fake a recent Chrome version to Spotify and see what comes out of it... Best of luck!