If it does (hopefully!), then see if the latest Defender updates install. If you’re not using EFI, then version 3 of KB4474419 (the Septemrelease) should successfully install for you. As I mentioned above, MS, in their infinite wisdom, somehow initially neglected to include MSI SHA-2 code signing support in this update and then even needed to re-release it again because it was also missing EFI boot managers required by some devices who were using these. Since you mentioned you were able to get KB4493730 successfully installed (which introduced SHA-2 code signing support for the servicing stack (SSU)), I would first suggest trying to re-install one of the later versions of KB4474419 to see if that works. I forgot to mention that KB4036398 is for 64 bit systems only but that info is also in the support article. I wish to focus on what change did or may have occurred to have the effect described above. Please, no inquiries or comments as to why I’m still running Vista or Windows Defender. Does anybody have insight into what happened this summer (and not before this year) to make this manual installation method stop working?Īdding to the strangeness is that when I hover the mouse pointer over the mpas-fe.exe file in Windows Explorer, the file information there differs from what I gave above: it has the file version as 1.323.290.0 with a creation date of at 11:45 AM. The last definition version is “1.321.534.0 created on at 10:49 AM”. Since the beginning of August, though, this manual method has stopped working. This was not a big problem because it was still possible to manually download the updates and install them by running the definitions file (mpas-fe.exe) as Administrator and I managed to keep doing just that until four weeks ago. A couple of years ago, Windows Defender stopped automatically installing new definitions updates in Vista.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |