Store Listings page broken — cannot delete/replace screenshots or save any changes (AgentMux, Store ID 9P9QCXNNCRK3)

Question

Store Listings page broken — cannot delete/replace screenshots or save any changes (AgentMux, Store ID 9P9QCXNNCRK3)

Asaf 10

The Store Listings page for AgentMux (Store ID: 9P9QCXNNCRK3, MSIX app) has been broken for several days. I am unable to make any changes to the listing — specifically:

Cannot delete or replace existing screenshots
Cannot save any changes — the save button either does nothing or returns "We are unable to save listing. Please reload the page or try again later"
Issue persists across multiple browsers (Chrome, Edge) and in incognito/private mode
Clearing cache does not help

All listing fields are correctly filled in. The app is live on the Microsoft Store. This is blocking a required update to the store listing.

Request: Please reset or unblock the store listing draft on the backend so I can update the screenshots and save changes.

App: AgentMux

Store ID: 9P9QCXNNCRK3

Publisher: AgentMux

Platform: MSIX desktop app

DMKI 10 Reputation points

2026-07-19T21:57:33.1833333+00:00

Same thing, it's not just your app. Asked support, they failed to resolve anything. In fact, they are pretty useless - only asked me to send them my browser's password cache.
DMKI 10 Reputation points

2026-07-19T22:19:40.91+00:00
Partner Center: "We are unable to save listing. Please reload the page or try again later."

What's happening: when you click Save, the browser sends your listing to Microsoft's server, and the server rejects it with a generic HTTP 400 error. The only thing the server sends back is:

{"message":"BadRequest","correlationId":"<id>"}

There is no explanation of what's wrong - just "BadRequest" and a reference ID.

Because the server gives no detail, the page can only show the generic "unable to save" message, and reloading or retrying never helps.

Why it happens: the rejection is on Microsoft's side, not in your listing. This is confirmed - a fully correct, valid save request is still rejected with the same 400, and even deleting a single screenshot is rejected the same way. So no amount of editing your description, screenshots, or other fields will fix it; the problem is in Microsoft's listing service.

The only useful clue is the correlationId in that 400 response (open DevTools > Network, click the failed request, look at the Response). Microsoft's team can look that ID up on their side to find the real cause. That's the thing to give them - not your saved passwords or browser cache (they actually asked me for it, weird stuff).

Initially I thought the problem is in file ID being 32-bit, but additional tests proved it wrong - deleting screenshots going through different endpoint. I have created another support ticket, but I honestly don't believe they will fix it.
Asaf 10 Reputation points

2026-07-20T04:08:58.7833333+00:00

The problem is the "Start Update" button. You need to click that first to start the update. Once you do that, you can update the screenshots.

Answer recommended by moderator

0 additional answers

Your answer

DMKI 10 Reputation points

2026-07-19T21:57:33.1833333+00:00

Same thing, it's not just your app. Asked support, they failed to resolve anything. In fact, they are pretty useless - only asked me to send them my browser's password cache.
DMKI 10 Reputation points

2026-07-19T22:19:40.91+00:00

Partner Center: "We are unable to save listing. Please reload the page or try again later."

What's happening: when you click Save, the browser sends your listing to Microsoft's server, and the server rejects it with a generic HTTP 400 error. The only thing the server sends back is:

{"message":"BadRequest","correlationId":"<id>"}

There is no explanation of what's wrong - just "BadRequest" and a reference ID.

Because the server gives no detail, the page can only show the generic "unable to save" message, and reloading or retrying never helps.

Why it happens: the rejection is on Microsoft's side, not in your listing. This is confirmed - a fully correct, valid save request is still rejected with the same 400, and even deleting a single screenshot is rejected the same way. So no amount of editing your description, screenshots, or other fields will fix it; the problem is in Microsoft's listing service.

The only useful clue is the correlationId in that 400 response (open DevTools > Network, click the failed request, look at the Response). Microsoft's team can look that ID up on their side to find the real cause. That's the thing to give them - not your saved passwords or browser cache (they actually asked me for it, weird stuff).

Initially I thought the problem is in file ID being 32-bit, but additional tests proved it wrong - deleting screenshots going through different endpoint. I have created another support ticket, but I honestly don't believe they will fix it.
Asaf 10 Reputation points

2026-07-20T04:08:58.7833333+00:00

The problem is the "Start Update" button. You need to click that first to start the update. Once you do that, you can update the screenshots.

Answer 1

Asaf 10

Answer:

You can't edit your Store Listing directly unless you've first clicked "Start Update."

The UI is misleading because it lets you open the Store Listings page, edit the text, replace screenshots, and appears to allow changes. However, if your app isn't already in an Update state, clicking Save will fail without a clear explanation.

The correct workflow is:

Click Start Update.

Once the app enters the Update state, edit your Store Listing (including screenshots).

Save your changes.

Submit the update for review.

Without starting an update first, your Store Listing changes won't be accepted.

DMKI 10 Reputation points

2026-07-20T18:29:05.31+00:00

That worked, thanks!