Auto-restore window positions after monitor reconnect

What to build

A lightweight Windows system-tray utility that automatically saves and restores multi-monitor window layouts after sleep, wake, lock, display reconnect, and dock/undock events. Built for developers, power users, and remote workers who maintain carefully arranged workspaces across two or more monitors.

Windows has never reliably restored window positions after a display change event, and years of unanswered forum threads prove Microsoft won't fix it soon. A focused, set-and-forget utility that hooks into Windows display events and snaps windows back to saved positions is a clear, shippable product with a proven willingness-to-pay audience.

Demand

Professional developers and remote workers who run multi-monitor setups lose their layouts dozens of times a week due to sleep cycles, docking, or remote sessions — and they're vocal about it. The pain is chronic, unresolved by Windows itself, and adjacent paid tools like DisplayFusion have already proven users will pay for this category.

• Product Hunt — Many DisplaysMeasured demand

  Product Hunt: Many Displays. Zero clicks: windows back after sleep, unlock or replugging — Discussion thread exists, confirming the concept has been floated publicly on Product Hunt as a named product.

• Microsoft Community ForumsUser complaint

  Numerous user threads on Microsoft Community and Reddit report that Windows consistently scrambles window positions after monitors disconnect or the PC wakes from sleep, a longstanding unresolved issue.

• Reddit r/windows and r/sysadminUser complaint

  Recurring posts in Windows-focused subreddits describe frustration with scrambled window layouts after docking/undocking laptops or after remote desktop sessions, indicating an unmet need.

• DisplayFusion / Existing ToolsMarket signal

  Third-party tools like DisplayFusion and Microsoft PowerToys FancyZones have gained significant user bases specifically to address multi-monitor window management limitations in Windows, validating commercial demand for paid solutions in this space.

• Stack Overflow Developer SurveyData

  A large proportion of professional developers use multiple monitors as part of their daily workflow, representing a core demographic that would benefit from automated window position restoration.

Stack

• C# / .NET 8 (Windows API access via P/Invoke)
• Windows Display Change Events (WM_DISPLAYCHANGE, WTS_SESSION_CHANGE)
• SQLite (local layout profile storage)
• NSIS or Inno Setup (Windows installer packaging)
• Paddle or Gumroad (one-time purchase / licensing)
• GitHub Actions (CI/CD and release pipeline)

Solo + AI difficulty

The core hook into Windows display-change events and window position enumeration is well-documented in the Win32 API and manageable with AI assistance in C# — expect 2–4 weeks to a functional MVP. The hard parts are handling edge cases: apps that resist programmatic repositioning (Electron apps, UWP), per-monitor DPI scaling, and reliably fingerprinting monitor configurations when EDIDs change. Polish, installer, and licensing add another 1–2 weeks.

Entry threshold

Buildable in days using Windows API (SetWindowPos, WM_DISPLAYCHANGE) or an existing library like python-win32 or AutoHotkey; no licences required, distribute via Gumroad or a personal site.

Window

3-6 months

Where to find first users

• r/windows, r/sysadmin, and r/PowerToys — post a demo GIF showing the before/after; these communities actively complain about this exact problem
• Product Hunt launch targeting developer and productivity audiences
• Hacker News 'Show HN' post emphasizing the technical approach and the chronic Windows gap
• Direct outreach in developer Discord servers (e.g., Programmatic.ly, developer productivity communities) and Twitter/X devrel circles

Competitors

• DisplayFusion
• Microsoft PowerToys
• WindowGrid
• Actual Window Manager

Counter-signals & risks

• Microsoft may natively resolve multi-monitor window position persistence in a future Windows 11 update, eliminating the need for a third-party utility and undermining the product's long-term viability.

• Existing free or low-cost tools such as Microsoft PowerToys, DisplayFusion, and WindowGrid already partially address this problem, creating significant competition and price pressure that could limit revenue potential.

• The market segment of power users willing to pay for this specific utility may be too small or price-sensitive to generate sustainable standalone revenue, potentially requiring bundling with broader productivity suites.