Vista: The update does not apply to your system

57 days & counting...

Hi JL3008:

Your main concern at the moment isn't that Vista SP2 will stop receiving security updates when extended support ends on 11-Apr-2017.  Your main concern is that your system hasn't received a security update for Vista SP2 or your IE9 browser since March 2016, so your system is already insecure and has been for almost a year.

If your BSODs are caused by faulty hardware that wasn't red-flagged in your Speccy profile, that still would not explain why System File Checker throws an error when you try to check the integrity of your system files, or why standalone .msu installers for important security updates that are missing from your system (including the latest cumulative security update for your IE9 browser) will not install.

Your Norton Security scan did not detect any malware, but that does not exclude the possibility that you are infected by a hidden rootkit or bootkit or some other malware [I run the occasional on-demand scan with Malwarebytes Anti-Malware to see if it can detect any potentially unwanted programs (PUPs) or malware missed by Norton].

Since you don't want to have the dump files from your BSODs analyzed, my only other suggestion is that you start a new topic in the bleepingcomputer Virus, Trojan, Spyware, and Malware Removal Logs board and have a trained malware removal specialist work with you one-on-one to see if you have any undetected malware on your computer.  Follow the Preparation Guide pinned at the top of that board that includes instructions on how to post a detailed diagnostic log generated with the Farbar Recovery Scan Tool (FRST). If the FRST diagnostic doesn't show any signs of a malware infection, it might still uncover the reason why System File Checker will not run on your system.  Once the malware removal specialist assigned to your case has confirmed that your system is clean you can come back to this thread and let us know their findings.

32-bit Vista Home Premium SP2 * Firefox v51.0.1 * NIS v22.9.0.68 * MBAM v2.2.1

HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Hello GWN,

I agree with you about what the main concern here is: it's the fact that I haven't had a successful update since June 2016, and not that support for Vista ends in a couple of months.

I also agree that I'm not sure the BSODs explain the failure of SFC. I'm more inclined to believe this is caused by some kind of corruption in the system files themselves, but, as you suggest, malware is also a possibility.

So: the plan. First up, I'm going to try the free version of the Malwarebytes Anti-malware to see if it finds anything. After that, I guess there are three possibilities: pursue the SFC failure; reset update components (following the instructions  here as far as possible, bearing in mind that they are for W7); pursue the BSOD (I'm happy to post a dump up to bleepingcomputer). Having not had a BSOD for some weeks, the PC obliged by throwing one yesterday (BAD_POOL_HEADER)! It's like it wants to be fixed.

I'm going to be away from the PC for a few days, so will start the process early next week. I'll post the outcome of the Malwarebytes scan up on here.

Many thanks.

Hello PA,

True. Fewer than 57 now. However, I woke up on the 1st January 2000 to find planes still flying, trains still running, phones still ringing and electricity still moving down wires. The threatened zombie apocalypse caused by evil mainframe programmers using short format dates just didn't happen. I'm pinning my hopes on a similar lack of Armageddon when Vista support ends. However, I'd just like to get it patched up as much as possible first.

I've got my fingers crossed!

Thanks

Hello PA,

True. Fewer than 57 now. However, I woke up on the 1st January 2000 to find planes still flying, trains still running, phones still ringing and electricity still moving down wires. The threatened zombie apocalypse caused by evil mainframe programmers using short format dates just didn't happen. I'm pinning my hopes on a similar lack of Armageddon when Vista support ends. However, I'd just like to get it patched up as much as possible first.

I've got my fingers crossed!

Thanks

no need to cross fingers

there was no NT3.1Pocalypse

there was no NT3.5xPocalypse

there was no NT4Pocalypse

there was no DOSPocalypse

there was no Win3.1xPocalypse

there was no 9x-MePocalypse

there was no 2KPocalypse

there was no XPocalypse

there will be no vistaPocalypse

there will be no Win7Pocalypse

there was no win8Pocalypse

there will be no win8.1Pocalypse

Problem In Chair Not In Computer

configure your network and system correctly and no problem

the worst problem with Vista

is requiring a fresh installation with MS Hologram Media to use AFD 4K:512e Sector HDD

Vista cannot be cloned to AFD HDD or restored from Factory Recovery Media to AFD HDD

• only exception is the Dell Vista Disc as it's not "recovery" media but a full OS installation disc

all others use an image based recovery which will have been built on 512Byte legacy HDD

as AFD didn't exist when Vista was RTM SP1 or SP2

ESENT is broken on Vista when the physical sector size changes

so when your HDD dies if you don't have an MS Hologram Media to use

you will not be able to reinstall on a modern AFD HDD

might get lucky with using SSD but AFD requires not using factory reset / recovery media, backup image or clone etc.

as to this other issue

one thing to test is if you can find a legacy 512Byte HDD or have MS Hologram Media

remove the current HDD and install another blank

perform a fresh installation

update SP2 with windows update disabled (set to "never check for updates")

with the following 6 patches

KB3078601

KB3109094

KB3185911

KB3191203

KB3203859

KB3204723

and windows update will not abuse CPU and RAM to get the remaining updates

if problems persist with  a fresh installation then the hardware is hooped