Unable to install latest betas from ftp .msix or MS store (on Win10?)

[DavidCEllis]

Describe the bug
When trying to install the latest betas (b4 or b5) from the .msix from the FTP site I get an "Error in parsing the app package." message and a failed install. Attempting to install via the MS store also fails with "There has been an error".

b3 installs from the .msix with no issue so it looks like a change in the .msix for b4/b5. The .msi installer for b5 also works although after using it I understand the desire to move to .msix as it gives even less indication that the install was successful.

To Reproduce
Try to install the latest betas on a Windows 10 machine from the b4 or b5 .msix files. Same result on 2 different Win10 machines, I don't have a Win11 machine to test with.

Additional context

I see this in the applications and services logs as a new error under AppxPackagingOM when I try to run the .msix installer so I think it's related - I see the same error appear when trying to install from the Windows store:

error 0xC00CE014: App manifest validation error: The app manifest must be valid as per schema: Line 135, Column 18, Note: The schema for MaxVersionTested specified does not recognize XML fields with namespace "http://schemas.microsoft.com/appx/manifest/com/windows10/4". Please ensure that you have the correct MaxVersionTested specified. Reason: Element '{http://schemas.microsoft.com/appx/manifest/com/windows10/4}Extension' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Extensions'.
Expecting: {http://schemas.microsoft.com/appx/manifest/foundation/windows10}ApplicationExtensionChoice, {http://schemas.microsoft.com/appx/manifest/foundation/windows10}ExtensionChoice.

[zooba]

Apparently we need to mark the com4 namespace as ignorable (and you won't get the "Edit in IDLE" context menu in Win10).

Easy fix, it'll be in the next beta. If you've got b3 installed then the auto update should eventually skip to it when it's released, and I assume it'll silently keep failing to update to b5 in the meantime.

[DavidCEllis]

I currently have the .msi install for b5 as I wanted to check there weren't any command/format changes in the new betas as I'm working on adding support to install runtimes with pymanager in ducktools-pytui.

Will switch back to the .msix for the next release.

[efimov-mikhail]

I'm also have a similar issue when trying to install b5 on Windows 10 Pro.
Unfortunately, I don't know how to "get deeper" and obtain some useful logs.

But I definitely can try to install another version since it has appeared.

[zooba]

Thanks. I'm not going to make a release on a Friday night, but I'll do an update on Monday to fix this.

[zooba]

@DavidCEllis @efimov-mikhail There's a new release up at https://www.python.org/ftp/python/pymanager/. Please let me know asap if it doesn't install on Win10

[DavidCEllis]

@zooba .msix install worked fine 👍

[zooba]

Thanks!

[pfmoore]

Out of curiosity, is it intended that it will autoupdate? My installation came from manually running (from the CLI) a copy of python-manager-25.0b5.msix that I'd previously downloaded from python.org, so it's the worst possible case for an autoupdate, but if there's an expectation that it might autoupdate, I'll leave it for a while and see if it does...

[AA-Turner]

@pfmoore what is your output from running Get-AppxPackageAutoUpdateSettings | ft PackageFamilyName, LastCheckedForUpdates, Version, AppInstallerUri in a powershell session?