TargetPlatformMinVersion confusion

Heiko 1,216 Reputation points

I want to make my app (WPF desktop bridge with .NET Framework) also available for arm64, for Windows 10 and Windows 11. On this page it is mentioned that arm64 is supported from Windows 10 20H2. Now I select the TargetPlatformMinVersion under Windows 11 in VS 2022 in the settings of my project and see 'Windows 10, version 2104 (10.0; Build 20348)'. However, the current Windows 10 version 22H2 has the build number 19045. Why is there only the build number 20348 and not 19045?

I have the app in the store with the following versions:

1.3.6 (created with VS 2017 under Windows 10 22H2; x86, x64)

1.4.0 (created with VS 2022 under Windows 11 21H2; x86, x64, arm64)

When I install my app from the store on Windows 10 22H2 Build 19045 x64, version 1.3.6 is installed. Since I have set 'Windows 10, version 2104 (10.0; Build 20348)' as TargetPlatformMinVersion, I would have expected version 1.4.0 to be installed on Windows 10 22H2.

The latest Windows 10 version is 22H2 build 19045. How can I make an app that supports x86, x64, arm64 available for Windows 10?



Windows Presentation Foundation
Windows Presentation Foundation
A part of the .NET Framework that provides a unified programming model for building line-of-business desktop applications on Windows.
2,710 questions
Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,871 questions
Microsoft Partner Center
Microsoft Partner Center
A Microsoft website for partners that provides access to product support, a partner community, and other partner services.
927 questions
0 comments No comments
{count} votes

Accepted answer
  1. Hui Liu-MSFT 47,336 Reputation points Microsoft Vendor

    Hi,@Heiko.Welcome to Microsoft Q&A Forum.
    When setting the TargetPlatformMinVersion in Visual Studio for your WPF desktop bridge app, it is essential to understand how this setting affects the compatibility and deployment of your application across different Windows versions.

    Target Platform Version (TargetPlatformVersion):

    This represents the version of the Windows SDK against which your app is compiled.

    Setting this to a higher version allows your app to take advantage of new APIs and features introduced in that SDK version.

    The target platform version doesn't restrict the app from running on lower versions, but it limits the app's access to newer APIs.

    Minimum Version (TargetPlatformMinVersion):

    This indicates the minimum version of the OS that your app can run on.

    It doesn't affect the compilation of your app; it's used to specify the minimum version your app can run on.

    Setting this to a higher version ensures that your app won't be installed on devices running versions below the specified one.

    Regarding your specific questions and concerns:

    Build Numbers:

    Build numbers are specific to each Windows version and represent the cumulative updates and patches.

    The number "20348" is likely related to an SDK version rather than a specific OS build.

    When specifying the minimum version, you typically choose a major version (e.g., 10.0) and allow your app to run on any build within that version.
    App Versioning and Store Deployment:

    The versioning of your app in the Store is managed independently of the target platform and minimum version settings.

    Windows Store uses the app's manifest and the supported OS versions to determine which version to deploy on a particular device.

    Ensuring Compatibility with Windows 10:

    To ensure compatibility with Windows 10 (including arm64), set your TargetPlatformMinVersion to a version that encompasses the Windows 10 builds you want to support.

    Verify that your app's manifest correctly reflects the supported architectures (x86, x64, arm64).

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 additional answers

Sort by: Most helpful