Hi Shasha Bowers,
The issue stems from a mathematical flaw in the scaling subsystem that miscalculates physical mouse positions into visual screen coordinates across monitors with varying display densities, which is common when pairing a Surface Book or HP ZBook with external screens. Because the display manager process is still actively running and simply calculating spatial logic incorrectly, this bug will not generate an application crash log like an Event ID 1000 in your Event Viewer.
Unfortunately, there is currently no permanent configuration fix available and you will need to wait for an official Microsoft patch to address the coordinate mapping error. You must avoid attempting to force legacy display scaling behaviors through registry modifications at paths like HKEY_CURRENT_USER\Control Panel\Desktop using the Win8DpiScaling or LogPixels keys, as this can severely break your user interface. Your safest and most reliable immediate workaround is to navigate to your Windows System Recovery settings and select the option to go back to the previous version of Windows, which will roll your system back to the last stable build until a corrected update is released.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN