erpdude8

right, wyxchari. You don't need to worry about this until Jan. 2020. You can also view the contents of the MSU files for Win7 using 7zip, which I do almost frequently. I've also checked the new updates for Windows 8 Embedded Standard Edition and they have the similar "ApplicabilityInfo" for all editions of Win8.0, including the non-supported "Client" versions.

sadly the ASUS A7V8X-LA Kelut on the old Compaq computer died a few months ago. So I no longer have any "single core" CPUs left to use, except maybe an old hyperthreaded Intel Pentium 4 prescott (524) 3.06Ghz processor but that will require a different motherboard which I did find a few years ago and have installed a different board & the Intel P4 onto the Compaq computer. Edit 6/21: And it looks like new Win7 updates in 2018 will not be compatible with CPUs without SSE2 support (aka. Intel Pentium 3s, AMD Athlon XPs, VIA C3s) as Microsoft will not even attempt to make them compatible with non-SSE2 processors. Article on Computerworld about Microsoft "quietly" cutting off Win7 support for older Intel CPUs.

wow Markokk888. you did not mention the KB3172614 update in any of your posts, which permanently fixes the Windows Update Client problem under Windows 8.1 (MS support KB article 3163023). Fix was first included in KB3161606 and later included in KB3172614. manually download and install the KB3172614 update from the MS Update Catalog site (need either KB3021910 or KB3173424 servicing stack update installed first) and reboot. after Win8.1 reloads, run Windows Update.

read this (updated June 2018) https://www.computerworld.com/article/3199373/windows-pcs/windows-by-the-numbers-sanity-returns-as-windows-7-sheds-user-share.html

use an old PS2 style (non-USB) keyboard as the GA-Z97P-D3 board allows it

Microsoft removed a bunch of MUM files needed to install on Home/Pro editions of Win10 v1507 starting with KB4025338 and later cumulative updates and only install under Win10 v1507 LTSB 2015, which I use on one of my old PCs. LTSB rules and never gets any feature updates 🙂

Dalai is no longer maintaining it for Vista. the guide from the MS answers forum for Vista is great - I was actually missing the KB3205638 user32.dll security update on my Vista machine even though I already had KB4012583 and other updates installed. after installing that user32.dll KB3205638 fix along with having the latest gdi32.dll/gdiplus.dll & win32k.sys fixes installed, I did a WU scan and it took nearly 30 minutes to show available updates [almost 200 of them] for Vista instead of taking several hours. KB4048970 is replaced by KB4056944 (Jan. 2018) and KB4015380 (atmfd.dll) is superseded by KB4056941.

that's bad. a bent pin means a hardware problem and you need to take your mac pro laptop to a professional computer repair shop to have it fixed.

seriously, why would any XP user still be using it at SP2 + IE6 level nowadays? best to get XP to SP3 level

speaking of KB4019276, that patch should be available on Windows Update or Microsoft Update effective Jan. 16, 2018 (starting off as an Optional update in Jan. 2018 and in Feb. 2018 it'll be listed as a Recommended update). still requires a bunch of registry entries and other patched DLL files like crypt32.dll to enable the newer TLS protocols on XP

no sorry hapxhapx, you can not use the 2929781, 3161639 & 3042058 patches under Vista as those patches require Win7 (Server 2008 R2) or higher and will fail to install saying they're "not applicable to your computer". MS did not make any of those patches for Vista/Server 2008 R0 SP2. note to VistaLover (OP): the KB4019276 updates have been revised mid-November 2017 and there's also a KB4019276 patch available for POSReady 2009 users (ah for those still using XP). Download & install the "revised" KB4019276 patches, installing them on top of the older version.

although now the latest win32k.sys update for Windows Server 2008 (and possibly Vista) is KB4048970, released on November 14. Vista & Server 2008 users must continue applying the very latest win32k.sys & IE9 updates to speed up Windows Update searches.

well a Maxtor 80Gb hard drive might be more than big enough for XP, it seems almost small for later OSes like Vista & Win7. I got a used Compaq SR1303WM computer (with an ASUS A7V8X-LA Kelut board) using an AMD Athlon XP 3200+ (2.2Ghz) CPU with 2x1Gb Patriot RAM sticks and a Western Digital 120Gb 5400RPM hard drive (darn, shoulda put in a 7200RPM drive for faster HD access) running a 32bit Win7 Professional just fine with little or no lags. GPU I had on there was an nVidia Geforce 5200FX AGP 8x card and also had a LiteOn SHW-160P6S DVD writer.

you can forget about KB4015195 as it is superseded by KB4019204, which is actually made available for both Vista & Server 2008 this June 2017 on MS Update Catalog. In May 2017, KB4019204 was made available only for Windows Server 2008 but they actually work for both Vista & Server 2008. Open the KB4019204 MSU file (either windows6.0-kb4019204-x86_8301605396e05d4b8e2ee38fcb3cd801ad019cce.msu or windows6.0-kb4019204-x86-custom_cc1a90841c15759e36c5095580dfb0b32b34eb8a.msu) using 7zip, extract the "Windows6.0-KB4019204-x86-pkgProperties.txt" or "Windows6.0-KB4019204-x86-custom-pkgProperties.txt" file and read the ApplicabilityInfo line in that TXT file. It says "ApplicabilityInfo="Windows Vista SP2;Windows Server Core SP2;Windows Server 2008 SP2;", which means the KB4019204 packages can be installed onto both Vista and Server 2008.

why use that full Shockwave EXE installer when you can use the Shockwave Full MSI installer instead, which doesn't bundle the Norton stuff and no ads. the MSI install package is 2x bigger than the full EXE installer but the MSI package contains both Shockwave versions 10.4 & 12.2.

it's not a good idea to remove the posready registry entries after installing any posready specific updates - that will prevent installation of posready specific updates on your XP computer after removing the posready keys. best to leave the posready reg key alone

the WannaCry ransomware only infects Win7 based computers and NOT XP machines (whether KB4012598 for XP is installed or not): https://www.askwoody.com/2017/the-original-wannacry-does-not-infect-windows-xp-boxes/

KB2670838 is only required when installing either IE10 or IE11, not IE9. plus there's KB2834140, which provides a fix for KB2670838. KB2670838 is no longer "evil" - it was only evil when installed on laptops with hybrid or switchable amd/intel or nvidia/intel graphics adapters using outdated graphics drivers. updated graphics drivers were provided to OEM/PC manufacturers that were compatible with the KB2670838 update. to answer pointertovoid's question about servicing stack updates, install either KB3020369 or KB3177467 servicing stack update first before any other update.

Get Visual C++ Redistributable 2015 from MS Download Center instead of from Windows Update. these are probably newer than the ones found on WU. Also, you need to install updates KB2999226 and KB3118401 first before installing the VC+ Restributable 2015. If you can't install KB2999226 & KB3118401 thru Windows Update, try downloading them from either Microsoft Update Catalog or Microsoft Download Center.

but only a few. There's the KB3184143 update that removes alot of the Get Win10 free stuff.

The Win8 embedded standard updates made after Jan. 2016 can also be applied to the normal/client version of Win8 (so far). Open a Windows8-RT-KBxxxxx.MSU file in 7zip, and double-click on the corresponding "pkgProperties.txt" file and see this line: ApplicabilityInfo="Windows 8.0 Client;Windows 8.0 Embedded;Windows 8.0 Server;" that line means that an MSU update can be installed onto Win8.0 client, embedded & "server" editions (the last one being Windows Server 2012 R0)

KB2756872 is for Win8.0 only. KB2919355 is for Win8.1 only. I'd just install Win8.1 refresh over Win8.0 from a DVD or usb installation media that has the KB2919355 (update 1) and KB3000850 (update 3) already integrated; saves a lot of time and headaches.

thanks. though it can only install under an x64 edition of Win8.0 and there was no x86/32bit version available

Besides, installing the latest Flash Player ActiveX update for IE, install updates KB3173424 (July 2016 servicing stack) AND KB3172614 (July 2016 update rollup). The KB3172614 update won't install without having either KB3021910 or KB3173424 update installed first. KB3172614 updates the Windows Update Agent/Client app on Win8.1. to v7.9.9600.18340, which has the proper "optimizations" mentioned in Microsoft KB article 3163023. The updated WUA for Win8.1 from the KB3161606 and KB3172614 updates makes svchost.exe use LESS RAM and WU scans should take between 3 to 6 minutes. By the way, under Win8.0 (build 9200), always takes between 10 to 15 minutes AND gobbles up to 2 GIGs of RAM (I'm not joking) when checking for updates - I measured how svchost.exe eats up between 1.5Gb to 2Gb of RAM with Task Manager on the Details tab during WU scans (enable Columns "CPU Time" and "Peak working set (memory)" for Task Manager). Latest versions of the Windows Update Agent are v7.8.9200.17172 (GDR) & v7.8.9200.21289 (LDR/QFE) from KB3013767 December 2014 update rollup for Win8.0. Installing the newest flash player activex update for Win8.0 doesn't do much to speed up WU scans on Win8.0. Also the latest Flash Player ActiveX update is KB3201860, even for Win8.0 embedded standard - I downloaded this fix myself from MS Update Catalog and it CAN install on the "client" version of Win8.0, even if MS dropped support for the client version of Win8.0 on 1/12/2016.

That WUA app is v7.6.7600.320 for Win7 SP1, dencorso - that same package also includes v7.6.7600.256 for WinXP SP3, Vista SP2 & Win7 RTM/SP0 as I checked myself. That did nothing to solve the WU problem and is kinda outdated; but this newly released KB3161608 Update Rollup of June 2016 is what actually fixed the problem - KB3161608 updates the Windows Update Agent app to v7.6.7601.23453 and is now the latest version for Win7 SP1 Quote from Microsoft support KB article 3161647 - the KB3161647 fix is included in KB3161608: . Took Microsoft several months to finally figure out and resolve the WU problem on Win7.