Touchscreen gestures on different screen after sleep-awake

Touchscreen (monitor 3, extended desktop from main monitor 1) works correctly after a full startup, or a restart. But, when putting the computer to Sleep, upon awaking the PC, the touchscreen gestures show up on the main monitor 1. Because the gestures are occurring on Monitor 1 (which is not a touchscreen), I am unable to run the Control Panel ... Tablet PC Settings ... Setup program, because when it gets to the touchscreen (monitor 3), when I try to touch to identify it's a touchscreen, the touch gesture is occurring on Monitor 1 (so the prompt does not recognize any input on this monitor). Also, calibration will not work until the touch gestures are being directed to the touchscreen (Monitor 3) rather than the wrong screen. Setup and calibration work fine when the gestures occur on the touchscreen monitor (3).

Again, the monitor works perfectly in all regards, until to put the PC into Sleep mode and awaken it.

I can resolve the issue by unplugging the USB-C cable to the touch monitor (touch signal), which powers down the monitor, then plugging it back in. Or I can resolve it with a Windows 11 PC restart.

I bought another touchscreen from a different seller, slightly different size, and it does the same thing. But I have a much smaller touchscreen that does not exhibit this issue.

Any ideas on what could be the root cause? I found many other threads, but they all focus on running the touchscreen setup. But obviously that is not the solution in my case.

Thanks for guidance ... surely someone else has seen this issue out there.

Kirk

Please, finish filling out your system specs. Include brand and model numbers of all your equipment. Desktop and Monitors.

You may need to make your touch screen your main monitor. Have you tried doing this?

Check Display Settings:

• Go to Settings (you can press Win + I to open it).​
• Click on System.​
• Select Display from the left sidebar.​
• Scroll down to the Multiple displays section.​
• Make sure that the touchscreen monitor (Monitor 3) is set as the main display. If it’s not, click on the drop-down menu and choose the correct monitor.​

Two concerns setting the touchscreen to the main screen.
- Microsoft Flight Simulator main screen is the Samsung Neo G9 ultrawide, changing this to a small touch screen would bring a LOT of complications it would seem
- One of the 3 touch screens I have used, while too small now for my needs, does not have this issue.

Got to be a way to address this without changing the touchscreen to the main screen?

Put in a USB-C switch as a work around when using Sleep mode (cycle power to the touch monitor to correct the problem). Sleep every day because of the historical connector heating issues with RTX-4090 cards ... probably will never be comfortable leaving the PC running all of the time due to these issues, so it's a daily dynamic.

No way can I set the touch screen as the primary monitor, that would be a work-around not a solution.

Appreciate any further ideas on this ... got to be a solution for it.

KRoy7 said:

Touchscreen (monitor 3, extended desktop from main monitor 1) works correctly after a full startup, or a restart. But, when putting the computer to Sleep, upon awaking the PC, the touchscreen gestures show up on the main monitor 1. Because the gestures are occurring on Monitor 1 (which is not a touchscreen), I am unable to run the Control Panel ... Tablet PC Settings ... Setup program, because when it gets to the touchscreen (monitor 3), when I try to touch to identify it's a touchscreen, the touch gesture is occurring on Monitor 1 (so the prompt does not recognize any input on this monitor). Also, calibration will not work until the touch gestures are being directed to the touchscreen (Monitor 3) rather than the wrong screen. Setup and calibration work fine when the gestures occur on the touchscreen monitor (3).

Again, the monitor works perfectly in all regards, until to put the PC into Sleep mode and awaken it.

I can resolve the issue by unplugging the USB-C cable to the touch monitor (touch signal), which powers down the monitor, then plugging it back in. Or I can resolve it with a Windows 11 PC restart.

I bought another touchscreen from a different seller, slightly different size, and it does the same thing. But I have a much smaller touchscreen that does not exhibit this issue.

Any ideas on what could be the root cause? I found many other threads, but they all focus on running the touchscreen setup. But obviously that is not the solution in my case.

Thanks for guidance ... surely someone else has seen this issue out there.

Kirk

Click to expand...

Hey, I ran into this exact same issue with my dual-touchscreen setup and spent a lot of time figuring out what's actually happening under the hood.

Why this occurs:
Windows stores the touch digitizer-to-display mapping in the registry, but after a sleep/wake cycle (or USB reconnect), the system re-enumerates HID devices. If your touch monitors come back online in a
different order than Windows expects — which happens a lot with USB daisy-chains or USB-C docks — Windows silently re-assigns the digitizer to the wrong display. The unplugging/replugging trick works because
it forces a clean re-enumeration that happens to land in the right order that time.

Manual fix (for anyone landing here from search):
Control Panel → Hardware and Sound → Tablet PC Settings → Setup. Press Enter to skip the primary monitor, then tap the correct touchscreen when prompted. Do not proceed to Calibrate afterward — that resets
the mapping again. This works, but it doesn't survive the next sleep cycle.

Automated solution:
Because I was tired of doing this every morning, I built a small open-source Windows tool called TouchMapper that runs as a background service. You configure the correct digitizer-to-display mapping once,
and it automatically reapplies it whenever Windows fires a device-change event (sleep/wake, USB reconnect, dock/undock). No more manual Tablet PC Settings dance.

GitHub: GitHub - Omega-Byte-Kft/TouchMapper: Automatic touch-to-display mapping for Windows

It requires .NET 8 Runtime and admin rights (needed to write the mapping registry keys). There's a WPF configurator to set up the mapping visually, then the service handles everything from there. Free and
open source.

Hope this saves someone the frustration — I wish I'd found something like this when I first hit this problem.