Microsoft Store MSIX Certification Kit
Take a WPF or WinUI 3 app from a clean commit to a certified Store listing without learning each rejection the hard way.
$49
Works with the AI Agents you already use
Microsoft Store MSIX Certification Kit
Example session with this skill installed
Our WinUI 3 app AcmeDesktop failed Store certification with 10.6.3 (allowElevation denied). Fix the submission and get a Store-ready package built from the current commit.
- Read your context and instructions
- Compiled the microsoft store msix
Summary
The denial was the support contact, not the capability: Properties > Support info was set to account-level details and your support page cannot select AcmeDesktop. Fixed the support URL, rewrote both capability fields, rebuilt 1.4.0.0 from a clean tree with round-trip proof, ran WACK on the exact package, and resubmitted. Ledger row added as submitted.
What the report actually said
10.6.3 Capabilities: Your request to use allowElevation has been reviewed and was denied based on the information provided. A valid support contact and/or developer website URL. Please add this information in Partner Center under Properties > Support Info > Use different details for this app.
Nothing else failed; the package showed Validated.
Fixes
| Step | Change | Read back |
|---|---|---|
| Support | Properties > Support info > Use different details for this app; product URL https://acme.example/desktop, support URL https://acme.example/desktop/support (names the product, returns 200) | reopened, both persisted |
| Short field | 496 characters: support URL, the three bounded elevated actions (toggle one eligible scheduled task, sign out one disconnected session, restore a device power profile), confirmation + UAC, protected items rejected, outcomes logged | reopened, identical |
| Notes | Additional Testing Information expanded from 1,900 to 5,840 characters: report reference, support correction, business need, helper mechanism (allow-listed action ids over a process-bound named pipe, state recheck, action record before acting), protection list, reviewer walkthrough with disposable targets, untested items stated | reloaded, identical |
Build evidence
$ pwsh -File scripts/Test-ReleaseMetadata.ps1 -ProjectPath src\AcmeDesktop\AcmeDesktop.csproj -IdentityFile store-identity.json -VersionLiteralFiles src\AcmeDesktop\Pages\AboutPage.xaml
OK: 11 metadata checks passed.
$ pwsh -File scripts/Build-StoreMsix.ps1 -ProjectPath src\AcmeDesktop\AcmeDesktop.csproj -IdentityFile store-identity.json -ManifestTemplate reference\AppxManifest.template.xml -AssetsDirectory store-assets -OutputRoot out
clean tree at 3f9c0a7d; identity AcmeSoftware.AcmeDesktop / CN=... (Partner Center); version 1.4.0.0
pack ok; unpack ok; 212/212 files hash-identical both directions
wrote out\20261029T1412Z\AcmeDesktop_1.4.0.0_x64.msix (sha256 9015fe03...)
$ pwsh -File scripts/Test-StorePackage.ps1 -PackagePath out\...\AcmeDesktop_1.4.0.0_x64.msix -IdentityFile store-identity.json -ExpectedVersion 1.4.0.0 -DevelopmentPublisher 'CN=AcmeDev'
No blocking finding. Review items: runFullTrust (justified), allowElevation (justified), DPI awareness declared.
$ appcert.exe test -appxpackagepath ...msix -reportoutputpath out\wack.xml
OVERALL_RESULT=PASS (13/13 required); optional test 88 Blocked executables: informational, documented in notes
Ledger
| Date (UTC) | Product | Submission | Version | SHA-256 | WACK | State |
|---|---|---|---|---|---|---|
| 2026-10-29 14:31 | 9NXXXXXXXXXX | 1152921505702xxxxxx | 1.4.0.0 | 9015fe03... | PASS 13/13 | submitted (reconsideration) |
Publishing is held until you release it. If the next report cites 10.8.7 (price), the playbook entry for the read-only pricing page applies: resubmit, cancel certification as it starts, then set the base price tier.
Connects securely to your tools. The creator never sees your data.
About this skill
Take a WPF or WinUI 3 app from a clean commit to a certified Store listing without learning each rejection the hard way.
Scripts (PowerShell, no modules):
Test-ReleaseMetadata.ps1: version shape, assembly/file version agreement, Store product id and publisher CN shape, in-repo manifest cross-check, hard-coded version strings in UI files.Build-StoreMsix.ps1: dirty-tree guard, identity validated against your Partner Center file (refuses a development publisher),x.y.z.0version,dotnet publish, manifest render from a template, payload sweep for secrets and machine paths, per-file hashes,makeappx pack, unpack into a second folder, hash comparison both ways,BUILD-RECEIPT.jsonandSHA256SUMS.txt. Unsigned, because the Store signs.Test-StorePackage.ps1: read-only checks of the exact .msix: identity, version, architecture, executable present, hash, forbidden entries, every declared capability listed for justification, DPI-awareness declaration detected.New-StoreAssets.ps1: the full tile and splash set from one logo PNG.Convert-StoreScreenshots.ps1: pixel-exact JPG to PNG, refuses undersized captures.
References: manifest template, Partner Center identity file example, the capability-justification structure (short field under 500 characters, long field in Additional Testing Information), a reconsideration template for a 10.6.3 denial, a certification-notes template, a submission ledger with a strict state vocabulary (submitted, in certification, failed, approved, published), and a failure playbook covering 10.6.3, 10.8.7 pricing (including the read-only pricing page and the resubmit-then-cancel workaround), DPI awareness, identity and version rejections, and the WACK blocked-executables optional test.
Windows only. Needs the Windows SDK and WACK installed. Nothing here is legal advice about Store policies.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
Windows only. Requires Windows SDK and WACK kit. Limited to .NET WPF and WinUI 3 apps. Playbook reflects Partner Center behavior as of 2026.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
Windows only
- Accounts
- Partner Center account
- Software
- .NET SDKWindows SDKWindows App Certification KitPowerShell 7orWindows PowerShell 5.1
The Windows SDK provides makeappx.exe and the kit provides appcert.exe. The Partner Center account needs a reserved product.