Skip to content
INSIGHTS & GUIDES · NETCLOUD24

How to Install .NET Framework Features on Windows Server

Install the .NET component an application actually requires, rather than enabling every feature whose name contains “NET.” Windows includes .NET Framework features, while modern .NET uses separate runtime and SDK.

Read the article ↓
Editorial illustration: How to Install .NET Framework Features on Windows Server

Install the .NET component an application actually requires, rather than enabling every feature whose name contains “NET.” Windows includes .NET Framework features, while modern .NET uses separate runtime and SDK installers. An application requiring .NET Framework 3.5 is not satisfied simply because .NET Framework 4.x is present, and an ASP.NET Core application usually needs a modern .NET hosting component rather than the legacy IIS ASP.NET feature.

This procedure explains Windows Server feature installation, source selection and verification. It applies to common Windows Server 2019, 2022 and 2025 deployments, but the included Framework release differs. Check Microsoft's current version matrix and the application's support statement before installing or upgrading a runtime. A server's operating-system support lifecycle and a particular runtime's lifecycle are separate checks.

Identify the application's runtime requirement

Obtain the vendor's installation prerequisites, including the framework family, minimum version, architecture and hosting model. Distinguish .NET Framework 3.5, .NET Framework 4.x, modern .NET runtime, ASP.NET Core Hosting Bundle and developer SDK. Installing an SDK on a production application server is unnecessary unless the application genuinely compiles or builds there.

Record the exact Windows Server version and installation type. An application with a graphical installer may not support Server Core even if its runtime does. If the application runs under IIS, inspect its documented application-pool settings, required role services and deployment method. Do not assume that enabling ASP.NET 4.x will make a modern ASP.NET Core application run.

Ask whether the change affects other applications. .NET Framework 4.x releases are generally in-place updates within that family, so an update can affect several applications sharing the runtime. Arrange a maintenance window and an application rollback plan instead of treating the runtime as an isolated utility.

Inspect the current Windows feature state

Open an elevated Windows PowerShell session and list the feature names available on the installed operating system:

Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber
Get-WindowsFeature NET-Framework*,NET-WCF*,Web-Asp-Net*

Feature display names can mention a familiar historical version while the installed Framework servicing level is newer. The feature state tells you whether a Windows component is installed; it is not a complete inventory of every runtime version. Save the output as the pre-change baseline.

For .NET Framework 4.x, inspect the release value and compare it with Microsoft's official version table:

Get-ItemProperty `
 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' `
 -Name Release -ErrorAction SilentlyContinue

Use the numeric release mapping rather than guessing from a folder named v4.0.30319. That folder name does not mean the installed product is only Framework 4.0. On Windows Server 2022, 4.8 is included and 4.8.1 is available; Windows Server 2025 includes 4.8.1. Older Windows Server 2019 images commonly begin with 4.7.2 and can be serviced to supported 4.8 configurations.

Install .NET Framework 3.5 from an appropriate source

When the application explicitly requires Framework 3.5, enable the Windows feature. First try the approved component source configured for that server:

Install-WindowsFeature NET-Framework-Core

If the payload is unavailable, use matching Windows Server installation media or the organization's approved feature repository. For example, after mounting the correct media as drive E:

Test-Path E:\sources\sxs
Install-WindowsFeature NET-Framework-Core -Source E:\sources\sxs

The media must match the operating-system release and relevant servicing requirements. A similarly named folder copied from another Windows version is not interchangeable. Do not download individual component files from unofficial archives. For a managed server that cannot reach Windows Update, review the policy controlling optional component installation and repair sources with the Windows management team.

Inspect the installation result and restart requirement. If it fails with missing-source errors, preserve the error code and review servicing logs. Repeating the same command with unrelated media does not address an incompatible source. Avoid temporarily changing the server's update-management authority without assessing the wider effect.

Enable only the required Framework and IIS components

For an application requiring the Windows .NET Framework 4.x feature, inspect the feature state first, then install the needed component if absent:

Install-WindowsFeature NET-Framework-45-Core

For a documented legacy ASP.NET application hosted in IIS, the necessary role service might include Web-Asp-Net45. Enable it only after confirming the application's requirements. WCF activation features are separate choices, and HTTP activation should not be enabled simply because the application uses a network connection.

If the vendor requires a newer supported Framework 4.x release than the OS image currently includes, obtain Microsoft's appropriate installer and follow its deployment guidance. Feature installation alone does not necessarily upgrade to the required servicing level. Apply the relevant security and quality updates and schedule any required restart before application testing.

Handle modern .NET separately

For a modern .NET application, use the supported runtime version and architecture specified by the vendor. Framework-dependent deployments require an installed matching runtime; self-contained deployments package their runtime but still require application lifecycle management. An IIS-hosted ASP.NET Core deployment may require the corresponding Hosting Bundle and IIS integration.

Where the .NET command-line tool is installed, inspect its runtime inventory:

dotnet --list-runtimes
dotnet --list-sdks

A “command not found” result can mean modern .NET is absent or not in the current process environment. It does not establish that Windows .NET Framework features are missing. Conversely, a modern .NET runtime listing says nothing about whether an application requiring Framework 3.5 has its dependency.

Verify with the application after the restart

Recheck Windows feature states and the Framework release value. For an IIS workload, verify the intended application pool is running, the application starts and a representative authenticated request succeeds. For a service, confirm startup under its real service identity and exercise the operation that loads the runtime-dependent code path.

Inspect Application events for .NET Runtime and application errors. A runtime installation may be successful while the application still fails because of permissions, a missing configuration file, incompatible native libraries or a wrong processor architecture. Preserve the exception message and stack information rather than assuming every startup failure requires another runtime reinstall.

Test more than the landing page when an application loads components on demand. A reporting export, scheduled processing job or database operation may use a different assembly or native dependency. Use the vendor's acceptance checks and compare with the baseline gathered before the change.

Back out without removing shared dependencies blindly

Before removing a Windows feature, identify every application using it. Removing Framework or IIS dependencies can affect workloads unrelated to the original request. Reversing a Framework 4.x update may have support and servicing constraints; do not promise a simple side-by-side downgrade. Use the approved system or application recovery plan if the vendor's rollback procedure requires it.

For repeatable builds, also document whether the installation used Windows Update, matching installation media or a managed component repository. A later repair should use the same approved source policy rather than an operator's personal download folder. Record the enabled features, installed runtime release, update level, source media and restart completion. Keep the installation source available through the approved repository so the next server can be built consistently. This also lets an operator distinguish a missing prerequisite from a drifted application deployment months later.

Microsoft's Framework system requirements and installed-version detection guidance provide the release-specific reference values.

Related procedures

How to Prepare Windows Server for Microsoft SQL Server Installation; How to Migrate IIS Websites to a New Windows Server; How to Configure IIS Application Pool Recycling.


Was this answer helpful?

« Back
Contact

Write to us

Do you have questions about our services or need a quote? Write to us and we will respond as soon as possible.

Contact form

Fields marked * are required.