Have you ever felt that moment of excitement after submitting an app, only to receive a certification failure a few hours later?
I know I have.
Recently, I submitted one of my apps to the Microsoft Store and expected a smooth approval process. The app worked. The package built successfully. Everything seemed ready. Then the certification report came back with an error:
Policy 10.1.1.3 – Inaccurate Representation
 |
| A realistic modern developer workspace with a Windows laptop screen displaying a Microsoft Store app submission dashboard, a certification report showing a warning about inaccurate screenshots |
At first, the message felt a little vague. The app itself was functioning correctly, so what exactly was inaccurate?
After digging deeper, I realized the issue had nothing to do with my code. The problem was hiding in my Store listing images.
If you're facing the same rejection, the good news is that this is one of the easiest Microsoft Store certification errors to fix once you understand what Microsoft is looking for.
What Microsoft Means by "Inaccurate Representation"
Microsoft wants Store listings to accurately represent the app users will actually install on Windows.
That means your screenshots and promotional images must show the real Windows experience.
If your screenshots look like they came from Android, iPhone, macOS, or a mobile browser, reviewers may reject the submission even if the app itself works perfectly.
The goal is simple: users should see exactly what they will get after downloading the app.
That sounds reasonable when you think about it. Nobody wants to install an app expecting one interface and receive something completely different.
Why This Error Happens So Often
I can understand why many developers run into this issue.
Today, many apps are built as:
- PWAs (Progressive Web Apps)
- WebView applications
- Cross-platform apps
- Mobile-first applications
When preparing screenshots, it's easy to grab images from whichever version is already available.
Sometimes that's the mobile version.
Sometimes it's a browser preview.
Sometimes it's a marketing mockup created before the Windows version was finalized.
Unfortunately, Microsoft reviewers examine these images very carefully.
Even small visual clues can trigger the rejection:
- Mobile browser address bars
- Android navigation buttons
- Phone status bars
- Mobile layouts
- Non-Windows device frames
- Screens showing features that are not available in the Windows version
If your screenshots do not clearly represent the actual Windows experience, certification can fail.
The Mistake I See Developers Make
One common mistake is assuming that because the app content is the same, the screenshots are acceptable.
For example, imagine you have:
- An Android version
- A mobile website
- A Windows app
All three versions display the same content.
You might think it doesn't matter which screenshots you upload.
Microsoft disagrees.
The screenshots must represent the Windows version specifically.
The reviewer is not evaluating your content. They are evaluating whether your Store listing accurately represents the product that Windows users will install.
That difference matters.
How I Fixed the Problem
The good news is that I did not need to rebuild the app.
I did not need to delete the submission.
I did not need to start over.
The fix was simply updating the Store listing images.
Step 1: Open Partner Center
Sign in to Microsoft Partner Center and open your application.
From there:
- Open your product
- Click Store Listings in the left menu
This section contains all listing information including descriptions, screenshots, and promotional assets.
Step 2: Select the Correct Language
Microsoft manages Store listings by language.
To update images:
- Click Manage Store Listing Languages
- Select the language you want to edit
- Open the listing
For many developers, this will simply be the English Store listing.
Step 3: Update the Images and Videos Section
Once inside the listing:
- Scroll to Images and Videos
- Click Edit
- Review every screenshot carefully
- Remove anything that resembles a mobile experience
This includes:
- Android screenshots
- iPhone screenshots
- Mobile browser screenshots
- Device mockups
- Screens containing Android navigation controls
- Images that do not match the Windows build
Then upload fresh screenshots captured from the actual Windows version of the app.
Finally, save your changes.
Step 4: Resubmit
After updating the images:
- Return to the submission overview
- Click Submit for Certification
That's it.
No new package.
No rebuilding.
No new app submission.
Just updated screenshots and a resubmission.
What Your Screenshots Should Look Like
When preparing Microsoft Store screenshots, I now follow a simple rule:
If a Windows user installs the app right now, the screenshot should match what they see.
Good screenshots should:
- Show the actual Windows version
- Display the real interface
- Match current app functionality
- Be readable and clear
- Avoid misleading promotional elements
- Stay consistent across all images
If you're publishing a PWA, make sure you capture screenshots from the installed Windows app, not from your mobile browser.
That distinction alone can prevent unnecessary certification failures.
What I Learned From This Experience
As someone who regularly builds websites, browser extensions, apps, calculators, and digital tools, I've learned that publishing is often just as important as building.
Developers tend to focus heavily on coding.
I know I do.
We spend hours fixing bugs, improving performance, and adding features.
Then we rush through screenshots, descriptions, and Store assets because they seem less important.
The reality is that your Store listing is part of the product.
Microsoft reviews it.
Users see it.
And if it doesn't accurately represent the app, it can stop the entire release process.
Practical Tips Before Submitting
Before your next Microsoft Store submission, take five minutes to verify:
✅ Every screenshot was taken from the Windows version
✅ No mobile browser UI appears in screenshots
✅ No Android navigation buttons are visible
✅ Images match the current app interface
✅ Promotional graphics do not misrepresent functionality
✅ The screenshots show real app screens rather than concepts or mockups
A quick review can save days of confusion and resubmission delays.
Final Thoughts
Certification failures are frustrating, especially when your app is ready to ship.
The good news is that Microsoft Store Error 10.1.1.3 is usually not a software problem. In many cases, it's simply a screenshot problem.
Once I understood that Microsoft wanted an accurate representation of the Windows experience, the solution became obvious. I replaced the problematic images, resubmitted the app, and moved forward.
Sometimes the smallest details can hold up an entire release.
And sometimes the fix is much simpler than we expect.
Have you ever had an app rejected for a reason that turned out to be much simpler than you first thought?