Forum Discussion
MSIX: Modification Package Layering still a problem in 18317
Hi, we looked at your package and noticed the MaxVersionTested is set to value that is early version of Windows.
Change this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.17763.0" />
to this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.18317.1" />
It works.
MicrosoftHi, we looked at your package and noticed the MaxVersionTested is set to value that is early version of Windows.
Change this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.17763.0" />
to this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.18317.1" />
It works.
This also fixed the problem for me as well. But I repackaged my Modification package with the new tool on an insider machine with build 18323. But even there I had to manually change the number. It would have been great if the Packaging Tool would have done that for me.
Great feedback. We are working on an update and should have it for the April release (which will align more to the 1903 OS changes).
John.
Uh, OK if that resolves it. The package wasn't generated on 18317, but with a version of the MPT that supports generating the correct syntax (if we ignore MaxVersionTested for a moment). I can live with that now that I know to use the full features of MPT 1.2019.1 I need to package on 18317 or above also.
But why should "MaxVersionTested" prevent fixes in the VFS layering runtime from being used? Surely we won't have to repackage to get the use of fixes in the runtime going forward?
