What does HRESULT 0x80270250 (E_MONITOR_RESOLUTION_TOO_LOW) mean?

 
Previous Next
FA_E_HOMEGROUP_NOT_AVAILABLE E_ELEVATED_ACTIVATION_NOT_SUPPORTED

E_MONITOR_RESOLUTION_TOO_LOW

The activation environment does not meet the display prerequisite

E_MONITOR_RESOLUTION_TOO_LOW is HRESULT 0x80270250 (signed decimal -2144927152, unsigned decimal 2150040144). AllStat, using winerror.h, records: “This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again.” The value has failure severity, facility 39 (FACILITY_SHELL), and code field 0x0250.

What Windows checked

This result belongs to the shell activation path for packaged Windows applications. Microsoft’s Windows App Certification Kit documentation states that IApplicationActivationManager::ActivateApplication requires an effective screen size of at least 1024 × 768 or 768 × 1024. The relevant value is the display mode visible to the interactive session where activation occurs. It is not the physical panel’s advertised maximum resolution and it is not the size of the application window.

The HRESULT therefore identifies a platform prerequisite failure before normal app startup. It does not show that the executable crashed, that package registration is damaged, or that the application rejected a particular document or URI.

Situations that produce this result

  • A virtual machine or test image starts with a low default display mode before guest display integration is installed.
  • A remote, nested, or automated session exposes a smaller effective desktop than the console session.
  • Display configuration falls back to a basic mode after a graphics-driver problem, monitor change, or recovery boot.
  • A certification or launch harness runs while the desktop is configured below the documented minimum.
  • Resolution is sufficient on another monitor, but the activation request is sent in a session whose current display topology does not expose it.

Evidence to record

  • OS version, session ID, interactive user, console-versus-remote status, and the exact activation method.
  • Current width, height, orientation, scaling, and which display is primary for that session.
  • Whether the same AppUserModelID activates after reconnecting to the console or selecting a supported mode.
  • Recent display-driver changes, fallback-driver use, VM guest-tool state, and monitor enumeration events.
  • The Immersive-Shell activation event and the returned HRESULT, without replacing it with a generic “app failed” message.

Diagnostic sequence

  • Measure the effective desktop mode in the failing session instead of reading the monitor specification from inventory.
  • Raise the resolution to at least the documented threshold and repeat the identical activation request.
  • If the mode cannot be raised, verify the display driver, VM integration components, remote-session policy, and monitor topology.
  • Confirm that the application starts under the same user and package registration when the display prerequisite is satisfied.
  • Only after this HRESULT disappears should investigation move to package registration, executable startup, or application code.

Retry and recovery

An unchanged retry under the same display mode is deterministic and should not be looped. Retry becomes meaningful after the session exposes a supported resolution. A service or remote administration tool should report the session/display prerequisite to the operator rather than attempting to launch the interactive app repeatedly.

Do not confuse it with application layout limits

The code is not a statement that one page, image, or control cannot fit in the app window. It is also different from a DirectX failure to create a swap chain. The shell declined activation because the environment was below its activation threshold; application UI code may not have executed at all.

Practical example

A clean virtual machine boots at 800 × 600 and an automation harness calls ActivateApplication. Windows returns E_MONITOR_RESOLUTION_TOO_LOW. Installing the guest display driver and setting the session to 1280 × 800 resolves the prerequisite. Repackaging or resetting the application would not address the cause.

Official Microsoft references

Looking for a different code? Search another status or error code.