"Our vendor contacted us saying the .NET version powering our system reaches end of support in November, but what does that actually mean?" We received this question from a manufacturing business owner who had commissioned a custom order management system. They did not understand the underlying technical details, but the phrase "end of support" sparked a vague sense of unease. That unease is entirely justified.
On November 10, 2026, Microsoft's development frameworks .NET 8 and .NET 9 will reach end of support simultaneously. If your company's core systems run on either version, new security fixes will no longer be provided after this date. It is the client companies who use the software daily and pay for it—not the developers who built it—who are responsible for understanding the situation and planning next steps. Rather than delving into technical minutiae, this article focuses specifically on what system owners must verify and decide before the deadline.
What End of Support Means for Business Systems
.NET is Microsoft's development framework that serves as the foundation for business systems and web applications. End of support means that updates to this foundation—most notably patches for newly discovered security flaws—will no longer be provided.
The system will not suddenly stop working. It will not halt on November 11, nor will screens disappear. That is precisely what makes it treacherous. The system continues operating with no outward change, but newly discovered vulnerabilities remain unpatched. When a system managing customer data or order processing enters this state, the risk of data breaches and unauthorized access quietly compounds over time. When a business partner asks, "Are you handling our data on an unsupported framework?" and you cannot answer confidently, the real damage in practice is the erosion of trust.
You might wonder why .NET 8 and .NET 9 share the exact same end-of-support date. .NET 8, a Long Term Support (LTS) release, has been supported for 36 months since November 2023, and that support window closes on November 10, 2026. Meanwhile, .NET 9 is a Standard Term Support (STS) release, but its support window was extended from the traditional 18 months to 24 months, aligning its sunset date to the same day: November 10, 2026. Microsoft recommends upgrading to the next LTS release, .NET 10 (supported through November 2028).
Three Things System Owners Must Check First
Even without technical expertise, there are concrete points you can verify and request as a system owner. Here is the recommended sequence:
| What to verify | Whom to Ask | What you can learn |
|---|---|---|
| Which .NET version powers your system | The development and maintenance vendor | Whether action is required |
| Whether the upgrade is covered under your maintenance contract | Contract documentation / maintenance vendor | Presence or absence of additional fees |
| When and who will execute the upgrade to .NET 10 | Mutual agreement between vendor and your company | Project roadmap through November |
The first point is your starting line. If you do not know whether your system runs on .NET 8 or 9 or a different framework entirely, you cannot assess whether remediation is required. Sending a simple, one-sentence inquiry to your maintenance vendor—"Which version of .NET does our system run on, and are we affected by the November end of support?"—is enough to start the conversation.
The second point concerns financial responsibility: is upgrading the underlying framework included in your monthly maintenance fee, or does it require a separate estimate? This varies significantly depending on the contract. Key items system owners should review in contracts are covered in our guide to maintenance and operations agreements for clients, while the true cost breakdown of ongoing upkeep is analyzed in our article on business system maintenance costs.
Options When You Cannot Upgrade Immediately
Complications arise when practical hurdles prevent an immediate upgrade. Dependencies on obsolete libraries, the departure of original system architects, or lost contact with the original vendor—these are everyday scenarios in the field. Even in such cases, doing nothing is not your only option.
One approach is formally commissioning a planned upgrade with your maintenance vendor, working backward from November to incorporate necessary testing periods. A second option is an upgrade paired with refactoring, swapping out deprecated dependencies with modern components while moving to .NET 10. A third option, if the architecture is outdated and upgrade costs are prohibitively high, is using this opportunity to consider a full rebuild or migrating to an alternative architecture. For modernizing older systems, see our article on legacy .NET application modernization; for managing data transitions safely during a vendor switch, consult our guide on client data migration planning.
Whichever path you choose, the key criterion is how many more years you expect to use the system. Spending heavily on a system scheduled for retirement next year makes little sense; conversely, if you plan to rely on it for the next decade, failing to act now will prove far more costly over time.
Case Study: The Company That Noticed Three Months Out and Made the Deadline
At a wholesale firm of about fifty employees (company name withheld), the core order processing system ran on .NET 8. The leadership was unaware of the impending end of support until reading an industry trade article, prompting an inquiry in July—roughly four months before the deadline.
Upon checking the active version and remediation requirements with their maintenance vendor, they confirmed their system was affected and that the upgrade required a separate quote. They established a schedule working backward from November 10, including comprehensive testing with extra verification allocated to payment processing flows. What made the project successful was not advanced technical acrobatics: it was confirming whether they were affected well ahead of the deadline and establishing a reverse-planned schedule. This alone prevented rushed last-minute work and post-deadline panic. Had they discovered the issue in October, testing time would have been insufficient, leaving them to navigate the peak year-end retail season with an anxious, unverified system.
Start by Sending a One-Sentence Inquiry to Your Maintenance Vendor
The sunset of .NET 8 and .NET 9 will not take systems offline instantly. That is why the biggest risk is inadvertently running core operations indefinitely on a foundation that no longer receives security updates. The first step for system owners is not mastering the underlying technology, but asking your maintenance partner one simple question: "Is our system affected by the November end of support?" If it is, working backward from the deadline to agree on timing, ownership, and budget will ensure you complete the transition in time.
If you are unsure whether your system is affected, cannot determine whether a vendor quote is reasonable, or have lost touch with the original developer, please feel free to reach out via GleamHub's development, AI, and automation consultation desk. From verifying active versions to building roadmaps to meet the deadline, we support you from the system owner's perspective.
