How to increment the version of the package I want to publish in Partner Centre - is there an easy way?

Brian 0 Reputation points
2026-03-30T11:35:33.5066667+00:00

I'm not a coder, I've vibecoded an app (my first - see brioritize.com) and via the Partner Centre I want to publish on the Microsoft Store.

I used PWABuilder to create packages to upload to the Microsoft Store. When going through the draft documentation, i had uploaded packages, but then realised I had not included the most up to date functionality, so I deleted them.

I then re-created the packages in PWABuilder and tried to upload them.

However, the Partner Centre won't accept the packages. It results in the error

Your submission contains a package that has the exact same package full name as another package you provided (either previously published or also uploaded as part of this submission), but with different contents. Each .msix or .appx package that you provide must have a unique full name that is specific to the exact contents. Please remove the duplicate package or increment the version of the package you want to publish so that the full name is unique. Package full name in conflict: BrianParkerWayneKent.Brioritizer1_1.0.1.0_Neutral_

I finally managed to change the product name of one of my packages using MSIX Packaging Tool, however now the system says

Invalid package identity name: BrioritzerSideLoad.Brioritizer1 (expected: BrianParkerWayneKent.Brioritizer)

So it won't let me upload a package with the expected name, and it won't accept the changed name despite stating that that is what it wanted. 

Any help please?

Microsoft Partner Center | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-30T11:35:53.7233333+00:00

    Partner Center requires each uploaded package to have a unique full name. The full name is derived from:

    • Identity Name
    • Publisher
    • Version
    • Architecture

    In this case, the conflict is because the new PWABuilder output has the same Identity (name + publisher + version) as a package that was already uploaded earlier, even if that earlier package was deleted from the draft.

    To resolve this, keep the same Identity name that Partner Center expects, and only change the version number in the manifest before rebuilding the package.

    1. Use the expected identity name

    Partner Center error shows the expected identity name:

    expected: BrianParkerWayneKent.Brioritizer

    So the PWA package must use exactly that Identity Name. Do not change it to BrioritzerSideLoad.Brioritizer1 or anything else.

    In PWABuilder or the manifest editor, set the Package/Identity Name back to BrianParkerWayneKent.Brioritizer.

    2. Increment the package version correctly

    The Store enforces version rules for Windows 10/11 packages:

    • Version format: Major.Minor.Build.Revision (four integers)
    • First part (Major) cannot be 0
    • All parts must be between 0 and 65535
    • For Store packages, the fourth part must be 0 when building (Store may change it later)

    Since 1.0.1.0 already exists for that identity, choose a higher version, for example:

    • 1.0.2.0 or 1.1.0.0 or 2.0.0.0

    Update the Version attribute in the manifest (Package/Identity) to this new value, then rebuild the package in PWABuilder.

    Partner Center will then see a different full name because the version changed, and the upload should succeed.

    3. If a rollback or multiple packages are involved

    The Store always delivers the highest version that a device qualifies for. If multiple packages exist:

    • Higher version wins
    • If versions are equal, architecture ranking is used (x64 > x86 > Arm > neutral)

    So always increment the version for any new build intended to replace a previous one.

    If a bad package was ever published and needs to be rolled back for new customers, the documented pattern is:

    1. Create a new submission, remove the bad package, upload an older package (with lower version) for new acquisitions.
    2. Then fix the issue and upload a new package with a higher version than the bad one so existing customers get updated.

    In this scenario, only step needed is to increment the version above 1.0.1.0 and keep the identity name exactly as Partner Center expects.

    References:

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

    Was this answer helpful?

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.