Skip to content

Windows Store Python package can't be used as a dynamic dependency #156127

Description

@tonyroberts

Bug report

Bug description:

Native (unpackaged) Win32 applications that want to embed the Microsoft Store build of Python in-process (e.g. loading python3xx.dll directly rather than spawning python.exe as a subprocess) need to call Windows 11's Dynamic Dependency API (TryCreatePackageDependency / AddPackageDependency) before they can load content out of the package's WindowsApps folder.

This currently fails for the Windows Store Python with HRESULT 0x80670016 ("Package dependency criteria could not be resolved"), even when the package family name, minimum version, and processor architecture passed to TryCreatePackageDependency are all correct.

The installed Python packages are main packages (Get-AppxPackage reports IsFramework: False), and their manifests don't declare the uap15 namespace or a uap15:DependencyTarget element. I think the resolution is failing because DependencyTarget isn't set.

I'm not 100% sure, but I think maybe all that's required is to add DependencyTarget=true to the properties in the manifest?

CPython versions tested on:

3.12 & 3.13

Operating systems tested on:

Windows 11

Metadata

Metadata

Assignees

No one assigned

    Labels

    OS-windowsbuildThe build process and cross-buildtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions