Office 2007 reached official end of extended support yet I'm still getting updates?

[mikeymikec]

https://support.microsoft.com/en-us/lifecycle/search?alpha=office 2007

Office 2007 SP3's end of extended support was 10/10/2017, yet I've received nine updates since that date (and my Office install is years old, I haven't modified/repaired/reinstalled it).

Am I missing something here? I could understand maybe one uber-emergency update, or an update that's been coming for some time before the shut-off date.

 

[Billb2]

Microsoft typically continues security updates (but not functionality updates) for their products after the EOL date.

 

[Victorian Gray]

Microsoft typically continues security updates (but not functionality updates) for their products after the EOL date.

Not according to Microsoft

"Office 2007 has reached the end of its support lifecycle, meaning there are no new security updates, non-security updates, free or paid assisted support options, or online technical content updates."

https://support.microsoft.com/en-ca/help/3198497/office-2007-approaching-end-of-extended-support

 

[bbhaag]

Perhaps these updates where still "in the pipe" so to speak before Office 2007 went eol. Take this Word 2007 security update as an example. It was officially published on November 16 2017 but didn't get main stream publication through Windows update until December 12 2017.
This is just a theory but it could explain why you are still getting updates even after the product went eol.

 

[Billb2]

Not according to Microsoft

"Office 2007 has reached the end of its support lifecycle, meaning there are no new security updates, non-security updates, free or paid assisted support options, or online technical content updates."

They always say that and then continue security updates for a few years. XP for example

A security issue has been identified in a Microsoft software product that could affect your system.

Version:
4012598
File Name:
WindowsXP-KB4012598-x86-Custom-ENU.exe
Date Published:
5/15/2017

 

[mikeymikec]

They always say that and then continue security updates for a few years. XP for example

A security issue has been identified in a Microsoft software product that could affect your system.

Version:
4012598
File Name:
WindowsXP-KB4012598-x86-Custom-ENU.exe
Date Published:
5/15/2017

That was an emergency update due to the whole NHS ransomware attack situation, I'm pretty sure. I fired up my XP VM the other day after reading your first post, and it hasn't installed any updates for XP since 2014 basically (2015 if I'm honest, but I rarely fire up the VM and looking at the update installation dates, there was a big gap between the first 2015 update installation and then it went back to before the XP support shut-off date). It has installed plenty of Office 2010 updates.

 

[Billb2]

For XP, when they discontinued updates at EOL all the people with embedded XP installations screamed bloody murder. So they continued security updates for embedded installs. There's a workaround to make MS think your XP is an embedded install so you can continue to get security updates.

 

[mikeymikec]

For XP, when they discontinued updates at EOL all the people with embedded XP installations screamed bloody murder. So they continued security updates for embedded installs. There's a workaround to make MS think your XP is an embedded install so you can continue to get security updates.

And 2014 was the new shut-off date for normal versions of XP.