microsoft / microsoft/winget-pkgs

[Windows 11 ≥26H1]: Prepare for how NetFx3 is no longer a WindowsFeature (but instead an installer) in ≥26H1, which breaks some packages if not adjusted.

Open
#391,929 1 comment 1 reaction 0 assignees View on GitHub
Needs-Triage
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

I know this repo has a million bigger problems going on, but https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-11#windows-11-26h1-build-28000-and-later possibly needs to be thought about on how to handle it.

If I interpret that page right, this means that manifests with the following in it are already unable to be installed on 26H1, and would become a decidedly bigger problem when 26H2 reaches stable:
```
Dependencies:
WindowsFeatures:
- NetFx3
```

They would however be able to install on ≥26H1 if replaced with this:
```
Dependencies:
PackageDependencies:
- PackageIdentifier: (Hypothetical Framework 3.5 package's name)
```

But that in turn would cause installations to fail on ≤25H2.

————————————————

At the time of writing, affected packages include, but are not necessarily limited to:

List of ≥35 packages:

```
AndrewWhewell.VirtualRadarServer
Bunny-Wabbit.ISOCreator
Certags.ComplyPro
CONZEInformatik.Vistrax
Coupang.CoupangPOS
drsaint.WixTool.Red
drsaint.WixTool.Yellow
IdeaMK.AIViewer
IdeaMK.CDRViewer
IdeaMK.DDSViewer
IdeaMK.EPSViewer
IdeaMK.IGSViewer
IdeaMK.PCXViewer
IdeaMK.PSDViewer
IdeaMK.RAWImageViewer
IdeaMK.STLViewer
IdeaMK.STPViewer
IdeaMK.TGAViewer
ING.Telelink
JasperKeuper.WixEdit
jgaa.WarSetup
Kensington.FingerprintApplication
KevinOttalini.SimpleMTUTest
LargeAddressAware.laa
Selur.Hybrid
SICK.FlexiSoftDesigner
Softpcapps.MinimizetoTrayTool
TheTLOPOTeam.TheLegendofPiratesOnline
VictronEnergy.BMVReader
VictronEnergy.ImpulseChargerTool
WiXToolset.WiXToolset
Xersin.Sumsie
zelenkov.WixTrim
Zwift.Zwift
```

————————————————

Partially related:
* https://github.com/pl4nty/winget-extras/pull/200

And to my honest surprise, it also turns out that ISOs for 26H1 x64 do exist out there, making it possible to test/reproduce the situation if/when needed.

Contributor guide

Open the contributing guide

Research direction

Start with the Windows 11 26H1/.NET Framework 3.5 documentation and the affected manifests using Dependencies.WindowsFeatures: NetFx3; compare them with the PackageDependencies form and the related winget-extras pull request. Done means establishing a manifest approach that works on both 26H1 and earlier Windows versions, then applying or documenting it for the affected packages.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
operating-systems, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.