In reference to my previous posts: #200783 & #200801
After giving this some additional thought, I now believe that Microsoft initially modified May 2018’s Win7/Vista Windows Defender engine version “1.1.14901.4” which purposely set an “end date” for defender engine & def updates for Vista at 6/12/2018 – 1 day prior to June 2018’s security patch Tuesday. However, Win7 updates would continue to receive whatever the next MOST current engine & def versions were available on the actual day/time the update was performed as verified in my previous posts above.
For Vista …
Running update resulted in engine updated to “1.1.14901.4” & defs to “1.269.1075.0” dated 6/11/2018 6:50AM.
But … why only to 6/11/2018? … this is not the MOST current engine & defs! Win7 just updated fine (see above) when starting with engine at “1.1.14901.4” & defs at “1.269.1075.0” dated 6/11/2018 6:50AM.
Running a 2nd/3rd update resulted in “No new updates found”.
In addition, June 2018’s engine version “1.1.15000.2” was also modified I believe “with the intent to stop all future Vista updates” but also in a way “without giving distinction between Vista & Win7” as currently both seem to use the very same engine & defs. I think this was where the error of “overlooking Win7” was made.
If Microsoft had intended to stop future updates for Win7, why did they allow for that “one” & “only one” next MOST recent update past 6/11/2018 for Win7 in engine version “1.1.14901.4”? They could have just as easily made Win7 & Vista the same using the same “end date” or different “end date” just for Win7.
With the way things stand now, even accounting for today’s Microsoft, everyone’s last defender update is/would be different dependent upon the actual day that the last Win7 update was done with engine “1.1.14901.4”. This seems a bit strange.
It could be that Microsoft intended to stop updating Win7 prior to July 2018’s security patch Tuesday but if that were the case, one would still get Win7 updates up until then with engine version “1.1.15000.2” and we know this is not the case today.
I guess only time will tell if it’ll be back (get fixed) or if it’s gone forever. Oh well …
Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS
