XENOSENTINELBY BESTON PROGRAMMINGSystem status
Explore
Ship map
XSS // INTERNAL NAVIGATION ARRAY YOU ARE HERE: XenoSentinel
CURRENT COMPARTMENTSELECT ANY DECK TO NAVIGATE
FLIGHT RECORDER // WINDOWS STORE

From working PC app
to bureaucratic orbit.

This is the actual launch path for XenoSentinel Network Mapper—not a generic how-to. Every gate below came from the build records, forms, uploads, account checks, certification report, and corrective resubmission.

Enter the gauntlet ↓View the actual product
RECORDED AUGUST 26–28, 2026

This is a transparent project log, not a claim that every developer will hit every detour. Microsoft can also change the route after this page is published.

01 / THE ACTUAL ROUTE

Nine gates between “it works” and “people can install it.”

Open each paperwork manifest if the summary does not look sufficiently ridiculous.

GATE 01ENGINEERING PASSED

Build an application worth submitting

Before Microsoft saw a single form, the desktop application needed a real security model, a bounded network engine, persistent client engagements, evidence exports, and a secure local report browser.

  1. Implement authorization gates, exact scope, cancellation, local evidence, case files, and entitlement enforcement.
  2. Build and exercise the Windows x64 installer on an actual Windows 11 machine.
  3. Verify signed upgrade, preserved workspaces, localhost mapping, reporting, restart persistence, and uninstall readiness.
  4. Finish with 33 automated checks before the corrected Store package was allowed out of the build folder.
Open paperwork manifest +
No portal forms yetMany local test recordsBuild and release evidence

REALITY CHECKThis was the straightforward part. It involved writing the software.

GATE 02IDENTITY ORBIT

Prove the developer is a real human

The release path crossed Microsoft account, Partner Center, and Azure identity systems before the product could receive a trusted publisher identity.

  1. Sign in with the correct personal business account and keep it separate from an unrelated work account.
  2. Complete multi-factor authentication and government-ID verification.
  3. Create a Microsoft Artifact Signing account, public-trust certificate profile, regional endpoint, and signer role.
  4. Verify the signed installer and application with a Microsoft timestamp and public-trust chain.
Open paperwork manifest +
Developer enrollmentIdentity verificationMFA enrollmentAccount contact profileArtifact Signing accountCertificate profileAzure role assignment

REALITY CHECKOne publisher, several Microsoft identity surfaces, repeated sign-ins, and a support path that could loop back to login.

GATE 03FINANCIAL CLEARANCE

Build the tax and payout plumbing

A paid product needs a seller profile, tax status, payout destination, and bank-beneficiary details before the Store can move money in either direction.

  1. Create the payout and tax profiles tied to the developer account.
  2. Complete the W-9 path and factual citizenship or residency questions.
  3. Enter beneficiary contact details and a bank-matching legal name and address.
  4. Create support@xenosentinel.com for public customer support while keeping private account contacts separate.
Open paperwork manifest +
Tax profileW-9 questionnairePayout profileBank beneficiary contactBank beneficiary locationSeller contact email

REALITY CHECKThe app can be free, but monetization cannot. Paid add-ons stay blocked until the parent app and financial profile are accepted.

GATE 04IDENTITY LOCKED

Reserve the name, then rebuild around Microsoft’s identity

The Store does not accept a normal desktop installer as-is. It assigns product identity values that must be copied exactly into a Store-specific package.

  1. Reserve “XenoSentinel Network Mapper” and receive Store ID 9P9MX1FDCL10.
  2. Bind the package name, publisher certificate name, publisher display name, and application ID exactly as issued.
  3. Create a separate x64 APPX build targeting Windows 10 build 19041 or newer.
  4. Declare full-trust desktop, Internet client, and private-network capabilities required by the mapper.
  5. Add a native StoreContext bridge for licensing and purchase dialogs.
Open paperwork manifest +
Manage app namesProduct identityPackage identity manifestRestricted capability declaration

REALITY CHECKA package can run perfectly on the PC and still be unusable by Partner Center if one identity character is wrong.

GATE 05LISTING COMPLETE

Complete the main product submission

The product page is not one form. It is a stack of separate submissions covering markets, claims, ratings, files, artwork, release behavior, and reviewer instructions.

  1. Choose markets, availability, pricing model, category, support URL, privacy URL, and system requirements.
  2. Accept IARC terms and complete the age-rating questionnaire.
  3. Write short and long descriptions, feature bullets, release notes, and truthful capability boundaries.
  4. Prepare and upload screenshots, logos, and Store artwork in Microsoft’s accepted formats and dimensions.
  5. Select publishing timing and provide any additional testing information.
Open paperwork manifest +
Pricing and availabilityPropertiesAge ratings / IARCPackagesStore listing — English (United States)Submission optionsAdditional testing information

REALITY CHECKFour screenshots had to be uploaded one at a time. A file named “.png” was still rejected until it was re-encoded as a valid PNG.

GATE 06ADD-ONS STAGED

Create the business model—twice

The free Basic edition, 30-day Pro Pass, and permanent Pro unlock required application code plus two independent Partner Center add-on records.

  1. Implement Basic, Pro Pass, and Pro entitlements without deleting or hiding expired customer evidence.
  2. Create xeno.networkmapper.pro.pass30 as a 30-day durable product at $4.99.
  3. Create xeno.networkmapper.pro as a forever durable product at $19.99.
  4. Repeat pricing, properties, inherited rating, English listing, and publication-hold setup for both add-ons.
Open paperwork manifest +
Add-on pricing × 2Add-on properties × 2Inherited age ratings × 2English listings × 2Manual publication holds × 2

REALITY CHECKThe add-ons cannot be fully submitted until the parent application publishes, so even the finished paperwork has to wait in formation.

GATE 070.2.0.0 ACCEPTED

Package, inspect, certify, upload

The Store build passed local gates, Microsoft’s Windows App Certification Kit, and Partner Center package validation before the first certification submission.

  1. Publish the native bridge, compile the renderer, and build the identity-bound x64 APPX.
  2. Inspect the manifest, architecture, minimum Windows version, capabilities, tile dimensions, and SHA-256 hash.
  3. Run Windows App Certification Kit and resolve its first tile-size warning.
  4. Upload the roughly 189 MB APPX, wait for Partner Center analysis, save the package, and complete the final submission review.
Open paperwork manifest +
Store package uploadDevice-family availabilityRestricted capability warningFinal submission review

REALITY CHECKLocal WACK returned PASS. Partner Center also marked the package Validated. Certification still found something neither gate rejected.

GATE 08POLICY 10.1.1.11

Fail certification over two tiny default icons

The first submission failed “On Device Tiles” because Electron Builder silently supplied its atom placeholder for the 44×44 tile and 50×50 Store logo.

  1. Open the certification report and isolate the only failed policy.
  2. Unpack the submitted APPX with MakeAppx instead of trusting the source folder.
  3. Compare every manifest-referenced asset and identify the two placeholder hashes.
  4. Generate branded replacements and add a regression test that rejects those exact defaults forever.
Open paperwork manifest +
Certification reportFailed-policy evidenceCorrective package record

REALITY CHECKThe 150×150 and 310×150 artwork was branded. The rejection came from two icons totaling less than 4 KB.

GATE 09IN CERTIFICATION

Rebuild, revalidate, re-upload, resubmit

Version 0.2.1.0 replaced the rejected package on August 28, 2026 and is now back inside Microsoft’s certification pipeline.

  1. Bump the Store manifest version so Partner Center will accept a replacement.
  2. Pass lint, all 33 automated tests, production build, Store bridge publish, identity preflight, package inspection, and WACK again.
  3. Upload the corrected 189 MB APPX and wait while Partner Center’s analyzer sits at 99%.
  4. Refresh the stalled page, confirm the staged package survived, save the replacement, and resubmit.
Open paperwork manifest +
Replacement package uploadAutomatic old-package removalSave replacementResubmit for certification

REALITY CHECKCurrent state: Microsoft reports “In certification.” Passing the local and upload gates is still not the same as passing the Store.

02 / PAPERWORK MATRIX

The forms behind the forms.

Several rows below open into more rows, and each paid add-on repeats its own product submission.

01Account & identity

Developer enrollment, MFA, ID verification, contact profile

02Money

Tax profile, W-9, payout profile, beneficiary contact and address

03Product identity

Reserved name, Store ID, package identity, publisher, application ID

04Main listing

Pricing, properties, IARC rating, package, listing, options, testing info

05Pro Pass add-on

Pricing, properties, inherited rating, listing, publication hold

06Permanent Pro add-on

Pricing, properties, inherited rating, listing, publication hold

07Certification

Upload validation, report, correction evidence, replacement, resubmission

03 / CURRENT ORBIT

The app is back in certification.

The corrected package is validated, the default Electron tiles are gone, local WACK passes, and Microsoft has the replacement. What remains is Microsoft certification, Store publishing, parent-app availability, paid add-on submission, and real Store-install purchase testing.

Open system status →Read the documentation boundary
Last verified: August 28, 2026 · No victory lap until the Store says published.