app update on Windows store causes a 0X80073CF3 due to Microsoft.NET.Native.Framework.2.3 not being found

Question

app update on Windows store causes a 0X80073CF3 due to Microsoft.NET.Native.Framework.2.3 not being found

Karhu Koti 76

After submitting our latest version of our app with just a small code change, the app install from the Windows app store is encountering an error on both Windows 10 and 11 and the error is saying Microsoft.NET.Native.Framework.2.3 dependency is not found - but this framework is suppose to be provided by the app store from what we read.

Please help !

As our .417. version was working fine, after we submitted .420. to the app store, this issue started happening.

I can installed the versions manually via the powershell yesterday before submitting the latest package and that worked. But now, after I uninstall the app, I cannot install it via the app store nor the package manually – repro steps below.

There seems to be a bug in the app store. The .net 2.3 the install is complaining about is supposed to be installed by the app store.

Repro Steps

Install version .417. manually – this works ok.

PS C:\backup\files> Add-AppxPackage -Path ./Satellites_10.17763.417.0_x86_x64_arm64.msixbundle

Remove application via Program Files -> Satellite Tracking -> Uninstall – this works ok.

Install version .420. manually – this works ok.

PS C:\backup\files> Add-AppxPackage -Path ./Satellites_10.17763.420.0_x86_x64_arm64.msixbundle

Remove application via Program Files -> Satellite Tracking -> Uninstall – this works ok.

Now try to install .420. from the Windows app store – this fails with following error code.

0X80073CF3

Now try to install .420. again, which worked before, manually – the store install above broke something !

PS C:\backup\files> Add-AppxPackage -Path ./Satellites_10.17763.420.0_x86_x64_arm64.msixbundle

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.

Windows cannot install package 4191KarhuKoti.Satellites_10.17763.420.0_x64__sd64qgh20x0ty because this package depends on a framework that

could not be found. Provide the framework "Microsoft.NET.Native.Framework.2.3" published by "CN=Microsoft Corporation, O=Microsoft Corporation,

L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 2.3.0.0, along with this package to install. The

frameworks with name "Microsoft.NET.Native.Framework.2.3" currently installed are: {}

NOTE: For additional information, look for [ActivityId] 78ef5fe0-5c8b-0002-61a2-f4788b5cdc01 in the Event Log or use the command line

Get-AppPackageLog -ActivityID 78ef5fe0-5c8b-0002-61a2-f4788b5cdc01

At line:1 char:1

Add-AppxPackage -Path ./Satellites_10.17763.420.0_x86_x64_arm64.msixb ...

+ CategoryInfo : WriteError: (C:\backup\files...rm64.msixbundle:String) [Add-AppxPackage], IOException

+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

PS C:\backup\files> Get-AppPackageLog -ActivityID 78ef5fe0-5c8b-0002-61a2-f4788b5cdc01

Time ID Message

---- -- -------

11/24/2025 8:13:07 PM 603 Started deployment Add operation on a package with main parameter

Satellites_10.17763.420.0_x86_x64_arm64.msixbundle and Options 0 and 0. See

http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.

11/24/2025 8:13:07 PM 164 The app bundle signature was validated for core content of the app bundle published by

CN=C225B717-F16C-40B6-8353-855341BBB69B. App packages won't be validated until they are read.

11/24/2025 8:13:07 PM 391 The bundle streaming reader was created successfully for bundle

4191KarhuKoti.Satellites_10.17763.420.0_neutral_~_sd64qgh20x0ty.

11/24/2025 8:13:07 PM 10002 Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\82283155-3a22-46ff-8e38-f16a50d3a

9fe_S-1-5-21-170124532-4292026490-2436934583-1001_39.rslc for Add Operation on Package

4191KarhuKoti.Satellites_10.17763.420.0_neutral_~_sd64qgh20x0ty.

11/24/2025 8:13:07 PM 607 Deployment Add operation on package 4191KarhuKoti.Satellites_10.17763.420.0_neutral_~_sd64qgh20x0ty has

been de-queued and is running for user SID S-1-5-21-170124532-4292026490-2436934583-1001.

11/24/2025 8:13:07 PM 614 Bundle Uri file:///C:/backup/files/Satellites_10.17763.420.0_x86_x64_arm64.msixbundle contains packages:

"Satellites_10.17763.420.0_x86.msix": 4191KarhuKoti.Satellites_10.17763.420.0_x86__sd64qgh20x0ty

"Satellites_10.17763.420.0_x64.msix": 4191KarhuKoti.Satellites_10.17763.420.0_x64__sd64qgh20x0ty

"Satellites_10.17763.420.0_ARM64.msix": 4191KarhuKoti.Satellites_10.17763.420.0_arm64__sd64qgh20x0ty

"Satellites_10.17763.420.0_scale-100.msix":

4191KarhuKoti.Satellites_10.17763.420.0_neutral_split.scale-100_sd64qgh20x0ty.

11/24/2025 8:13:07 PM 157 The app package signature was validated for core content of the app package published by

CN=C225B717-F16C-40B6-8353-855341BBB69B. Payload won't be validated until the files are read.

11/24/2025 8:13:07 PM 216 App manifest validation warning: Declared namespace

http://schemas.microsoft.com/developer/appx/2015/build is inapplicable, it will be ignored during

manifest processing.

11/24/2025 8:13:07 PM 170 The streaming reader was created successfully for app package

4191KarhuKoti.Satellites_10.17763.420.0_x64__sd64qgh20x0ty.

11/24/2025 8:13:07 PM 854 Successfully added the following uri(s) to be processed:

file:///C:/backup/files/Satellites_10.17763.420.0_x86_x64_arm64.msixbundle file:///C:/backup/files/Satell

ites_10.17763.420.0_x86_x64_arm64.msixbundle\Satellites_10.17763.420.0_x64.msix.

11/24/2025 8:13:07 PM 628 Windows cannot install package 4191KarhuKoti.Satellites_10.17763.420.0_x64__sd64qgh20x0ty because this

package depends on a framework that could not be found. Provide the framework

"Microsoft.NET.Native.Framework.2.3" published by "CN=Microsoft Corporation, O=Microsoft Corporation,

L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 2.3.0.0,

along with this package to install. The frameworks with name "Microsoft.NET.Native.Framework.2.3"

currently installed are: {}

11/24/2025 8:13:07 PM 605 The last successful state reached was Indexed. Failure occurred before reaching the next state Resolved.

hr: 0x80073CF3

11/24/2025 8:13:07 PM 401 Deployment Add operation with target volume C: on Package

4191KarhuKoti.Satellites_10.17763.420.0_neutral_~_sd64qgh20x0ty from:

(Satellites_10.17763.420.0_x86_x64_arm64.msixbundle) failed with error 0x80073CF3. See

http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.

11/24/2025 8:13:07 PM 404 AppX Deployment operation failed for package

4191KarhuKoti.Satellites_10.17763.420.0_neutral_~_sd64qgh20x0ty with error 0x80073CF3. The specific

error text for this failure is: Windows cannot install package

4191KarhuKoti.Satellites_10.17763.420.0_x64__sd64qgh20x0ty because this package depends on a framework

that could not be found. Provide the framework "Microsoft.NET.Native.Framework.2.3" published by

"CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64

processor architecture and minimum version 2.3.0.0, along with this package to install. The frameworks

with name "Microsoft.NET.Native.Framework.2.3" currently installed are: {}

Manually install .417. again – this works and restores the problem the app store broke. I can even install .420. manually again.

PS C:\backup\files> Add-AppxPackage -Path ./Satellites_10.17763.417.0_x86_x64_arm64.msixbundle

PS C:\backup\files> Add-AppxPackage -Path ./Satellites_10.17763.420.0_x86_x64_arm64.msixbundle

Fyi – this shows throughout the process.

PS C:\backup\files> Get-AppxPackage NET.Native.Framework | Select Name, Version, Architecture, PublisherId

Name Version Architecture PublisherId

---- ------- ------------ -----------

Microsoft.NET.Native.Framework.2.2 2.2.29512.0 X64 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.1.3 1.3.24211.0 X64 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.1.3 1.3.24211.0 X86 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.1.7 1.7.27413.0 X64 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.1.7 1.7.27413.0 X86 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.2.0 2.0.27427.0 X64 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.2.0 2.0.27427.0 X86 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.2.1 2.1.27427.0 X64 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.2.1 2.1.27427.0 X86 8wekyb3d8bbwe

Microsoft.NET.Native.Framework.2.2 2.2.29512.0 X86 8wekyb3d8bbwe

Danny Nguyen (WICLOUD CORPORATION) 5,165 Reputation points Microsoft External Staff Moderator

2025-11-25T08:22:48.5166667+00:00
Hi,

The failure is because the 10.17763.420.0 package now depends on Microsoft.NET.Native.Framework.2.3, and that framework is not actually present on the machines where the Store is trying to install the app.

Compare the manifests for 10.17763.417.0 and 10.17763.420.0 and confirm that 420 now has a <PackageDependency Name="Microsoft.NET.Native.Framework.2.3" … /> entry while 417 uses 2.2.

Rebuild the app with the same Windows 10 SDK / .NET Native toolchain that produced 417 so that the dependency is again Microsoft.NET.Native.Framework.2.2, and publish that as a new version.

If the toolchain must target 2.3 and you can’t revert, then this isn't your code probl: the Store isn’t provisioning Microsoft.NET.Native.Framework.2.3 even though your manifest is valid. In that case, open a ticket with Microsoft Store support and include your ActivityId and logs so they can enable or fix the framework for your app.

There isn’t a client‑side fix for normal users: you can only workaround it on dev machines by manually installing the Microsoft.NET.Native.Framework.2.3 framework package with Add-AppxPackage, but production installs must be serviced by the Store.

If you share your AppxManifest.xml for both 417 and 420, maybe we can find the core problem.

What should the app's manifest file look like for specifying the missing Microsoft.NET.Native.Framework.2.3 file ?

<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" IgnorableNamespaces="uap">  <Dependencies> <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" /> <PackageDependency Name="Microsoft.NET.Native.Framework.2.3" MinVersion="2.3.0.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies>  </Package>

However, you normally do not hand‑edit this yourself; Visual Studio and the .NET Native toolchain generate it based on:

The Windows SDK version you target.

The installed .NET Native tools.

So, the practical fix is:

Either rebuild with a toolset that targets 2.2 (or another framework version that actually ships to users),

Or, if 2.3 is required, have Microsoft enable/fix distribution of Microsoft.NET.Native.Framework.2.3, because normal users can’t install that framework manually.

There’s no reliable client‑side workaround for Store users; the only dev‑side workaround is manual framework install on test machines.
Karhu Koti 76 Reputation points

2025-11-25T10:28:55.35+00:00
This what the .417. and .420 say which has what has been defined for several years now below.

<Dependencies>

<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.16299.0" MaxVersionTested="10.0.18362.0" /> ``` </Dependencies> So something has changed elsewhere ???
Danny Nguyen (WICLOUD CORPORATION) 5,165 Reputation points Microsoft External Staff Moderator

2025-11-25T10:53:20.5866667+00:00

Microsoft.NET.Native.Framework.2.3 is injected by the build toolchain or the Store pipeline. That’s why your manifest hasn’t changed, but the 420 build suddenly depends on 2.3 and fails when that framework isn’t present.

Most likely something changed in your VS/Windows SDK/.NET Native toolset, or on the Store ingestion side.

To confirm, extract the final AppxManifest.xml from the 417 and 420 .msix packages (inside the bundles) and compare their <Dependencies> sections (not just the project file). If you can paste those two <Dependencies> blocks here, we can see exactly what changed.

Karhu Koti 76

They look the same to me. Am I missing something ? (folks said, including myself, said this issue started after OS updates - not sure if 100% true or not). Also, the app certificate folks didn't let me republish .417 (reason unknown currently) just saying didn't work with store.

Here is the .417:

<Dependencies>
<TargetDeviceFamily`` Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.18362.0"/>
<PackageDependency`` Name="Microsoft.UI.Xaml.2.8" MinVersion="8.2310.30001.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.NET.Native.Framework.2.2" MinVersion="2.2.27912.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.NET.Native.Runtime.2.2" MinVersion="2.2.28604.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.VCLibs.140.00" MinVersion="14.0.30704.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.30704.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
</Dependencies>

Here is .420:

<Dependencies>
<TargetDeviceFamily`` Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.18362.0"/>
<PackageDependency`` Name="Microsoft.UI.Xaml.2.8" MinVersion="8.2310.30001.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.NET.Native.Framework.2.2" MinVersion="2.2.27912.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.NET.Native.Runtime.2.2" MinVersion="2.2.28604.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.VCLibs.140.00" MinVersion="14.0.30704.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency`` Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.30704.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
</Dependencies>

Karhu Koti 76 Reputation points

2025-11-25T11:57:29.3766667+00:00

Danny - how should this proceed, it seems like an issue with the MS Store app, right ? How does the Windows Store app team get involved here ?

Steven Blom 11

I used a website called rg-adguard to get the download links for the MSIX that the store uses.

When I downloaded that version, my dependencies looked like this:

  <Dependencies>
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18362.0" MaxVersionTested="10.0.26100.0" />
    <TargetDeviceFamily Name="Windows.Team" MinVersion="10.0.18362.0" MaxVersionTested="10.0.26100.0" />
    <PackageDependency Name="Microsoft.UI.Xaml.2.8" MinVersion="8.2310.30001.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.NET.Native.Framework.2.3" MinVersion="2.3.0.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.NET.Native.Runtime.2.3" MinVersion="2.3.0.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.33519.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.33728.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
  </Dependencies>

Karhu Koti 76 Reputation points

2025-11-26T06:44:00.4666667+00:00

Thanks Steve - what VS version are you using ?
Danny Nguyen (WICLOUD CORPORATION) 5,165 Reputation points Microsoft External Staff Moderator

2025-11-26T10:20:32.3633333+00:00

in Partner Center, can you double‑check your latest submission to see if there are any new options or checkboxes that could affect packaging or target frameworks (e.g. updated target device families, automatic packaging updates, or using a newer SDK/toolset)?
Martin R 0 Reputation points

2025-11-26T10:40:04.4566667+00:00

We are encountering this issue as well.

Could it be related to updating Visual Studio to 17.14.21 ?
Steven Blom 11 Reputation points

2025-11-26T12:43:28.5266667+00:00

Thanks Steve - what VS version are you using ?

We're developing on both 2022 (17.14.19) and 2026 (18.0.0)
Our build server was recently updated to run MS Build tools 2022 (17.14.18/19, not sure which) and 2026 (18.0.0)

The build was executed using 2022.

in Partner Center, can you double‑check your latest submission to see if there are any new options

No, I've been unable to see any new options that weren't there the last time we published our app.
Steven Blom 11 Reputation points

2025-11-27T09:53:02.29+00:00

I heard news in the Windows Community Discord that this had been resolved. I've republished our package and it is now working as expected.
Bui Bao Chau 21 Reputation points

2025-11-27T18:29:21.2966667+00:00

Hey @Steven Blom what do you mean republished? rebuild with a higher version? No need to change anything in our app?

Answer accepted by question author

2 additional answers

Your answer

Karhu Koti 76 Reputation points

2025-11-25T10:28:55.35+00:00

This what the .417. and .420 say which has what has been defined for several years now below.

<Dependencies>

<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.16299.0" MaxVersionTested="10.0.18362.0" /> ``` </Dependencies> So something has changed elsewhere ???
Danny Nguyen (WICLOUD CORPORATION) 5,165 Reputation points Microsoft External Staff Moderator

2025-11-25T10:53:20.5866667+00:00

Microsoft.NET.Native.Framework.2.3 is injected by the build toolchain or the Store pipeline. That’s why your manifest hasn’t changed, but the 420 build suddenly depends on 2.3 and fails when that framework isn’t present.

Most likely something changed in your VS/Windows SDK/.NET Native toolset, or on the Store ingestion side.

To confirm, extract the final AppxManifest.xml from the 417 and 420 .msix packages (inside the bundles) and compare their <Dependencies> sections (not just the project file). If you can paste those two <Dependencies> blocks here, we can see exactly what changed.
Karhu Koti 76 Reputation points

2025-11-25T11:57:29.3766667+00:00

Danny - how should this proceed, it seems like an issue with the MS Store app, right ? How does the Windows Store app team get involved here ?
Steven Blom 11 Reputation points

2025-11-25T23:33:02.4566667+00:00

I used a website called rg-adguard to get the download links for the MSIX that the store uses.

When I downloaded that version, my dependencies looked like this:

<Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18362.0" MaxVersionTested="10.0.26100.0" /> <TargetDeviceFamily Name="Windows.Team" MinVersion="10.0.18362.0" MaxVersionTested="10.0.26100.0" /> <PackageDependency Name="Microsoft.UI.Xaml.2.8" MinVersion="8.2310.30001.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.NET.Native.Framework.2.3" MinVersion="2.3.0.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.NET.Native.Runtime.2.3" MinVersion="2.3.0.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.33519.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.33728.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies>
Karhu Koti 76 Reputation points

2025-11-26T06:44:00.4666667+00:00

Thanks Steve - what VS version are you using ?
Danny Nguyen (WICLOUD CORPORATION) 5,165 Reputation points Microsoft External Staff Moderator

2025-11-26T10:20:32.3633333+00:00

in Partner Center, can you double‑check your latest submission to see if there are any new options or checkboxes that could affect packaging or target frameworks (e.g. updated target device families, automatic packaging updates, or using a newer SDK/toolset)?
Martin R 0 Reputation points

2025-11-26T10:40:04.4566667+00:00

We are encountering this issue as well.

Could it be related to updating Visual Studio to 17.14.21 ?
Steven Blom 11 Reputation points

2025-11-26T12:43:28.5266667+00:00

Thanks Steve - what VS version are you using ?

We're developing on both 2022 (17.14.19) and 2026 (18.0.0)
Our build server was recently updated to run MS Build tools 2022 (17.14.18/19, not sure which) and 2026 (18.0.0)

The build was executed using 2022.

in Partner Center, can you double‑check your latest submission to see if there are any new options

No, I've been unable to see any new options that weren't there the last time we published our app.
Steven Blom 11 Reputation points

2025-11-27T09:53:02.29+00:00

I heard news in the Windows Community Discord that this had been resolved. I've republished our package and it is now working as expected.
Bui Bao Chau 21 Reputation points

2025-11-27T18:29:21.2966667+00:00

Hey @Steven Blom what do you mean republished? rebuild with a higher version? No need to change anything in our app?

Answer 1

Hi,

Since there has been definitive reason as well as resolution to this problem, I would like to create a summarize response to this post. If you find this helpful, please mark it as the final solution.

The install/update failure with error 0x80073CF3 (“missing Microsoft.NET.Native.Framework.2.3”) is typically not caused by a change in the app’s own manifest when the manifest still declares .NET Native framework/runtime 2.2. Affected submissions showed identical <Dependencies> blocks like:


<PackageDependency Name="Microsoft.NET.Native.Framework.2.2" MinVersion="2.2.27912.0" ... />

<PackageDependency Name="Microsoft.NET.Native.Runtime.2.2"  MinVersion="2.2.28604.0" ... />

Manual sideload (Add-AppxPackage) of the original MSIX/MSIXBundle succeeds, proving the locally built package is valid; the failure appears only when installing from the Microsoft Store, which then reports a requirement for Microsoft.NET.Native.Framework.2.3 that is not installed on the machine.

Root Cause

A Microsoft Store ingestion pipeline regression can mutate or re-bind submitted packages to newer dependency versions (e.g. .NET Native Framework/Runtime 2.3, newer VCLibs, modified TargetDeviceFamily entries). If those updated frameworks are not yet provisioned on the target OS, installation fails with 0x80073CF3 and a “framework could not be found” message.

Resolution

Microsoft has addressed the ingestion pipeline issue. Incrementing the app’s version and resubmitting triggers a fresh compilation/binding step that restores correct dependencies and allows normal Store installation.

Recovery Steps

Increment the app/package version (e.g. X.Y.Z.N → X.Y.Z.(N+1)).
Rebuild exactly as before .
Resubmit the new version in Partner Center.

After publication, verify on a clean test machine or VM:


   # List installed .NET Native frameworks

   Get-AppxPackage NET.Native.Framework | Select Name, Version

   # (Optional) Retrieve your app’s install location

   Get-AppxPackage <YourPackageFamilyName> | Select PackageFullName, InstallLocation

Open the installed AppxManifest.xml in the app’s InstallLocation and confirm <Dependencies> still reference the intended versions (2.2 unless Microsoft has confirmed 2.3 deployment).
Launch and smoke‑test the app.

Hope this helps.

Answer 2

Tom McDonald 5 Microsoft Employee

Hello! I am very sorry to hear about the store app publish problem!!! The store ingestion pipeline issue has been corrected, and so please try incrementing the package version and resubmitting through Partner Center. This should retrigger app compilation in the ingestion pipeline and correct the issue in the store. In the future, please feel free to reach out to us directly at dotnetnative@microsoft.com for direct help!

Tom

Karhu Koti 76 Reputation points

2025-11-27T20:31:14.55+00:00

Hi Tom, what was the root cause of the bug ?

Answer 3

The error code 0x80073CF3 indicates that the installation of your app is failing due to a missing dependency, specifically the Microsoft.NET.Native.Framework.2.3. This framework is supposed to be provided by the Windows Store, but it seems that it is not being installed correctly in your case.

Here are some steps you can take to troubleshoot and potentially resolve this issue:

Check Installed Frameworks: Make sure that the required version of the .NET Native Framework is indeed missing. You can do this by running the command:
```
   Get-AppxPackage *NET.Native.Framework* | Select Name, Version, Architecture, PublisherId
```
This will show you all installed versions of the .NET Native Framework.
Manual Installation: Since you mentioned that you can install the framework manually, you might want to ensure that Microsoft.NET.Native.Framework.2.3 is installed before attempting to install your app from the store. You can download the necessary framework package from the official Microsoft site if available.
Check App Manifest: Ensure that your app's manifest file correctly specifies the dependencies, including the required version of Microsoft.NET.Native.Framework. If the manifest is incorrect, it might lead to installation issues.
Rebuild and Resubmit: If the issue persists, consider rebuilding your app with the correct dependencies and resubmitting it to the Windows Store. Sometimes, a small change can inadvertently affect dependencies.
Event Logs: Look into the Event Log for more detailed error messages related to the installation failure. You can use the command:
```
   Get-AppPackageLog -ActivityID <YourActivityID>
```
Replace <YourActivityID> with the ID provided in the error message for more context on what went wrong.
Contact Support: If none of the above solutions work, it may be beneficial to contact Microsoft support for assistance, as they can provide insights specific to the Windows Store and app deployment issues.

By following these steps, you should be able to identify and resolve the issue with the missing framework dependency.

Karhu Koti 76 Reputation points

2025-11-24T20:04:28.09+00:00

What should the app's manifest file look like for specifying the missing Microsoft.NET.Native.Framework.2.3 file ?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Victor Chen 111 Reputation points

2025-11-27T06:11:20.72+00:00

@Karhu Koti Hi, I ran into the same issue—how did you solve it? I believe this is 100% a Windows Store issue, it changed our dependency on Microsoft.NET.Native.Framework from 2.2 to 2.3.

Share via

app update on Windows store causes a 0X80073CF3 due to Microsoft.NET.Native.Framework.2.3 not being found

2 additional answers

Your answer