Windows defender does not update vista

There really should be no reason why anyone running Vista today could not successfully continue to keep it completely up-to-date by applying Server updates starting in May until January and even Server ESU updates starting in February until now.

Defender will still not update but there are always other free AV products that would be able to fill in this void quite nicely. FWIW, I think this is another wise decision on your part as well. As you saw, some of the questions you had were subsequently taken care of. Earlier, I had tried version When I got to the end of that DOS box and the updater claimed3 of the 5 updates had installed successfully, I was very hopeful, but then we had another black screen on reboot.

According to the Update History, once again KB failed to actually install. I agree with you on trying to get the Vista laptop up to date as much as possible. BTW both Vista systems have Norton on them, and Norton has announced they will stop issuing new virus definitions for Vista and XP sometime early in As my N subscription expires in December, I already have a replacement lined up: Panda Dome , which is still advertised as compatible with Vista. As noted in that MS Answers thread:.

To confirm that KB rel. Oct , KB rel. Sep and KB rel. At the end of the day this is just a side discussion to your problem.

The original point I was trying to make is that ESR v9. As you pointed out in your explanation, indeed it is the case that the Vista laptop was reinstalled more recently; IIRC, some years ago I had installed some. That was an incentive to start making image backups on a regular basis.

The tower has every one of the patches mentioned in the previous sentence. I would add that perhaps you might want to run this version without the NVIDIA card installed in the event WSUS is able to find and install any missing updates to see if the reboot is also successful. I would also suggest you try to run v9. OK, I tried v9. These missing trust certificates can also prevent Vista SP2 users with Norton antivirus products from upgrading to the latest Norton v From what I understand, an alternate way to add these missing trust certificates on both Win XP and Vista machines is to run the rootsupd.

I exchanged a few PMs with a Norton employee on this topic and suspect that ongoing issues with trust certificates on older OSs is one of the main reasons why Norton announced on Sep that they will discontinue support for Win XP and Vista in early Wondering if I should try instead the method involving rootsupd.

Not to throw even more balls up in the air, but I can report that both of my Vista x64 machines do have Norton version Neither system has KB installed. I drag that machine into this sorry mess to list the following data bits about it, in case they are relevant:. This machine has not received that I remember any Server updates. This experience persuaded me to stop spending time trying to keep these tertiary and quaternary systems up to date with Server patches, as the effort-to-reward ratio was poor.

Go figure. I have same issues with WD…. Windows Defender Version: 1. You have the last engine version that was compatible with Vista, fellow anonymous poster. Still, you might be interested in a link that was posted by Imacri in a September 17 reply to 7ProSP1 above. None of the posters here seem to have noticed that VistaLover was able to update definitions without updating the engine. Some time around Aug Microsoft started bundling the mpas-fe. As far as I know, your problem with the Vista desktop that boots into a black screen as soon as a Win Server updates changes the build to v6.

This thread has piqued my interest, and I have done some tests on a Windows Vista x64 VMware virtual machine.

The virtual machine is patched to June including the 5 updates released after the end of extended support for Vista. The build version of Vista is 6. Specified updates below are all supposedly for Windows Server but can all be installed on Windows Vista. Build version of Vista changed to 6.

Returned error EFD. Refused to install. This is just a little test but from this experience I am forced to agree with Imacri that we may no longer be able to install Windows Defender updates on Windows Vista even though the necessary SHA-2 updates appears to be successfully installed. Out of curiosity I also took a Windows Server x64 VMware virtual machine and did a test to see what will happen.

The virtual machine was patched to August just before the change to the rollup model in September Available updates were displayed. I stand corrected. Thank you for pointing out my error. The latest mpas-fe.

So how exactly does VistaLover use newer mpas-fe. Instead of running the mpas-fe. I just tried extracting the individual files from the latest mpas-fe. Did this on both the tower and the laptop. There was no visible change: Defender is still stuck on old definition versions. Question: did you unregister the old. If you install a program, it registers the. But if you are just swapping files, you may have to reregister.

Usually, you unregister the old version, then remove it. Then you replace it with the newer version and regsvr32 registers the newer version that is in the path you give it. In this folder there are four subfolders, the first of which is named with a seemingly random sequence of alphanumeric characters inside curly brackets, the second one named Backup, the third one Default, and the last one Updates.

The Default subfolder has three files from and The Backups subfolder has more recent stuff, including mpengine. The randomly-named subfolder contains three files with those same names, but from July 9, The August 3 date used to show up there, until I started trying to update WD unsuccessfully just prior to starting this thread. The mpengine. So, if I understand your instructions correctly, I would 1 unregister mpengine.

Unregister, remove, replace, register. I navigated to the randomly-named Definitions Updates subfolder and tried to unregister mpengine. This is what happened:. Maybe I should try the method outlined by Anonymous below , it may involve fewer minefields to navigate. Im the one with the offi not updating…so i managed to show my WD updated.. Let u know if succeed. There are currently links there for the August updates e. I personally prefer to use the self-extracting.

I replace in backup and the other long folder…just in case i backup that old definition folder restart wd service note: after wd restart i didnt see a change.. We shall see for how long this method keeps working maybe until Redmond sees this thread , but for now it looks like we have a solution. For the Vista tower, I did not even need to reboot the machine. Just make sure to place the two new. I was briefly back at the August 3 definitions that, early on in this thread, had seemed to disappear in favor of the July 9 definitions, until I put the September 24 defs in both subfolders.

I am LK the off guy …thanks Imacri.. Cyber…good to hear that worked ok both folder were to do the job.. Other anonymous poster here. Glad this thread finally got somewhere. Congratulations, Cybertooth! Your persistence has paid off.

A huge and sincere thank you to lmacri , our two anonymous posters, James Bond , PKCano and EP for their insightful and excellent contributions in helping Cybertooth solve this incredibly frustrating dilemma. I know I have certainly learned a great deal from this problem solving journey. I, too, learned a lot from the discussion. And I will absolutely take your advice to leave the Vista tower alone from here on out!

BTW, this morning the Vista laptop also successfully updated the Windows Defender definitions via the same method that worked for the tower. This parameter you can also find in MpSigStub. Just to let you know, today I just have checked winupdates and have available the september of updates i downloaded from catalog b4 but didnt installed them at that time..

From what I understand, the expected fix abbodi86 mentioned in reply is a new Windows Defender engine mpengine. Ceteris paribus, here is, in my opinion, an excellent synopsis from September 25, by VistaLover at MSFN of why Defender stopped updating its definitions on Vista SP2 and how to keep updating said definitions for the time being. Until, hopefully, an official forthcoming fix is released by Microsoft at the beginning of October as mentioned by abbodi86 above.

From October 31, , here is a continuation of the above, again by VistaLover at MSFN, providing yet another well-detailed synopsis of how Microsoft messed up and subsequently resolved this issue thereby allowing Vista SP2 users to update their Windows Defender definitions once again. Well I just updated successfully the WD running the mpas-fe.

I just tried manual updates, and both failed. FWIW, the Vista laptop failed with error 0xj while the Vista tower failed with error 0xefd. Both are still using definition version 1. I then tried to manually install mpas-fe.

Curiously, Norton flagged it as unknown and offered to kill it, something it had never done before with mpas-fe. But—even stranger—it offered to do this only on the tower, not on the laptop which has the same Norton program installed.

They are now on engine version 1. The release notes for the previous v1. Again mpas-fe not working, but this time because the MpSigStub has changed version…and that break the mpas executable..

What happens when you test with the latest available mpas-fe. For other users just joining this thread, mpas-fe. Hi lmacri , I can confirm that downloading the latest Defender definitions from Microsoft, then right-clicking on the file to Run as Administrator, does work.

Both my Vista tower and Vista laptop now have Definition version 1. Thank you so much for staying on top of this, and to Microsoft for fixing the newest installation problem.

While my head is still spinning from all discussion regarding the problems you were having when attempting to move your Vista desktop to Build while your Vista laptop had no such issues , and while I am also not trying to stir it all up again, I am both happy to hear this and completely baffled you were able to install the new WD Definitions and Engine to both systems because as pointed out above:.

You truly have one unique Vista tower there, Cybertooth! Yeah, I have no idea why it works on both machines in spite of their differences in the set of installed patches. And of course now, weeks later, the details have started to fade in my carbon-based RAM.

Thank you! Yes, the details have apparently faded or completely disintegrated, in my case from my carbon-based RAM as well. My thanks to both lmacri and abbodi86 for their expertise and insight and, for me, memory prompting as well.

Much appreciated, Cybertooth and thanks again to lmacri , abbodi86 and volume-z for their further clarification. Upon installation, Windows asked to reboot. During the reboot, I was puzzled to see that the computer was behaving as if it had installed a Windows Update, with the update progress screen prior to going back into the OS. After Windows finished booting, a quick trip to Update History showed that a Hotfix KB had been installed, evidently as part of the process of installing ZoneAlarm.

Today I went ahead and installed KB on the Vista tower. No reboot was requested, and everything appears to have gone well. You can use BBCodes to format your content. Your account can't use all available BBCodes, they will be stripped before saving.

Log in Remember me. Register Lost your password? It's easy to post questions about Windows 11 , Windows 10 , Win8. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced. Contact Customer Support. Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars. AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters formerly Windows Secrets Newsletter and AskWoody Plus Alerts, emails when there are important breaking developments.

Click here for details and to sign up. Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday?

Send an email to sb askwoody. Free Newsletter Signup. Current Microsoft patches are causing havoc. Don't patch. Defender updates no longer install on Vista. Topic Resolution: Resolved. This topic has replies, 11 voices, and was last updated 1 year ago.

Topic New Reply. Cybertooth AskWoody Plus. August 31, at pm Reply Quote. Viewing 81 reply threads. September 1, at am Have you tried this command? OK thanks, I just tried it. There was no change. Alex AskWoody Plus. September 1, at pm What is Windows Defender? Windows Defender is a free program from Microsoft that helps protect your computer against pop-ups, slow performance, and security threats caused by spyware and other unwanted software.

For more information, see Windows Defender helps remove spyware from your computer. Skip to main content. You may also like these articles Featured image for 6 strategies to reduce cybersecurity alert fatigue in your SOC. My computer crashed and the hard drive has been replaced and copied from the old. Any help would be great.

Do you have any security software installed on your computer? How long have you been facing this issue? Did you make any software or hardware changes on your computer prior to this issue? How do I reset Windows Update components? Troubleshooting Windows Defender. How to troubleshoot definition update issues for Windows Defender?

Was this reply helpful?