Leaderboard

I think the only option now is to forget about any IE8 embedded Windows Update links, as they no longer work. They re-direct to the Windows Update FAQ page on the Microsoft support site, which no longer works at all in IE8. The address which now redirects doesn't seem to be stored in the registry, it's almost certainly hard coded. Just make a favourite or internet shortcut pointing to one of the addresses that heinoganda gave earlier.

To unzip an update for Windows XP, run the patch with the -x parameter. WindowsXP-KB4012598-x86-ENU.exe -x The binary delta compression does not work with conventional packers. The only difference I could find When comparing the srv.sys and xpsp4res.dll files in the SP3QFE folder of both updates, there was no difference! Current in May KB4012598 was replaced by KB4018466 (still additional security gap in SMB)! (Current Version from srv.sys 5.1.2600.7238 and xpsp4res.dll 5.1.2600.7238)

Today (May 15th 2017) I hunted down and installed all non-security and security Windows Updates destined for Windows Server 2008 SP2 32bit (that were published after April 11th 2017) onto my Windows Vista SP2 32bit laptop; together with security updates for .NET Framework 2.0 SP2, this is how it looks in the "Installed Updates" section of my WU: Further updates for installed .NET Framework 4.6.1 (not officially supported on either Vista SP2 nor WS 2008 SP2, but still installable on both these OSes, see here) were also hunted down and installed: So far, everything seems to be working as expected... @2008WindowsVista wrote: > I didn't try any updates related to .NET Framework, as I couldn't figure out how to obtain them. Well, my starting point for locating all Windows Updates is the following MS page: Description of Software Update Services and Windows Server Update Services changes in content for 2017 This gets updated in chronological order, whenever new updates are published... You can isolate WS 2008 SP2 updates and via the KB links you can hopefully arrive to individual WUC links (and pray that the catalog site isn't crawling like a worm...). Hence, for updates issued after April 11th 2017 (Vista's EOL), I have written down the following list of updates: April 18th (nonsecurity) Update for Windows Server 2008 (KB4015193) May 2nd Update for .NFW 2.0 SP2 on Windows Server 2008 (KB4020511) Update for .NFW 4.6[.1] on Windows Server 2008 (KB4020503) May 9th Cumulative Security Update for IE9 (KB4018271) Security Update for Windows Server 2008 (KB4018466) Security Update for Windows Server 2008 (KB4018556) Security Update for Windows Server 2008 (KB4018821) Security Update for Windows Server 2008 (KB4018885) Security Update for Windows Server 2008 (KB4018927) Security Update for Windows Server 2008 (KB4019149) Security Update for Windows Server 2008 (KB4019204) Security Update for Windows Server 2008 (KB4019206) (nonsecurity) Update for Windows Server 2008 (KB4020535) "Security Update for Windows Server 2008 (KB4018196)" does not install on (client) Vista SP2, because it strictly affects a Server function (Windows DNS Server Denial of Service Vulnerability in Microsoft Windows Server 2008: May 9, 2017); as for "Malicious Software Removal Tool - May 2017 (KB890830)", it has already been discussed in this thread... .NET Framework: May, 2017 Security Only Update for .NFW 2.0 SP2, 4.6[.1] on WS 2008 SP2 (KB4019109) => [Security Only Update for the .NFW 2.0 SP2 for WS 2008 SP2 (KB4014575) & Security Only Update for the .NFW 4.6[.1] for WS 2008 SP2 (KB4014591)] May, 2017 Security and Quality Rollup for .NFW 2.0 SP2, 4.6[.1] on WS 2008 SP2 (KB4019115) => [Security and Quality Rollup for the .NFW 2.0 SP2 for WS 2008 SP2 (KB4014502) & Security and Quality Rollup for the .NFW 4.6[.1] for WS2008 SP2 (KB4014511)] NB: If you install the "Security and Quality Rollup" bundle, you need not also install the standalone "Security Only Update"; if you have not yet moved to 4.6[.1] and are still on 4.5.2, you should locate the corresponding updates for that version of .NFW ! For future reference, I will conclude by posting some helpful (to me at least) links (with the hope the mods do not mind...) :

Go ahead. I don't know of any reason not to update Windows Installer to v4.5.

Sure. The OS interrogates the device to know sector size, issue is - generally speaking - that a number of components may ASSUME the disk block size to be 512 bytes, if there were not these assumptions, 4 Kb "native" drives would work nicely (BTW they do work nicely, only they cannot usually be booted). Though I doubt that it will actually help our friend to understand the matter, some not-so-unrelated info: http://www.msfn.org/board/topic/173265-formatting-an-external-drive-using-different-interfaces/ http://www.msfn.org/board/topic/173642-mkprilog-batch-to-access-a-same-disk-under-two-different-interfaces/ jaclaz

And here it is! The most awaited Vista repository with Server 2008 updates (atleast for the few people who care about the OS). Included in here are updates for both x86 and x64 architectures, and all versions of .NET available for Vista, from 2.0 to 4.6.1. If there's anything missing, do let me know. https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w I would like to direct a huge thank you to @VistaLover and @2008WindowsVista, for testing out the updates, and listing them in an easy to copy way

It means Home XP was provided with patch that blocks WannaCry spread via SMBv1 and not a bit more. Home XP got update from march. POSReady got new update in may, fixing another flaw.

That why it a good idea to buy another key to use it as a spare.

The only issue I've encountered so far is inability to set the theme with Settings app on Win10 Creators Update. The workarounds are described some posts back. Obviously the easiest solution might be waiting for new Aero Glass build and use its method for UxTSB.dll injection which should take care of these things automatically. If there are reliability issues with said method, the workaround is to have it sit on login screen for few seconds. Multiple user accounts or one password-protected account without enabling auto-login feature accomplishes that and allows things to settle.

Is Tommy just feeding Salt into our Wounds(tm)? :-D

Very soon.

You are correct - the last version of .NET Framework 4.x.x that would install on Vista (Home Premium SP2 x86 here) is 4.6.1; but the last version officially supported by MS on Vista is 4.6, so WU won't offer you to install 4.6.1 if you have 4.6 already installed; as I see it, if you have 4.5.2 installed, WU will find updates for 4.5.2 and offer an in-place upgrade to 4.6; if the upgrade is chosen and applied, only updates for 4.6 are found. The full standalone installer for 4.6.1 is file "NDP461-KB3102436-x86-x64-AllOS-ENU.exe" and can be fetched via MS Download Center; this will install fine on your fully patched Vista OS, replacing your previous .NET FW 4.x.x version and all of its updates. Sadly, as pointed out by @Mine Turtle, being an unsupported version means that WU won't be able to find any updates for it . One can always track down in MS Security Bulletins (now discontinued) or Microsoft Catalog individual updates for 4.6/4.6.1 destined for Windows 7 SP1, fetch them to disk and apply them manually... I am lucky with regards to the tracking part, because sister's laptop runs W7 SP1 x64 with .NET FW 4.6.1 (purposely not upgraded yet to 4.6.2) and I am monitoring what .NET FW updates this gets, write down their KB numbers and then download their x86 flavours and apply them manually in my Vista laptop. For anyone curious/needing those, here's a capture (via snipping tool) of the .NET Framework 4.6.1 section of my "Installed Updates" list (4.6.1 was manually installed last May): As for 4.6.2, its .EXE installer may have been "artificially" made incompatible with Vista or it may indeed be the case that 4.6.2 as a whole requires API functions not present in the Vista OS; really inapt to tell... And since v4.6/4.6.1 is still supported on W7, it may well be that future security/performance updates for 4.6/4.6.1 on W7 could be manually applied on Vista, too (unless MS plays it nasty and blocks them via an OS check switch or whatever ).