How do I configure my appxmanifest so that it can only be installed on Windows 11 and newer?

Question

How do I configure my appxmanifest so that it can only be installed on Windows 11 and newer?

Anne Admin 21

For example I have an appxmanifest which includes:

  <Dependencies>
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.26100.0" MaxVersionTested="10.0.26226.0" />
  </Dependencies>

How can I make it so that Windows store doesn't even offer installation as an option if you are on Windows 10?

0 comments

2 answers

Your answer

Answer 1

Danny Nguyen (WICLOUD CORPORATION) 6,865 Microsoft External Staff Moderator

Hi,

To make the package installable only on Windows 11 (and future builds), just raise the MinVersion in your TargetDeviceFamily to the first Windows 11 build number (or a later one if you prefer). Windows 11 still reports its OS version with major/minor 10.0; the distinction from Windows 10 is in the build number.

Windows build number landmarks (desktop):

Windows 10 final servicing builds: 19041 / 19042 / 19043 / 19044 / 19045 (21H2/22H2) – all < 20000
Windows 11 21H2: 22000
Windows 11 22H2 / 23H2 base: 22621 / 22631
Windows 11 24H2: 26100 (GA)

(Your 26226 looks like a newer flight / Insider build.)

So if you set MinVersion to 10.0.22000.0 you exclude all Windows 10 devices. Anything below build 22000 (i.e., Windows 10) will not meet the dependency and the Store will not offer Install.

Example:

<Dependencies>
<TargetDeviceFamily

      Name="Windows.Desktop"

      MinVersion="10.0.22000.0"

      MaxVersionTested="10.0.26226.0" />
</Dependencies>

Notes:

MinVersion is the hard floor: the app will not install on lower OS builds.
MaxVersionTested is NOT a cap; it tells the Store/OS what you’ve validated against. Higher builds can still install; the OS may apply compatibility modes if needed.

Pick the earliest Windows 11 build you intend to support (usually 22000 or 22621 if you rely on newer APIs) and set that as MinVersion. That’s all you need.

As Linhnguyen Hanoi has pointed out, you can also check for which packages will be offered to specific Windows 10 or Windows 11 device families under Packages section in Microsoft Partner Center.

A screenshot showing the overview of packages already uploaded page for MSIX/PWA app.

For more information, check out Upload MSIX app packages - Windows apps | Microsoft Learn

Also if you want a guide on how to publish Windows apps through Microsoft store, check out this documentation Publish Windows apps and games to Microsoft Store - Windows apps | Microsoft Learn

I hope this helps. Feel free to reach out if you need any help.

sysadmin 140 Reputation points

2025-10-23T04:43:51.1333333+00:00

Haven't I already done that? I've set minversion to 10.0.26100.0 so it shouldnt be offered on anything older than 24H2
Danny Nguyen (WICLOUD CORPORATION) 6,865 Reputation points Microsoft External Staff Moderator

2025-10-23T11:00:32.0433333+00:00

Yes, you have, I just want to clarify that part. As for not having a deselect option for Windows 10, I think your manifest file already does that. You might want to test it out beforehand though.
sysadmin 140 Reputation points

2025-10-23T22:27:24.15+00:00

I have deployed a manifest with these settings but Windows 10 PCs are still allowed to install it
Danny Nguyen (WICLOUD CORPORATION) 6,865 Reputation points Microsoft External Staff Moderator

2025-10-24T09:59:58.9133333+00:00
I suggest following this quick check list if you can

Confirm the built package actually has the raised MinVersion: unzip the .msix/.msixbundle → open AppxManifest.xml → look for <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.26100.0" ... />.

Ensure there is ONLY one TargetDeviceFamily entry (no leftover Windows.Universal or another Windows.Desktop with a lower MinVersion).

Check the .csproj: <TargetPlatformMinVersion>10.0.26100.0</TargetPlatformMinVersion> (if this is lower, it will overwrite your manual edit).

Uninstall any prior version on the Windows 10 test machine before retrying (avoid launching an already-installed older build).

sysadmin 140

Here is the whole appxmanifest, can you see anything that would explain why win10 is still allowed to install it, or is this a bug?

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Package IgnorableNamespaces="uap uap5 rescap desktop3 build" xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" xmlns:desktop3="http://schemas.microsoft.com/appx/manifest/desktop/windows10/3" xmlns:uap5="http://schemas.microsoft.com/appx/manifest/uap/windows10/5" xmlns:build="http://schemas.microsoft.com/developer/appx/2015/build" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest">
  <Identity Name="iCognitionAustralia.46016B8C4577E" Publisher="CN=7FDBC02D-974B-467D-91BA-0EAF515DB855" Version="1.0.57.0" ProcessorArchitecture="x64" />
  <Properties>
<DisplayName>Ingress</DisplayName>
<PublisherDisplayName>iCognition Pty Ltd</PublisherDisplayName>
<Logo>Assets\StoreLogo.png</Logo>
  </Properties>
  <Dependencies>
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.22000.0" MaxVersionTested="10.0.22000.0" />
<PackageDependency Name="Microsoft.WindowsAppRuntime.1.8" MinVersion="8000.642.119.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
  </Dependencies>
  <Resources>
<Resource Language="EN-AU" />
  </Resources>
  <Applications>
<Application Id="App" Executable="Ingress.exe" EntryPoint="Windows.FullTrustApplication">
  <uap:VisualElements DisplayName="Ingress" Description="Ingress" BackgroundColor="transparent" Square150x150Logo="Assets\Square150x150Logo.png" Square44x44Logo="Assets\Square44x44Logo.png">
    <uap:DefaultTile Wide310x150Logo="Assets\Wide310x150Logo.png" Square71x71Logo="Assets\SmallTile.png" Square310x310Logo="Assets\LargeTile.png" ShortName="Ingress">
      <uap:ShowNameOnTiles>
        <uap:ShowOn Tile="square150x150Logo" />
        <uap:ShowOn Tile="square310x310Logo" />
        <uap:ShowOn Tile="wide310x150Logo" />
      </uap:ShowNameOnTiles>
    </uap:DefaultTile>
    <uap:SplashScreen Image="Assets\SplashScreen.png" BackgroundColor="transparent" />
  </uap:VisualElements>
  <Extensions>
    <desktop3:Extension Category="windows.cloudFiles">
      <desktop3:CloudFiles IconResource="Assets\ingress_icon_black_256.png" />
    </desktop3:Extension>
    <uap5:Extension Category="windows.startupTask">
      <uap5:StartupTask TaskId="IngressStartupTask" Enabled="false" DisplayName="Ingress" />
    </uap5:Extension>
    <uap:Extension Category="windows.protocol">
      <uap:Protocol Name="trimwebdavedit">
        <uap:DisplayName>Ingress WebDav Edit</uap:DisplayName>
      </uap:Protocol>
    </uap:Extension>
  </Extensions>
</Application>
  </Applications>
  <Capabilities>
<Capability Name="internetClient" />
<rescap:Capability Name="runFullTrust" />
  </Capabilities>
  <Extensions>
<Extension Category="windows.activatableClass.inProcessServer">
  <InProcessServer>
    <Path>Microsoft.Web.WebView2.Core.dll</Path>
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2CustomSchemeRegistration" ThreadingModel="both" />
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2ControllerWindowReference" ThreadingModel="both" />
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2EnvironmentOptions" ThreadingModel="both" />
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2Controller" ThreadingModel="both" />
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2Environment" ThreadingModel="both" />
    <ActivatableClass ActivatableClassId="Microsoft.Web.WebView2.Core.CoreWebView2CompositionController" ThreadingModel="both" />
  </InProcessServer>
</Extension>
  </Extensions>
  <build:Metadata>
<build:Item Name="Microsoft.UI.Xaml.Markup.Compiler.dll" Version="3.0.0.2509" />
<build:Item Name="makepri.exe" Version="10.0.26100.6584 (WinBuild.160101.0800)" />
  </build:Metadata>
  <mp:PhoneIdentity PhoneProductId="eee392d6-5609-4bfe-a6f6-d7d4f653cffc" PhonePublisherId="403f2a5a-9bdf-4993-8707-10cf5c149e29" />
</Package>

Danny Nguyen (WICLOUD CORPORATION) 6,865 Reputation points Microsoft External Staff Moderator

2025-10-24T10:44:11.7033333+00:00

I took a look of yours and it seems fine. Maybe this has something to do with the package on your Windows 10 setup? Unzip msix file you installed and open AppxManifest.xml inside it to confirm the MinVersion?

Also, might be unrelated but if it's a bundle, none of them should have a lower MinVersion.
Danny Nguyen (WICLOUD CORPORATION) 6,865 Reputation points Microsoft External Staff Moderator

2025-10-28T03:29:38.7133333+00:00

just checking in, is there any update on this problem?
sysadmin 140 Reputation points

2025-10-28T03:44:46.7933333+00:00

It must have been a caching issue because its fixed itself with no changes from us
Danny Nguyen (WICLOUD CORPORATION) 6,865 Reputation points Microsoft External Staff Moderator

2025-10-28T03:55:09.0566667+00:00

Great to hear the issue is resolved.

If you found my earlier response helpful, kindly consider marking it as the final solution so others can benefit too. Thank you.

Answer 2

Linhnguyen Hanoi 75

According to your description, you have already set the minimum version requirement in the app list. And then when you create an app submission in Partner Center, you could configure the system requirements in the properties and In the Device family availability section, you could deselect all Windows 10 related options.

You could refer to the Doc: Create app submission

sysadmin 140 Reputation points

2025-10-23T04:47:07.2633333+00:00

There is no way to deselect Windows 10 without also deselecting Windows 11
Linhnguyen Hanoi 75 Reputation points

2025-10-24T02:34:54.0966667+00:00

When you set the MinVersion, the store should automatically handle compatibility checks. If the Windows 10 PCs are still allowed to install it, I suggest you could check the actually deployed manifest via powershell.

Share via

How do I configure my appxmanifest so that it can only be installed on Windows 11 and newer?

2 answers

Your answer