Some applications are asking for .NET Framework 3.5 after an update to Windows 11 26H2, even though the feature was enabled before. Is this happening on every upgrade, and what should we do about it?
Is Windows 11 26H2 disabling .NET Framework 3.5?
Answers
There are reports of it disappearing on some devices after an upgrade, but not every device seems to be affected. That doesn't establish that 26H2 removes it by design or explain why it happens.
For an affected machine, try enabling .NET Framework 3.5 again through Windows Features. That has restored the applications in the reported 26H2 cases. It would also be worth checking the feature after upgrades on devices known to run software that needs it.
Reply to this answer
The upgrade path might be worth tracking. With 25H2, there were reports of the feature disappearing after some ISO-based upgrades but staying enabled after an enablement package. That's an observation about 25H2, not proof the same distinction applies to 26H2.
Reply to this answer
There's a longer-term application question here too. Moving away from a dependency on .NET 3.5 may be sensible, but replacing software tied to expensive equipment isn't always a quick or practical option.
.NET Framework 3.5 SP1 is supported until 2029, so an old dependency is not necessarily an unsupported one. Check the specific version and application rather than assuming all .NET Framework releases share the same support dates.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Cavrix.2u:
I'd record the starting Windows version and the update method alongside which machines lose the feature. That may help narrow down a pattern.