We have a large number of .NET installations and limited visibility into which applications use them. How would you inventory .NET 8 and 9 and plan removals without breaking things?
How do you find and safely remove old .NET runtimes at scale?
Answers
Start with an inventory, not an uninstall job. Collect the installed runtime and SDK versions, runtime types, and installation scope across devices. Keep the results by device so you can group machines with the same software and investigate representative samples.
Installation data tells you what's present, not necessarily what's in use. Match it with your application inventory and owner information where you can, then test removal in small waves with a rollback plan. A scream test can catch missed dependencies, but it shouldn't be the only discovery method.
Reply to this answer
Check the actual support dates before treating both versions as end of life. .NET 9 reached end of support on November 10, 2026. .NET 8 is supported until November 10, 2026 as well, so both are out of support now.
Getting the newest patch within an old major version is not the same as moving the application to a supported major version. Ask application owners or vendors what they support before removing a runtime or assuming a newer one will work.
Reply to this answer
Watch out for self-contained applications, especially on IIS servers. They can carry their own runtime, so updating or removing a machine-wide runtime or hosting bundle does not necessarily update the runtime bundled with the app.
Include application deployments in the review and work with the vendor or app owner on an updated build. Machine-level inventory alone won't give you the whole picture.
Reply to this answer
Your patch management tool may already have a package or script workflow for detecting and updating these runtimes. Worth checking before building the whole thing from scratch. Test its detection and removal rules first, especially for desktop runtimes, SDKs, and different installation scopes.
4n~socketmortar_863:
That sounds like a useful place to start for the inventory, even if application dependency checks still need separate work.
Reply to this answer
Don't lump .NET Framework 3.5 in with modern .NET runtimes. An application may still depend on that older framework, and its lifecycle and removal process are separate. Track those dependencies separately rather than treating every old-looking version as the same cleanup job.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_z56!pluvori.8:
For rollback, keep a way to redeploy the exact runtime type and a supported version of the required major release.