Open-ShellSoftware & guidesClassic menus. Practical Windows guidance.

Open-Shell guide

Check Open-Shell on multiple monitors

Multi-monitor behavior should be tested per display, especially when resolutions or scaling differ. Start-button placement, menu sizing, and Windows taskbar.

Direct answer

Multi-monitor behavior should be tested per display, especially when resolutions or scaling differ. Start-button placement, menu sizing, and Windows taskbar settings interact. A working primary monitor does not establish that a secondary display is configured correctly.

What to do

  1. List each monitor resolution, scale, and whether Windows treats it as primary. Note any taskbar replacement or docking utility that is also active.
  2. Test Open-Shell on the primary display with a supplied button and skin. Establish a baseline before introducing custom resources.
  3. Activate Start on the other displays where the Windows taskbar exposes it. Compare the opening position, click target, and label scaling.
  4. Temporarily test without overlapping shell customizers. Restore your normal setup afterward and record which combination reproduces the difference.

Check the result

Check both fixed desktop use and reconnection of a dock or external display. Verify that the menu remains reachable when the monitor arrangement changes.

Limits & precautions

This guide does not promise an identical taskbar or menu on every Windows release. Report the actual display arrangement and reproduction steps instead of a general “multiple monitors broken” description.

Questions & answers

Why does a custom button look fine on only one screen?

Mixed display scaling may expose an asset or size-setting problem.

Should I test the built-in skin first?

Yes. It removes a custom resource from the list of possible causes.

Sources & scope

Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.