Skip to content
Certification errors

We could not identify if your app is installing silently

Partner Center shows it under "Silent install check" when it validates an MSI or EXE package, usually next to "Entry in add or remove programs" and "Bundleware check", which both say: "We could not identify the app name and the publisher name that your app has added in the add or remove programs." A certification report can cite the same rule as "10.2.9.2 Security - Package Submissions | Win32 products must install silently."

What it means

The Store installs your MSI or EXE itself, with no one clicking through it. Policy 10.2.9 says starting the install must not show any installer interface, though a User Account Control prompt is allowed. For an MSI the Store runs it with /qn. For an EXE it uses the installer parameters you entered on the Packages page, and if those still open a wizard, the check fails.

The other two checks look for the entry your installer adds to Add or Remove Programs (Installed apps on Windows 11). A Microsoft moderator on Q&A said the app name and publisher there must exactly match the values in Partner Center. If they differ, or the installer writes no entry, the Store can't tell which app it installed.

How to fix it

  1. Run the installer the way the Store does, on a clean PC or VM, and watch for any window. For an MSI:
    msiexec /i YourApp.msi /qn
    For an EXE, use your installer's own silent switch. NSIS takes /S (capital S), Inno Setup takes /VERYSILENT /SUPPRESSMSGBOXES. Put the same switches in Installer parameters on the Packages page.
  2. If anything still appears, like a license page, a "launch now" checkbox or a message box, make the installer skip it in silent mode. The install also has to be standalone. A web installer that downloads files while it runs fails the Store's rules.
  3. Open Settings, Apps, Installed apps after the silent install and check the entry. Its name and publisher must match the app name and publisher display name in Partner Center. In WiX they come from the package Name and Manufacturer, in Inno Setup from AppName and AppPublisher, and in NSIS from the DisplayName and Publisher values you write under the Uninstall registry key.
  4. Make sure the installer doesn't install other software the listing doesn't mention. Microsoft says the installer must not bundle unrelated software.
  5. A Microsoft moderator on Q&A has also blamed a UAC prompt for a failed silent install check, even though the policy allows one. If your installer elevates and you've fixed everything above, try a per-user install that doesn't need elevation, or package the app as an MSIX, which skips these checks. Our MSI vs MSIX guide covers both routes.
  6. Build the installer again at a new versioned URL and update the package URL in Partner Center. Our guide to a failed certification covers resubmitting.

Sending the fixed update with StoreFast

StoreFast can send your next update to Partner Center from a dashboard, CI or a coding agent. There's a free plan, and connecting Partner Center starts 14 days of Plus with no card.

Sources

Facts about Microsoft's tools were checked against these pages on October 30, 2026.