Event log warnings on schemas.

[TIMOTHY MANGAN]

If you package an app up using the Microsoft MSIX Packaging Tool, the AppXManifest file references a number of schemas.

When you install the package on a Windows 10 1204 based machine you will find a number of warnings in the Windows/AppxPackagingOM/Operational log, all similar to this:

App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/manifest/uap/windows10/10 is inapplicable, it will be ignored during manifest processing.

I am seeing this for 4 of the schemas each time a package is installed.  That probably shouldn't be happening.  Perhaps it is causing no harm and is just a check that shouldn't be putting out the events, but perhaps there is something more sinister going on...

[#2]

Hi @TIMOTHY MANGAN,

The namespace you reference should be UAP10 which should be supported in build 2004.

Assuming you meant windows build 2004, that error message does look odd.  We'll take a closer look.

If you meant a different windows build, please let me know! I don't recognize 1204 as a released build.

Thanks!
James

[#3]

@James Pike Sorry about the typo, yes I meant 2004.

The syntax being complained about is present by default on packages generated by the Microsoft MSIX Packaging Tool.  I only called out one, but I think there were about three different refences generating warning events PER package.

The packages in question seem to be OK in spite of those warnings.

[#4]

Hi @TIMOTHY MANGAN ,

These warnings are a result of the max tested version the packaging tool is setting on generated packages.  It was an oversight in the tool and we will correct it in the future.

In the meantime, if your package actually relies on any entries in the UAP10 or other namespaces you are seeing warnings for, you can manually correct the max tested version in the generated manifest.

Thanks!
James

[#5]

@James Pike Would the lower MaxTested value in those packages cause a difference in functionality when deploying to OS 2004?  I recall it affecting a feature on 1903 previously.

[#6]

Hi @TIMOTHY MANGAN,

The max tested version alters compatibility behavior of the application.  The system will adjust platform behavior to mimic the version specified.

In this case, you may see that the namespaces that are newer than the max version tested may not have the full desired effect unless you update the max version tested field.

As long as your package isn't using any of the features in the new manifest namespaces, you most likely will observe no functional problems.  Future versions of the packaging tool will take this into account and align the max tested version with the up to date toolchain/release. 

Thanks!
James

[#7]

@James Pike Perhaps Microsoft should consider a change in enforcement.

If an application package contains valid information that would work with extended functionality offered in a new version, especially if it asked for that functionality and it was previously ignored, I think that the system should grant that new functionality in spite of any MaxTested field.  

I previously ran into this with Modification Packages that wouldn't overlay the modified files properly unless we changed this MaxTested field.  Once the OS had the ability to perform this layering, why should it ignore the modified files just because of this field?  I think MSIX will be easier for everyone to understand if that field was just ignored by the runtime.

[#8]

Hi @TIMOTHY MANGAN,

I've pointed out your feedback to the relevant teams.

Thanks!
James