Vista: The update does not apply to your system

Hello GWN,

I've had boot time protection in NAV switched on for a couple of days now, and have also had NAV run a full system scan (with Windows launched in safe mode for a bit of extra belt and braces). NAV has reported a clean bill of health: no security threats, nothing. Is it still worth trying Malwarebytes 2.2.1?

If not, where next? The BSODs?

Thanks

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.

Hi JL3008:

Perhaps you misunderstood, but I did not recommend that you install and run Malwarebytes.  The current Malwarebytes 3.0 was just released a few weeks ago and has many known bugs listed <here> that were not fixed during beta testing.  If you accept the 14-day trial of real-time protection features during installation you could create a conflict your with Norton Security because of duplicated features (e.g., anti-exploit, malicious website protection).  Rootkits and bootkits often embed themselves deep in the Windows kernel, and if you run a custom rookit scan with Malwarebytes and it tries to automatically remove this type of infection there is a low but legitimate risk that the remediation could damage your Windows system files and leave your system unbootable.

There is a growing overlap these days between antivirus programs that specialize in detecting high-risk malware like virus and trojans that can damage your OS versus anti-malware programs like Malwarebytes (my personal preference) and SuperAntiSpyware that are better at detecting lower-risk infections like adware, browser redirectors, and other PUPs/PUMs (potentially unwanted programs/registry modifications). See the Lifehacker article *The Difference Between Antivirus and Anti-Malware (and Which to Use)* - it's an older article but still has some good advice on this topic.

If your Norton Security does not detect an infection you can't be 100% certain that your system is clean, especially if you use Norton's default settings and have boot-time protection disabled (Settings | Antivirus | Automatic Protection | Boot Time Protection) and have never scheduled a Full System Scan (Settings | Antivirus | Scans and Risks | Full System Scan | Configure).  I often recommend that Norton users run a second opinion on-demand scan with the free Malwarebytes Anti-Malware v2.2.1 (i.e., no real-time protection, no rootkit scan) if they are having performance problems like high CPU consumption or a browser that responds slowly, but your BSODs and failed System File Checker scan (sfc /scannow) indicate a more serious problem that likely can't be fixed by Malwarebytes.

I would still advise that you let a trained malware removal specialist run a thorough diagnostic over at the bleepingcomputer Virus, Trojan, Spyware, and Malware Removal Logs board.  They can help you safely remove any malware that might be on your system and might also flag out-of-date, insecure third-party software that could be causing a problem.

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

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

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

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 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.