It's over unless you
Windows defender definition updates
- Thread starter Vistauser324
- Start date
Vistauser324
New Member
I believe Vistaar says they do.
Vistaar
Vista Guru
For those who haven't worried about patching their OS for two and a half years, the old antispyware version of Defender strikes me as a rather lame reason to suddenly become interested. I have advised against using Defender for years, notably in the 3-year-old thread Avast Turns Off Defender. I also doubt that definition updates will continue after support for Windows 7 ends on January 14.
According to the text files that Microsoft deliberately includes with Windows updates, virtually all Windows 6.0 updates released in recent years apply to both Windows Vista SP2 and Windows Server 2008 SP2. For example, I just extracted this document using 7-zip:
VistaLover of MSFN has just shown that definitions for Defender can still be installed: Server 2008 Updates on Windows Vista.
Last edited:
Vistauser324
New Member
'For those who haven't worried about patching their OS for two and a half years'.
First I want to say thanks for your help and knowledge but Why do you have to be so passive aggressive all the time? It's no skin off your nose if somebody is using an unsupported OS. And I mean this whole forum is about vista, so it is obvious anyone on it hasn't updated their OS! I mean, if people using unsupported OSs annoys you why do you even come here?
Vistaar
Vista Guru
Some people are actually running Vista fully updated to October 2019, but you are correct that not many of them post at this forum.
Vistaar & others
check out this Askwoody forum topic:
what are your reactions to this?
check out this Askwoody forum topic:
what are your reactions to this?
SHA-1 is gone. Vista wasn't updated. It's M$ again trying to push older versions out. They ONLY want people to be on 10.
The same thread mentions a possible fix.
Last edited:
Vistaar
Vista Guru
If Cybertooth of AskWoody was able to manually install definition updates for Windows Defender until August 3, 2020, then he had already installed SHA-2 support - and yet most of that AskWoody thread is about installing SHA-2 support. 
I can neither confirm nor deny that definition updates became impossible to install after August 3, since I keep that piece of junk disabled and haven’t bothered to install any definitions for many years. Hopefully most Vista users have better security solutions installed!
I can neither confirm nor deny that definition updates became impossible to install after August 3, since I keep that piece of junk disabled and haven’t bothered to install any definitions for many years. Hopefully most Vista users have better security solutions installed!
Last edited:
lmacri
Vista Pro
Hi erpster4:
I posted some comments in reply # 2295699 in Cybertooth's AskWoody.com thread but they've performed a system restore on that desktop machine so many times I can't follow what Win Server 2008 updates are still installed - or what hardware components / anitvirus program that machine has. If I recall correctly Cybertooth owns two Vista SP2 machines - 1 desktop and 1 laptop - and they had a similar black screen issue on that same desktop machine back in June 2019 when they applied the May 2019 KB4499149 (monthly rollup) or KB4499180 (security only) update to patch the Bluekeep exploit vulnerability that changed their build to 6.0.6003 (see Cybertooth's comments in the AskWoody thread Are Bluekeep Patches Causing BSODs With Server 2008 SP2 and Vista?) At the time Cybertooth mentioned that both Vista SP2 machines had Norton 360 installed and that the problem desktop machine had a NVIDIA graphics card. Their Vista SP2 laptop that does not have a discrete graphics card and uses the integrated Intel graphics drivers did not boot to a black screen when the Bluekeep patch was applied and the build changed to 6.0.6003 - and according to their 12-Sep-2020 post # 2295735, this laptop still boots normally when the Servicing Stack Updates and KB4474419 patch to add SHA-2 support are installed - but who knows what other differences there are between their two machines.
I'm even wondering now if v6.0.6003.x versions of files like the Driver Store API drvstore.dll that come bundled with Servicing Stack Updates like KB4493730 (the Win Server 2008 SSU from April 2019) could be contributing to Cybertooth's black screens.
It looks like Vistaar has decided to pursue this over in the MSFN forum in Windows Update Error Code 80072EFD where he posts as user Vistapocalypse. He's already stated that "lmacri tends to exaggerate the problems encountered by those of us who are actually running Windows 6.0.6003" when I mentioned that the change to Build 6.0.6003 could be causing black screens at boot-up on some Vista SP2 machines (see his comment <here> as user Abzyx in the BleepingComputer forum) so I'm eager to hear what the root cause of this problem actually is if Cybertooth's black screen has nothing to do with their graphics drivers and/or the Microsoft Graphics Components that come bundled with some Win Server 2008 updates.
--------------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Malwarebytes FrePremium v3.5.1-1.0.365
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS