Veeam's official plan regarding the upcoming End-of-Life (EOSL) for Microsoft .NET 8

[K-taira]

Hello everyone!

I would like to inquire about Veeam's official plan regarding the upcoming End-of-Life (EOSL) for Microsoft .NET 8. We are currently planning our future infrastructure and need to understand how this will be handled.

[ Background ]
As per the official system requirements, Veeam Backup & Replication (VBR) v12 and v13 have a dependency on .NET Desktop Runtime 8.

- VBR v12: Requires Microsoft .NET Desktop Runtime 8.0
(Source: https://helpcenter.veeam.com/archive/ba ... kup-server)
- VBR v13: Requires Microsoft .NET Desktop Runtime 8.0.21
(Source: https://helpcenter.veeam.com/docs/vbr/u ... kup-server)

According to Microsoft's support policy, .NET 8 will reach its EOSL on November 10, 2026. This raises concerns about how to maintain a fully supported Veeam environment after this date.
(Source: https://dotnet.microsoft.com/en-us/plat ... #lifecycle)

[ Questions ]
To help us plan accordingly, could you please provide guidance on the following points?

1. Strategy for Veeam Backup & Replication:
- For VBR v13: Will a patch or future update be released to support a newer .NET Desktop Runtime (e.g., .NET 10 or later)?
- For VBR v12: Will a dedicated patch be provided, or will an upgrade to a newer VBR version (e.g., V13.x or V14) be the required path to stay on a supported .NET runtime?
- User-Side Upgrades: Could a scenario exist where, even without a patch from Veeam, we could replace .NET 8 with .NET 10 (or later) ourselves, have it function correctly, and still be eligible for official support?
- Component Removal: Is there a scenario where, if the VBR features requiring .NET 8 are limited and we do not use those specific features, it would be acceptable for us to uninstall .NET 8?

2. Strategy for Other Veeam Products:
We have also noted that other products require .NET 8, such as:
- Veeam Agent for Microsoft Windows: Requires .NET Desktop Runtime 8.0.21
- Veeam ONE: Requires Microsoft .NET Runtime 8.0.17

What is the roadmap for these products concerning the .NET 8 EOSL?

Any official information on Veeam's future direction regarding this dependency would be greatly appreciated.

Thank you for your time and assistance.

[Mildur]

Hi K‑taira,

Welcome to the forum!

You can’t replace .NET yourself or remove .NET 8 — please wait for an official product update from us.
Products that have not yet reached their end of fix date will receive updates for .NET 10.

For Veeam Backup & Replication, Veeam ONE, and Veeam Agent:

• v13: The Update to support .NET 10 is already in development and will be provided later this year.
• Agent v6 and VBR/VONE v12: Reached end of fix and will not receive .NET 10 support.

To answer your question:
- You’ll need to plan an upgrade of your environment to v13.* later this year, as soon as .NET 10 support becomes available.

Best regards,
Fabian

[K-taira]

Hello Fabian,

Thank you for your clear and prompt response.

I understand that for organizations like ours, where maintaining a fully supported VBR configuration is essential, upgrading to a future version of V13 is the required path.

To help us create a concrete action plan for our environments, we would like to ask a few follow-up questions:

1. Release Timeframe and Deployment Scheduling:
You mentioned the update is planned for "later this year." To ensure we have adequate time to plan, test, and deploy this important update well before the .NET 8 EOSL in November 2026, we are hopeful for a release as early as possible. Could you provide a more specific target, such as a particular quarter (e.g., Q3 or Q4) or month (e.g., August, September) of this year?

2. Update Process Details:
While we understand that details may not be finalized yet, could you share any preliminary information about the technical process of this update? This would help us anticipate the effort required. For example:
- Will the V13 update package likely handle the entire process automatically (e.g., installing .NET 10 and removing .NET ?
- Or should we anticipate that administrators might need to perform separate manual steps?

3. Release Notification:
How can we best stay informed about the official release of this .NET 10-compatible update? Will there be a specific announcement on this forums, a dedicated KB article, or should we simply monitor the release notes of all future V13 updates?

Your clarification on these points is essential for our forward planning.

Thank you for your continued support.

[Mildur]

1.) We are targeting the end of Q2.

2.) The upgrade will follow our standard procedure for upgrading Veeam Backup & Replication from one major/minor version to the next. Here is an example Help Center article for v13.0: Help Center - Upgrading to Veeam Backup & Replication 13.
When it's supported in our upcoming releases, .NET 10 will be deployed automatically as part of the "Install missing software" step during the upgrade, so customers do not need to prepare it manually.
But we will not remove the previous .NET version, because we cannot determine whether other third-party applications rely on it on a customer-managed Windows machine.

3.) There are multiple ways to follow product release news:

• Monitor our KB article for Veeam Backup & Replication versions: https://www.veeam.com/kb2680
• Subscribe to our RSS feed to be notified about all KB changes: https://www.veeam.com/services/open/kb/rss-feed
• Monitor our forum topic for Veeam Backup & Replication versions: [ALL VERSIONS] Current build is ****** (January 6, 2026) (updated when a new version is released)

We won’t publish a dedicated KB article for .NET 10 compatibility. But you can verify the required .NET version on the system requirements pages after we release a new minor and/or major version.

Best,
Fabian