Microsoft .NET Framework 3.5 Deployment Considerations
.NET Framework 3.5 is not included by default in Windows 10 or Windows Server 2016, but you can download and deploy it for application compatibility. This section describes these deployment options.
In this section:
- Deploy .NET Framework 3.5 by using Group Policy Feature on Demand setting
- Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM)
- Enable .NET Framework 3.5 by using Windows PowerShell
- Enable .NET Framework 3.5 by using Control Panel and Windows Update (Windows 8 only)
- Enable .NET Framework 3.5 by using the Add Roles and Features Wizard
- .NET Framework 3.5 deployment errors and resolution steps
Windows 10 or Windows Server 2016 include .NET Framework 4.6, which is an integral Windows component that supports building and running the next generation of applications and web services. The .NET Framework provides a subset of managed types that you can use to create Microsoft Store apps for Windows by using C# or Visual Basic. For more information, see .NET Framework.
Only the metadata that is required to enable the .NET Framework 3.5 is contained in the default Windows image (\sources\install.wim). The actual binaries are not in the image. This feature state is known as disabled with payload removed.
You can get the .NET Framework 3.5 payload files from Windows Update or the installation media in the \sources\sxs folder. For more information, see Installing the .NET Framework 3.5. After the .NET Framework 3.5 feature is enabled, the files are serviced just like other operating system files from Windows Update.
If you upgrade from Windows 7 (which includes .NET Framework 3.5.1 by default) to Windows 10, or from Windows Server 2008 R2 (which has .NET Framework 3.5.1 feature installed) to Windows Server 2016, .NET Framework 3.5 is automatically enabled.