Hasta la vista! Microsoft finally ends extended updates for ancient Windows version
- Reference: 1768401909
- News link: https://www.theregister.co.uk/2026/01/14/microsoft_calls_time_on_the/
- Source link:
January 13 marked another milestone for legacy systems, as support for the software - codenamed Longhorn Server - expired for customers that [1]bought Microsoft Premium Assurance (PA).
Extended support ended for Windows Server 2008 on January 14, 2020. It was possible to keep the lights on until January 10, 2023, via Extended Security Updates. A fourth year came courtesy of Azure, which took the code to January 9, 2024, but that was it for anyone without PA.
[2]
The long-defunct plan was a paid add-on to Software Assurance that kept security updates flowing for 6 years. It was eventually phased out in favor of Extended Security Updates to ease the transition between software versions. However, Microsoft [3]said , "We will honor the terms of Premium Assurance for customers who already purchased it."
[4]
[5]
The final patch means an end of support for the Windows Vista codebase, which was released to manufacturing in 2006 and made generally available in 2007. The Vista-derived Windows Server 2008 was released in 2008.
The extinction event was logged on social media, with one person [6]noting the lengthy time in which updates for the Vista codebase kept flowing: "It's so strange to think that updates for Vista existed for a longer time than updates for XP did, considering the... 'small,' difference between their reception and usage."
[7]Windows info-disclosure 0-day bug gets a fix as CISA sounds alarm
[8]Mall display crashes the vibe with Windows activation nag
[9]Developer writes script to throw AI out of Windows
[10]'Windows sucks,' former Microsoft engineer says, explains how to fix it
In another corner of the Microsoft universe, the US vendor called time on some modems in Windows 10 this week.
The January 13, 2026, Windows 10 patches (for which many users will need Extended Security Updates to access) marked the end of the road for several models, as the company announced that the agrsm64.sys , agrsm.sys , smserl64.sys , and smserial.sys modem drivers were being removed.
[11]
"Modem hardware dependent on these specific drivers will no longer work in Windows," Microsoft said.
This doesn't mean all modems, but the removal of the likes of agrsm.sys means that hardware using the legacy Agere modem chipset won't function. The driver family has been noted as a vulnerability, and given its legacy nature, removal makes more sense than hoping for a patch. ®
Get our [12]Tech Resources
[1] https://www.theregister.com/2016/12/12/microsoft_announces_16_years_of_support_for_windows_sql_servers/
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aWlxnXTX7jwD_MtPnvautwAAAI4&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxnXTX7jwD_MtPnvautwAAAI4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aWlxnXTX7jwD_MtPnvautwAAAI4&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://www.reddit.com/r/WindowsVista/comments/1qbg41p/comment/nzadcz6/
[7] https://www.theregister.com/2026/01/14/patch_tuesday_january_2026/
[8] https://www.theregister.com/2026/01/12/mall_bork/
[9] https://www.theregister.com/2026/01/13/script_removes_ai_from_windows/
[10] https://www.theregister.com/2025/11/07/does_windows_really_suck_that/
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aWlxnXTX7jwD_MtPnvautwAAAI4&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://whitepapers.theregister.com/
Dude. If you're still running that, and you're expecting support, I'll have what you're smoking.
If you're running that and it's not on it's own locked down non-internet-exposed network, you deserve the beating you're going to get.
If you have equipment that REQUIRES an ancient OS you need to fence it off and not expect miracles.
Yup. Decades ago, I was a paid intern for the city I lived in doing data entry for the pavement management database.[1] The software that we were using was ancient, and I worked on an isolated Win 3.11 box with NO networking at all. We had to backup and transfer the reports on floppies. Not only could the system not be upgraded, but even installing a networking stack onto it would break the software. So I don't think they were being security-conscious, but it just worked out that way.
[1] it contained the condition of every road and what was wrong with each one for knowing when to resurface them according to some sort of triage
The trouble is that jumping through the regulatory hoops for any updates on some kit can be horribly expensive & time consuming - eg hospital heart echo scanners.
The intention is good (having kit that is known to work, etc) but the practice is bad as it results in kit not being updated and so running on old/hard-to-replace hardware and running an operating system with known flaws (especially bad are networking ones as this kit will often be plugged into the hospital LAN).
This is not just a Microsoft problem - it can happen to any long lived embedded system.
Microsoft said, "We will honour the terms"
How nice of them to continue to provide something that has already been paid for.
Presumably this was ring-fenced somehow otherwise it would have been shitcanned long ago.
Re: Microsoft said, "We will honour the terms"
They could have also said "we will not honour the terms, here is you money back, with something extra to cover interest and inconvenienece"... So, they actually keep support for such an ancient codebase is noteworthy (and perhaps even comendable)
JM2C YMMV
Are those "Modems" softmodems?
I remember, long long time ago, there were "winmodems", so cheap that the CPU did even the most basic work. So, good that crap is gone...
Regarding Server 2008: The last server OS with 16 bit support, if you installed it as 32 bit version. Maybe.... maybe they now have free resources to fix Windows 11? (don't know which icon would fit here)
Re: Are those "Modems" softmodems?
Yes, they are all softmodems.
"I remember, long long time ago, there were "winmodems"
...I remember, long long time ago, there were "modems"... :-)
I'm glad they're all gone now. I have certain nostalgia for Telix, AT command tinkering, GIFLINK, hideous phone bills - even Zyxel was a reputable brand back then - but it's been at least 15 years since I had to deal with modems or GSM data, and I wonder how long will it take for MS to sunset the modem support anyway. There's zero ISP's with modem banks left where I live and ADSL is also being killed.
I recall the biggest problem with those softmodems more often wasn't the CPU perf hit but the craptastic quality of drivers or actually finding a working driver for the noname PCI modems.
Now, let's not delve into the crappy Winprinters...
10 years after
Still getting support! I decommed the last 2008 beast that I managed back in late 2016
Re: 10 years after
Whoopie doo!
"My stuff is easy to migrate on account of it being simple and boring. Sod anyone else."
I recall 2008 R2
the only server version of Windows that ever dirtied my hands.
I inherited a dongle locked license server running an ancient version of Windows on an equally ancient consumer PC and was required to move it to an unused 1RU server racked in the machine room
Of course the license manager software would only run under Windows and Win7 was the then "stable" version (cf Win8) so as a naive *ix admin thought just install Win7 on the server - easey·peasy … yes… sort of but would not activate nohow noway.
The enterprise Microsoft support people were no help whatsoever (you are doing it wrong.)
Finally worked out the problem and guessed that installing a windows server OS should work and 2008 R2 seemed the best bet which it was. Installed, connected to the corporate license service and activated.
I was really surprised by how clean and fairly minimal the user interface and installed software were — a better version of Win7. :)
Never had to touch it (other than periodic updates) until decomissioned nearly a decade later. I think the ancient client application wouldn't run under the now mandated Win10 so running the license service became pointless.
Huh.
I wonder if there is some version of Windows 7 still getting updates?
and yet I bet there's still systems exposed on the network (if not the internet) still running that shit. You hope manufacturing (and healthcare) are starting to take note of how hard it is to transition and how impossible it is to get real long term support for the OSes they choose to run.