Leaderboard

Funny, I was about to post an update to the update repository Replaced Monthly Rollup with the new KB4507452 (located on the root directory of the repository) Added Security Only Update, KB4507461 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update with KB4507434 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4507003 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4507001 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4506997 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Security Only Updates with: -KB4506975 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security Only") -KB4506966 for .NET 4.5.2 (located in "/NET 4.5.2/Security Only") -KB4506963 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security Only") Added Extra update KB4508774 (located in "/Extras") with an updated readme. https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w BTW, I've seen demand for it, so I'm thinking of posting my Vista update repository that holds all of Vista's x86 and x64 updates from the beginning until its EOL (April 2017). Useful if you want to update your system offline without using WU. It's completely separate from this repository I'm updating every other month. Is there any interest?

ASPI has been historically not supported by MS (and delegated to Adaptec) and SPTI was used: https://web.archive.org/web/20140203072159/http://support.microsoft.com/kb/182542/en-us Adaptec is no more, and a quick search on the site www.adaptec.com resolves to: https://www.microsemi.com/ which gives no results for ASPI, but something can be found on https://storage.microsemi.com/ https://storage.microsemi.com/en-us/speed/software_pc/aspi/aspi_471a2_exe.php (I believe it is the latest ASPI version from Adaptec ) So, it is years that the FrogASPI exists, it is a mapping of ASPI commands to SPTI ones, at least on 32 bit systems it worked just fine, but in your case I would try to use the Starburn drivers (that have been tested on Windows 10 x64, at least in a VM, with success), see: http://wp.xin.at/archives/829 jaclaz

True. Luckily, ProxHTTPSProxyMII works with Office apps just as it does with "straight" IE8, Chrome, etc. It's nice that M$ added support for TLS 1.2 (and the AES cipher) while POSReady '09 was in support, but it's just not enough anymore.

https://tipsterarea.com/ requires SNI. The server probably hosts several Web sites with various host names. I don't believe IE8 supports SNI.

There were different variants for the MP10 and MP11, especially during the transition from sp2 to sp3. Now nobody knows in advance which of the variants of the MP the user has installed. An update that is not required for the existing version of the MP will not be installed anyway. I also have 2 variants of MP 11 available, where I tested it. In addition, I assume that a user, at the later time when AU / WU / MU is no longer available to install the updates via a control file. Hardly a user would like to install the mass of updates manually.

Only post SP2, but I do include the installers for SP1 and SP2. What I meant by "all" was also the hotfixes that Microsoft released that were not available in WU (more for x64 than x86, since I only managed to collect from MS's hotfix service before it closed for the former).

List of XP updates with description and links updated with corresponding findings of @ED_Sln and @heinoganda Do not contain .net installers and Microsoft Security Essentials (to be found in separate topic) @dencorso don't you think it should land at the beginning of the topic, to make the list visible? XP Updates2.zip

Welcome to MSFN forums The most recent WD defs file update that came through WU here was on July 6th: As you can see, the update frequency interval is between 2 to 3 days; I also haven't installed any of the SHA-2 updates yet; I usually tend to update WD manually, though, due to more frequent updates delivered that way (3 to 4 during a day...). I guess you could test yourself by leaving WD not (manually) updated for more than 3 days, while keeping WU itself enabled (e.g. notify but not auto-install updates); if nothing turns up after, say, 4-5 days, then you'll get confirmation WU it's broken... As for previous Vista updates, a more ominous rumour is flying around, that dedicated XP and Vista MS Update servers will be permanently shut down; see the relevant XP thread: https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/ XP die-hards have already started archiving XP updates from the Catalog, Web Archive and elsewhere, for future usage; haven't seen a similar effort undertaken from Vista communities; but I personally think we should be OK until Jan 2020, when both Server 2008 SP2 and Win7 SP1 reach Extended Support EOL; but I might be wrong...

Yeah, doesn't work here either