Add information about changes to Win11 and 3.5 #51430
Conversation
| ms.topic: include | ||
| --- | ||
|
|
||
| Starting with Windows 11 Insider Preview Build 27965, .NET Framework 3.5 is no longer included as Windows Feature on Demand optional component. Installation of .NET Framework 3.5 is done through a standalone installer (also known as an offline installer). For more information, see [Announcing Windows 11 Insider Preview Build 27965 (Canary Channel)](https://blogs.windows.com/windows-insider/2025/10/08/announcing-windows-11-insider-preview-build-27965-canary-channel/). <!-- When updated in the future, note that these installers only work for this specific version of Windows 11. --> |
There was a problem hiding this comment.
Is the term "offline installer" userful to readers?
There was a problem hiding this comment.
It is useful to those that have a history with .NET Framework installation methods, being the "web installer" and "offline installer."
| answer: Yes. Use `/q` and `/quiet` command-line options for unattended deployment. | ||
|
|
||
| - question: Can I apply .NET Framework 3.5 to an offline Windows image? | ||
| answer: No. Offline installation and servicing isn't supported. .NET Framework 3.5 is no longer an optional Windows Feature on Demand component, so DISM can't manage it. Use online servicing to modify a Windows installation. For more information, see [Modify a Windows image](/windows-hardware/manufacture/desktop/modify-an-image?view=windows-11). |
There was a problem hiding this comment.
This is another reason why not to use the term "offline installer".
"so DISM can't manage it" doesn't seem all that helpful.
There was a problem hiding this comment.
I think for the audience that question is intended for, it makes sense. I'm trying to be clear about what people managing offline deployment would be doing. And the terms used.
- Q&A: Issues trying to install .NET Framework 3.5 to an Offline Machine (solution is use DISM)
- Q&A: How can I install .NET Framework 3.5 offline? (solution is use DISM)
- Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM)
- SuperUser: Can't uninstall/reinstall .NET Framework 3.5 with DISM
How's this to clarify?
| answer: No. Offline installation and servicing isn't supported. .NET Framework 3.5 is no longer an optional Windows Feature on Demand component, so DISM can't manage it. Use online servicing to modify a Windows installation. For more information, see [Modify a Windows image](/windows-hardware/manufacture/desktop/modify-an-image?view=windows-11). | |
| answer: No. Offline installation and servicing isn't supported because .NET Framework 3.5 is no longer an optional Windows Feature on Demand component. DISM and other tools that customize offline Windows deployment images can't manage .NET Framework 3.5. Use online servicing to modify a Windows installation. For more information, see [Modify a Windows image](/windows-hardware/manufacture/desktop/modify-an-image?view=windows-11). |
| questions: | ||
| - question: What is the recommended migration path? | ||
| answer: | | ||
| Update your application from .NET Framework to modern .NET, such as .NET 10. If you can't move to .NET, update your application to .NET Framework 4.8.1. For more information, see [Microsoft .NET Framework lifecycle policy](/lifecycle/products/microsoft-net-framework). |
There was a problem hiding this comment.
This isn't what the other part of the doc says. It says to upgrade to 4.8.1 and then if you want to .NET 10. And we don't use "modern .NET" anywhere.
|
|
||
| ASP.NET 3.5 and WCF require additional registration to run in IIS. | ||
|
|
||
| Enable ASP.NET 3.5 on your device using the [`Enable-ASPNet35.ps1`](https://go.microsoft.com/fwlink/?linkid=2348600&clcid=0x409) PowerShell script. The script enables the functionality of the following optional components that have been removed from Windows: |
There was a problem hiding this comment.
We are not making download links available yet, so these links also don't make sense. They assume you have downloaded 3.5 already.
There was a problem hiding this comment.
Download links are available, they're on the Announcing Windows 11 Insider Preview Build 27965 (Canary Channel) post. I just didn't link to it files directly, but I will when this moves out of preview.
| ## Enable .NET Framework 3.5 on Windows | ||
|
|
||
| You can enable the .NET Framework 3.5 through the Windows Control Panel. This option requires an internet connection. | ||
| You can enable the .NET Framework 3.5 through the Windows Control Panel. This option requires an internet connection. If you're using Windows 11, consider the [.NET Framework 3.5 on Windows 11 FAQ](dotnet-35-windows-11-faq.yml). |
There was a problem hiding this comment.
I don't quite get this flow. Why is "Windows" and WIndows 11 Prevew" split into different sections? Windows client sections should be beside each other and it should be clear which instructions apply to which Windows versions. That isn't clear.
Summary
Future releases of Windows 11 (actually it started in a previous insiders build) are removing .NET Framework 3.5 from the Operating System. A standalone installer for Windows 11 is provided.
Once this change is applied to the non-insiders release, these articles will include download and installation instructions.
Internal previews