Share via

Microsoft Partner Center – Submission Options showing “Incomplete” despite all fields filled (runFullTrust capability used)

Satish Kulkarni 20 Reputation points
2026-04-17T07:12:53.2+00:00

Hi Team,

I am submitting a Windows application (MSIX packaged desktop app) to Microsoft Store via Partner Center and facing an issue where the submission remains “Incomplete” even after completing all required sections.

🧩 App Details

  • App Type: Packaged Win32 (Desktop Bridge / MSIX)
  • Capability Used: runFullTrust (restricted capability)
  • Package: Successfully validated
  • Store listing: Completed
  • Age rating: Completed
  • Properties: Completed
  • Additional Testing Information: Provided
  • Credentials: Not required (no login-based functionality)

⚠️ Issue Description

The “Submission Options” section continues to show “Incomplete” even after:

  • Selecting:
    • ✔ “Publish this submission as soon as it passes certification”
    • Clicking Save multiple times
    • Refreshing the page
    • Trying different browser sessions

🔍 Additional Context

  • The app uses runFullTrust capability, and I have already:
    • Provided detailed justification in the restricted capabilities section
      • Confirmed that this is required for: 
        - Local AI model execution

      - File system access

            - Bundled executable (GenieUI.exe)

            - Based on Microsoft documentation:

               - `runFullTrust` is expected for packaged desktop apps

                  - Restricted capabilities require explanation but should not block submission completion

❓ Questions

  1. Can the presence of runFullTrust capability cause the Submission Options section to remain incomplete?
  2. Is there any additional approval step or hidden field required specifically for restricted capabilities?
  3. Could this be a UI/backend issue in Partner Center not reflecting saved state?
  4. Are there any logs or validation details I can check to identify the missing requirement?Hi Team, I am submitting a Windows application (MSIX packaged desktop app) to Microsoft Store via Partner Center and facing an issue where the submission remains “Incomplete” even after completing all required sections.

    🧩 App Details

    • App Type: Packaged Win32 (Desktop Bridge / MSIX)
    • Capability Used: runFullTrust (restricted capability)
    • Package: Successfully validated
    • Store listing: Completed
    • Age rating: Completed
    • Properties: Completed
    • Additional Testing Information: Provided
    • Credentials: Not required (no login-based functionality)

    ⚠️ Issue Description

    The “Submission Options” section continues to show “Incomplete” even after:
    • Selecting:
    • ✔ “Publish this submission as soon as it passes certification”
    • Clicking Save multiple times
    • Refreshing the page
    • Trying different browser sessions

    🔍 Additional Context

    • The app uses runFullTrust capability, and I have already:
    • Provided detailed justification in the restricted capabilities section
    • Confirmed that this is required for:
    • Local AI model execution
    • File system access
    • Bundled executable (GenieUI.exe)
    • Based on Microsoft documentation:
    • runFullTrust is expected for packaged desktop apps
    • Restricted capabilities require explanation but should not block submission completion

    ❓ Questions

    1. Can the presence of runFullTrust capability cause the Submission Options section to remain incomplete?
    2. Is there any additional approval step or hidden field required specifically for restricted capabilities?
    3. Could this be a UI/backend issue in Partner Center not reflecting saved state?
    4. Are there any logs or validation details I can check to identify the missing requirement?
MSN Partner Hub | Content rejection
0 comments

Answer accepted by question author

AI answer

2026-04-17T07:13:13.8066667+00:00
  1. The runFullTrust restricted capability itself does not mark the Submission options section as incomplete. Restricted capabilities require justification during the app submission process, but the documentation states that they are handled as part of Store onboarding policy and review, not as a blocking condition for filling out Submission options. The capability is declared in the package manifest and then explained on the Submission options page, but its presence alone is not documented as a cause for that section to remain “Incomplete”.
  2. For restricted capabilities (including runFullTrust), the additional requirement is to:
    • Declare the capability in the app package manifest using the rescap namespace, and
    • Provide information during the app submission process on how the app uses each restricted capability, on the Submission options page.
    The documentation describes this as an approval/onboarding review step for Store submissions, but does not list any extra hidden fields beyond the explanation of how each restricted capability is used.
  3. A UI/backend issue in Partner Center is possible but not covered in the provided documentation. The guidance for resolving submission errors focuses on:
    • Ensuring the package is correctly built and signed (.msixupload/.appxupload for UWP, correct packaging for Desktop Bridge).
    • Avoiding common certification failures (privacy policy, age ratings, accessibility declaration, etc.).
    • Providing required information for restricted capabilities on the Submission options page.
    There is no documented behavior where a correctly completed Submission options page remains “Incomplete” specifically because of runFullTrust. If all required questions and explanations are filled and saved, and the section still shows “Incomplete”, that aligns more with a Partner Center issue than with a documented policy rule.
  4. The available documentation does not expose any Partner Center logs or detailed validation traces for the Submission options page. What is documented instead is:
    • For restricted capabilities, the explanation is entered on the Submission options page as part of the submission process.
    • For general submission issues, the Store will surface error messages during preprocessing or certification (for example, name/identity errors, package format issues, or compilation errors), and those are described in the “Resolve submission errors” articles.
    There is no mention of a separate log view for why Submission options remains incomplete.

Given the documentation:

  • runFullTrust must be declared as a restricted capability in the manifest and explained on the Submission options page.
  • Restricted capabilities are subject to additional Store review, but that review happens as part of certification, not as a precondition for marking Submission options complete.
  • If all visible fields on Submission options are filled (including the explanation for runFullTrust) and saved, and the section still shows “Incomplete”, this is not a documented, expected behavior and likely requires Partner Center support to investigate.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.