How to fix APPX0702 errors?

Question

• [visual-studio], [msix] [windows-packaging-project].
• I have already deleted the bin, obj, and emptiedAppPackages folders

Answer 1

APPX0702 is a packaging/deployment failure that typically maps to an underlying APPX/DEP error. The fix depends on the inner error code shown in the Output or Error List window (for example, APPX_E_INVALID_MANIFEST, APPX_E_MISSING_REQUIRED_FILE, 0x80073CF0, etc.). Use these steps to identify and resolve the root cause:

1. Inspect the detailed error in Visual Studio
   1. Rebuild the Windows Packaging Project.
   2. In Visual Studio, open View → Output, select Build or Deploy from the dropdown.
   3. Locate the APPX0702 line and note any inner error code such as:
      • APPX_E_INVALID_MANIFEST (0x80080204)
      • APPX_E_MISSING_REQUIRED_FILE (0x80080203)
      • APPX_E_CORRUPT_CONTENT (0x80080206)
      • A deployment error like 0x80073CF0, 0x80073CF6, etc.
2. If the inner error indicates a manifest problem Common codes: APPX_E_INVALID_MANIFEST (0x80080204), DEP0700, ERROR_INVALID_DATA (0x8007000D).
   1. Validate the package manifest:

            MakeAppx unpack /p "C:\path\to\app.msix" /d "C:\unpack-output"
      

   2. Open AppxManifest.xml in the unpacked folder and check:
      • XML is well-formed (no missing/extra tags).
      • Publisher exactly matches the signing certificate Subject (including spaces and capitalization).
      • Capabilities and namespaces are valid for the target OS version.
      • MinVersion/TargetDeviceFamily values are appropriate for the OS.
   3. Fix any issues, then rebuild and redeploy.
3. If the inner error indicates missing or invalid package files Common codes: APPX_E_MISSING_REQUIRED_FILE (0x80080203), APPX_E_INVALID_BLOCKMAP (0x80080205), APPX_E_CORRUPT_CONTENT (0x80080206).
   1. Ensure the package contains all required files:
      • \AppxManifest.xml
      • \AppxBlockMap.xml
      • If \AppxMetadata\CodeIntegrity.cat exists, ensure \AppxSignature.p7x is also present.
   2. Clean and rebuild the solution (already deleted bin, obj, AppPackages, which is correct) and let Visual Studio regenerate the package.
4. If the inner error is a deployment error (0x80073CFx, etc.) Match the code to the documented cause and fix:
   • 0x80073CF0 (ERROR_INSTALL_OPEN_PACKAGE_FAILED)
     • Verify the .msix file path and permissions.
     • Install from a local path (not a network share) and, if needed, run PowerShell as administrator.
   • 0x80073CF3 (ERROR_INSTALL_PACKAGE_DOWNGRADE)
     • A newer version is already installed.
     • Uninstall the existing package or increase the version in the manifest and rebuild.
   • 0x80073CF6 (ERROR_INSTALL_REGISTRATION_FAILURE)
     • Run wsreset -i to reset Store cache.
     • Run sfc /scannow to repair system files.
     • Try Settings → Installed apps → [App] → Advanced options → Repair and check Event Viewer for inner errors.
   • 0x80073CF9 (ERROR_INSTALL_PACKAGE_NOT_FOUND)
     • Ensure all dependency packages (VCLibs, .NET, Windows App SDK) are installed.
     • If installing via PowerShell, use:

              Add-AppxPackage main.msix -DependencyPath dep1.msix, dep2.msix
       

   • 0x80073CFB (ERROR_PACKAGE_ALREADY_EXISTS)
     • Remove the existing package:

              Get-AppxPackage <PackageName> | Remove-AppxPackage
       

   • 0x80073D02 (ERROR_PACKAGES_IN_USE)
     • Close all running instances of the app (Task Manager or Get-Process) before rebuild/deploy.
   • 0x8007000D (ERROR_INVALID_DATA)
     • Often a corrupt package or publisher mismatch.
     • Confirm the manifest Publisher matches the signing certificate subject, then rebuild and re-sign.
5. If the error mentions signing or trust
   • For trust issues like CertNotTrusted (0x8BAD0042):
     • Import the signing certificate into Local Computer → Trusted People on the target machine, or use a certificate from a trusted CA.
   • For invalid signature or SIP-related errors (for example APPX_E_INVALID_SIP_CLIENT_DATA 0x80080209):
     • Recreate and re-sign the package using the correct certificate and tooling.
6. If the error persists after fixes
   1. Confirm the Windows SDK and tools versions in Visual Studio match the project’s target/min versions.
   2. Repair Visual Studio and the Windows SDK if packaging components appear corrupted.
   3. Rebuild the solution and redeploy, then re-check the inner error code if APPX0702 still appears.

---

References:

• MSIX deployment troubleshooting
• MSIX troubleshooting guide
• Troubleshooting packaging, deployment, and query of Windows apps