If there's a bug, I will find it! (bug adding two Appx packages into latest Win10 22H2)

[ZorkLVM]

See attached screenshots.

To reproduce:

1. Download latest Microsoft.YourPhone_8wekyb3d8bbwe and Microsoft.ZuneMusic_8wekyb3d8bbwe
2. Load current Win10 22H2 iso into NTLite
3. Try adding two appx packages to UPDATES (ignore erroneous "this package is older" message)
4. Try creating iso, the two appx packages are skipped

Workaround for now is to hand-edit install.wim. Big pain.

 

[tistou77]

There was the same problem with Notepad and another App, quite simple to fix, from memory
To see with nuhi

 

[ZorkLVM]

nuhi

None of these packages willl integrate into Win11 24h2 due to various errors, but mostly NTLite falsely thinking the newer packages to be integrated are older than the existing -- similar to the Win10 issues above.

Microsoft.ApplicationCompatibilityEnhancements_8wekyb3d8bbwe
Microsoft.AV1VideoExtension_8wekyb3d8bbwe
Microsoft.AVCEncoderVideoExtension_8wekyb3d8bbwe
Microsoft.BingNews_8wekyb3d8bbwe
Microsoft.BingSearch_8wekyb3d8bbwe
Microsoft.BingWeather_8wekyb3d8bbwe
Microsoft.GamingApp_8wekyb3d8bbwe
Microsoft.GetHelp_8wekyb3d8bbwe
Microsoft.HEIFImageExtension_8wekyb3d8bbwe
Microsoft.HEVCVideoExtension_8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe
Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe
Microsoft.MPEG2VideoExtension_8wekyb3d8bbwe
Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
Microsoft.RawImageExtension_8wekyb3d8bbwe
Microsoft.ScreenSketch_8wekyb3d8bbwe
Microsoft.Todos_8wekyb3d8bbwe
Microsoft.VP9VideoExtensions_8wekyb3d8bbwe
Microsoft.WebMediaExtensions_8wekyb3d8bbwe
Microsoft.WebpImageExtension_8wekyb3d8bbwe
Microsoft.Windows.DevHome_8wekyb3d8bbwe
Microsoft.WindowsAlarms_8wekyb3d8bbwe
Microsoft.WindowsCalculator_8wekyb3d8bbwe
Microsoft.WindowsCamera_8wekyb3d8bbwe
Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe
Microsoft.Xbox.TCUI_8wekyb3d8bbwe
Microsoft.XboxGamingOverlay_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider_8wekyb3d8bbwe
Microsoft.XboxSpeechToTextOverlay_8wekyb3d8bbwe
Microsoft.YourPhone_8wekyb3d8bbwe
MicrosoftCorporationII.MicrosoftFamily_8wekyb3d8bbwe
MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy
MicrosoftWindows.CrossDevice_cw5n1h2txyewy

There are also dependency parsing problems with these (NTLite doesn't have the correct dependency data, or is parsing it wrong):

Integrating: News + Dependencies - Error 0xc1570117 - [279]
Integrating: MSN Weather + Dependencies - Error 0xc1570117 - [279]
Integrating: Xbox App + Dependencies - Error 0xc1570117 - [279]

 

[garlin]

3. Try adding two appx packages to UPDATES (ignore erroneous "this package is older" message)

This isn't actually a bug, but a correct reflection of MS's versioning strategy for the different families of W10 & W11 Apps.

NTLite will read the package's AppxManifest.xml to determine if the version number is higher or lower, than the currently installed package. The manifest only provides a version number, there is no release date to read.

Version number is a data type defined by:

- Major number​

- Minor number​

- Build​

- Revision​

W10 was released with an initial group of default Apps. Some of which were later completely rewritten for W11 releases. MS has decided W10 users won't receive the W11 app versions as updates (in order to encourage them to upgrade, rather than stay on W10).

The version numbers of what Appx packages can be downloaded from MS servers can be confusing.

- W10-only apps can be recognized, because they use the app's release year as the Major number.​

- W11-only apps can be recognized, because they have a non-calendar year as the Major number. This prevents W10 users from receiving W11 app updates, because 20[xx] > 10 or 11.​

- UWP Framework packages try to use some different number based on the package's family version.​

To further add to the confusion, a "W10 app" will probably run fine on W11. And "W11 app" will probably run on W10. The only problem is including the right set of required UWP framework libraries. Which is the bug you see here when loading dependencies.

 

[ZorkLVM]

Thanks for the info, garlin. I assumed NTLite did it's own custom check rather than a simple greater-than/less-than check to determine if a package is newer or older.

Another solution would be to have NTLite ignore the version string altogether and just do what the user requests. If it bricks their build, hey, that's the power of NTLite.

My concolusion with the apps below is that it's not possible to integrate them because Microsoft delivers them (via https://store.rg-adguard.net/) in a way that makes them impossible to integrate:

Microsoft.BingNews_4.8.11001.0_neutral_~_8wekyb3d8bbwe.msixbundle
Microsoft.BingWeather_4.54.63007.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.GamingApp_2412.1001.25.0_neutral_~_8wekyb3d8bbwe.msixbundle

Error: 0xc1570117

The specified package is not a bundle containing a stub package. A stub package is required when the InstallStub option is
specfied, or the package family's stub preference is configured to install a stub package.

I can't find the stub packages available for download and the included stub packages on 24H2 are not usable with dism's `/DependencyPackagePath:`.