Windows 7 Esu 2026
Verline Wesolowski
The following list represents products retiring or reaching the end of support in 2026. Upon retirement or end of support, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. Go here to learn about Fixed and Modern Lifecycle policies and service packs.
The following products will be moving from Mainstream to Extended Support in 2026. Extended Support includes security updates at no cost, and paid non-security updates and support. Additionally, Microsoft will not accept requests for design changes or new features during the Extended Support phase.
At Microsoft, we are dedicated to providing our customers with the tools they need to achieve what matters, in their work and life. In order to focus on new benefits, we occasionally remove features and products.
In October 2026, Microsoft Publisher will reach its end of life. After that time, it will no longer be included in Microsoft 365 and existing on-premises suites will no longer be supported. Until then, support for Publisher will continue and users can expect the same experience as today.
Many common Publisher scenarios including the creation of professionally branded templates, envelope and label printing, and producing customized calendars, business cards, and programs are already available in other Microsoft 365 apps such as Word and PowerPoint. You can find a wide array of customizable templates at Microsoft Create.
Support for the perpetual version of Publisher will end in October 2026, when Office LTSC 2021 reaches end of support. Microsoft 365 customers will not be able to access Publisher from that date forward.
Very excited about all the new features! Hotpatching even when not running on an Azure VM is amazing, can't wait to find out more about the new Hyper-V features, that's something I use every single day.
Junte-se a mim para uma imerso profunda nas novidades, recursos avanados e a revoluo que o Windows Server v.Next trar para o mundo dos servidores. Desde melhorias de segurana at atualizaes de desempenho, vamos explorar tudo o que h de mais novo nesta plataforma poderosa.
With Advanced Group Policy Management going EOL with MDOP in April 2026 and no clear replacement are Microsoft intending to integrate an "AGPM like" capability within the "Next Generation Active Directory" coming with Server 2025? If not is there any assurance Microsoft can provide to current AGPM customers still very much reliant on it's capabilities for GPO management that something will be coming to replace AGPM and we won't need to move to 3rd party solutions?
In terms of TPM, it is not required, so your legacy hardware will continue to work with Windows Server 2025. For *new* physical servers to be qualified for Windows Server 2025, TPM is required. This shouldn't be a problem because physical servers have been shipping with TPMs for years.
Honestly, it's 2024. You should be raising your security. If you've got legacy hardware without TPM you really should look at upgrading that hardware. Hardware that old is lacking the hardware to support Secured-core Server.
In the assumption the workloads run mainly on virtual systems the vTPM support of the hypervisor, would be more important. I understood now, the installation process for W2K25 will not check the TPM readiness of the underlay (v)HW as a prerequisite. Is that right?
Sorry, if I wasn't clear in my previous statement, I just edited my response to be clear that I'm specifically referring to physical hardware. As for VMs, Windows Server 2025 will work just fine in your VMs without a TPM.
@Udo_Poehlmann as Windows Admin Center might not support it yet (you could still try), I believe there only PowerShell. The new dedup has New PowerShell Commands and the old dedup might not be enabled at the same time.
In addition to TPM concerns, mind that hardware without TPM is that old that the CPU Performance ratio is about 10:1 means one pCore can now handle 10 more vCores as in the past. Consider Azure Stack HCI 23H2 / 22H2 integrated or premier nodes, too when modernizing hardware servers.
I am particularly interested in NVMe-oF support in Windows Server 2025, is this feature available yet? Are there any official documentations or guides available that outlines the implementation and configuration details for NVMe-oF on Windows Server 2025? Thank you!
What I have seen is hot patching has not worked at all on my test builds, but I don't like that you have to pay $5 a machine to be able to use hot patching, most of the rmm tools used can do updates, this should really be a free feature or replace the arc patching and make hot patching available inside the OS that can be scripted or maintained using any rmm tools
Am I missing anything? Generation 1 is not deprecated but quite sunset as Gen 2 will be finally the default VM generation with Windows Server 2025 and in Azure. The reasons are multiple, but one is UEFI and Secure Boot requirements + technology like VBS, HCVI and other rely on this. In addition vTPM will come play a role in the VM security strategy.
At Better View Windows and More, our mission is to provide you with a stress-free experience shopping for windows, siding, doors, and roofing. We believe in doing what is in your best interest and treat your home or business like they were ours. When you need window installation in Virginia Beach, you can count on Better View Windows and More to deliver superior products and customer service.
Do you see the pattern of behavior here? Microsoft releases a new server operating system, attempts to not support M365 Apps, then relents after customer displeasure. Given that they only extended official M365 Apps support another year, into 2026, the new game Microsoft may be playing is shortening the pledged M365 Apps support timeline in an attempt to make customers purchase RDS CALs more frequently, by tying M365 Apps support to a new version of Windows Server.
Of course, in regards to continuing to provide support for hosting M365 Apps in RDS, Microsoft has a sword of Damocles hanging over it in the form of EU regulators that are scrutinizing their business practices and licensing rules around apps and services hosted in Azure, as compared to apps and services hosted in other clouds and datacenters.
But now in May of this year, Paul Thurott reports that the EU has launched a separate antitrust investigation into Microsoft Azure and its business practices. Suffice it to say, the EU has a massive spotlight shining on Microsoft business behavior within Azure, which I think will pump the brakes on any Microsoft attempts to remove M365 Apps support from RDS in the near future.
So, in conclusion, I think classic RDS is here to stay for another decade, and I think M365 Apps support on RDS outside of Azure will also remain supported for another decade, albeit perhaps with the caveat that you may need to upgrade RDS and RDS CALs to newer Windows Server versions more frequently. What do you think? Post your comments below here on my blog, or at this post on my RDPHard Twitter feed.
Andy Milford is the CEO and Founder of RDPSoft and is a Microsoft MVP in the Enterprise Mobility / Remote Desktop Services area. Prior to starting RDPSoft, Andy was the CEO and Founder of Dorian Software, a log management company acquired by Ipswitch in late 2009. He loves creating easy-to-use yet powerful software solutions for SMBs and emerging enterprise companies.
Microsoft announced a few months that M365 will be supported in Server vNext for 5 years during mainstream support. So that means that M365 is effectively guaranteed on Server vNext RDS until 2029. Since M365 Apps support sunsets on Server 2022 in October 2026, we recommend upgrading to Server vNext in the next 24 months.
If the restatement window for 401(k) plans opens 1/1/2026,then the two will overlap. Originally, (in a galaxy long, long ago and far, far away) I seem to recall that the "regular" pre-approved plan cycles were going to be timed such that they would not overlap, but I'm not certain of that.
Do you know if anyone has suggested to the IRS (document providers, ARA, etc.) that the 2-year DC Cycle 4 restatement window not open until 2027, to avoid this overlap? And if so, even unofficially, was the IRS at all receptive to the suggestion?
Honestly, I haven't bothered to figure it out yet. I fully plan to be retired by then, so selfishly, it'll be someone else's problem. I did see something about this somewhere, but I just skipped over it, so I don't know what it said...
[German]Brief information to administrators in the enterprise environment who are running Windows Server 2022. It is now final, there will be support for Microsoft 365 apps until October 2026. This affects support for Microsoft 365 apps (Word, Excel, etc.) on Windows Server 2022. As recently as December 2021, Microsoft had emphasized that there would be no support for the MS 365 apps in question on the operating system. I had reported on the U turn from Microsoft.
It was a shock to many administrators that Microsoft would not provide support for Microsoft 365 apps (Word, Excel, etc.) on Windows Server 2022. I had pointed out Microsoft's position in October 2021 in the blog post Windows Server 2022: Microsoft 365 Apps unsupported (see also the following screenshot). Affected users should switch to Azure Virtual Desktop or Windows 365, according to Microsoft.
It was kicked off by an affected party with a large number of Windows Server 2016 instances with Microsoft 365 apps (Office 365). The affected person wrote in early December 2021 that he needed to update these servers. He made it "incendiary" in his post because the end of support for Windows Server 2016 was January 2022 after all (that's not so true, that's when Active Support ended, Extended Support still runs until January 12, 2027).
The issue has probably led to quite a bit of protest from customers. In any case, in September 2022, there was feedback in Microsoft's tech community from Microsoft employee Elden Christensen on the user post Support for M365 Apps (O365) on Windows 2022, who announced that Microsoft had reconsidered. I had picked this up in the blog post Windows Server 2022: MS 365 apps to be supported.
c80f0f1006