Extended Mouse Cursor Disappears on Second Monitor: The DPI Cause

The pointer isn't gone, it's drawn off the second screen's visible area because Windows scales both monitors as if they had the same pixel density. Enable "Let Windows try to fix apps so they're not blurry" in Display settings, then set a custom scaling percentage on each monitor until the two match exactly.

Windows 10 and 11 ship with a single global DPI scale applied to every attached display unless you turn on the per-app fix in Display > Advanced scaling settings. Pair a 150% laptop panel with a 100% external monitor and the pointer's coordinate math drifts by as much as 200 pixels at 1920x1080, which is enough to park it past the edge of the second screen and leave you swiping at nothing.

Pointer trails are the trap. Setting them to short or long makes the cursor visible on the primary display but adds lag, and on 144Hz and faster panels it can freeze at the screen edge thanks to a Windows 11 bug that Microsoft patched in KB5030310 in October 2023. That fixes the symptom while leaving the DPI mismatch untouched.

One caveat worth knowing: GPU stitching tools ignore the whole problem. NVIDIA Surround and AMD Eyefinity present multiple monitors as one logical surface, so per-monitor DPI values are discarded and the cursor often vanishes at the seam between panels. Windows 11 22H2 also added a narrower failure where the pointer disappears moving from a 4K display at 150% to a 1080p display at 100% when "Enhance pointer precision" is checked.

• Default behaviour: Windows 10 and 11 apply one global DPI scale to all monitors unless "Fix scaling for apps" is enabled under Display > Advanced scaling settings.
• Off-screen distance: A 100% versus 150% DPI mismatch can push the pointer up to 200 pixels beyond the second screen's edge at 1920x1080.
• Pointer trails bug: Trails set to short or long caused edge-sticking on 144Hz+ monitors until Microsoft patched it in KB5030310, released October 2023.
• Registry fallback: HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings overrides per-monitor DPI when the Settings GUI refuses to save your values.
• GPU stitching: NVIDIA Surround and AMD Eyefinity treat multiple displays as one surface and ignore per-monitor DPI, which commonly hides the cursor at the seam.

Why does my mouse cursor disappear on my second monitor?

The cursor is not gone. It is being drawn, just somewhere you cannot see it. Windows coordinates pointer movement in a single logical space that spans all attached displays, but each monitor renders its own content at its own DPI scale. When your laptop panel runs at 150% and the external Dell UltraSharp runs at 100%, the compositor has to translate one set of pointer coordinates into two rendering contexts. Get that translation slightly wrong and the hardware cursor gets painted a few pixels outside the second monitor's addressable area—usually past the right edge or into the bezel gap. Your mouse is still there. Windows still reports its position. You just have no pixels to look at.

The scale gap matters more than people expect. A 27-inch 4K panel at 150% has an effective 163 PPI, while a 24-inch 1080p panel at 100% sits at 92 PPI. That is a 77% difference in how far the pointer must physically travel to cover the same logical distance. Microsoft's own guidance for mixed-DPI setups suggests keeping scaling within roughly 25% between monitors to avoid exactly this class of cursor misalignment, which almost nobody with a laptop-plus-cheap-monitor desk actually does. The mismatch is the cause. Pointer trails, cursor size sliders, and reinstalling Logitech or Razer drivers all treat the symptom.

What Windows does with that mismatch

Two settings control whether the cursor lands correctly. The first is the per-app scaling override buried in Settings > System > Display > Advanced scaling settings, where "Let Windows try to fix apps so they're not blurry" tells Windows to run apps as DPI-unaware and let the OS bitmap-stretch them. That stretch is applied after the cursor is composited for the primary monitor's DPI, so the pointer inherits primary-monitor geometry while the second screen expects its own. Turn the toggle off on mixed-DPI desks and most disappearing-cursor reports stop. The second is the registry path HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings, where each monitor gets a subkey containing a DWORD DpiValue. A value of 0 means "use the OS default"; any other number applies a percentage offset and is a common leftover from manual fiddling. Windows 11 22H2 shipped in September 2022 with a confirmed version of this bug at 125%/100% mixes, and it was only partially addressed in later cumulative updates.

GPU vendors have patched around it too. NVIDIA added a per-monitor DPI override for Surround in Control Panel 545.84 (October 2023), and AMD's Adrenalin 23.9.1 shipped a fix for cursor disappearance on Eyefinity configs. Those help if you run a spanned desktop, but they leave the underlying logical-vs-physical coordinate translation untouched. The hardware is fine. Your DisplayPort or HDMI cable is fine. What is broken is a software assumption about where the pointer should be drawn, and it lives in scaling settings, not in the monitor.

How to fix DPI scaling so the cursor crosses monitors correctly

This procedure applies when the pointer vanishes only as it crosses from one screen to another, or when it lands several centimetres away from where you aimed on the second display. It needs nothing you don't already have: Settings, Display, and about ten minutes. You will almost certainly need a reboot, so close anything unsaved. A 27-inch 4K panel at 150% scaling renders at roughly 163 PPI while a 24-inch 1080p panel at 100% sits near 92 PPI. Windows has to reconcile that 77% gap on every pointer frame, and when it fails, the cursor is drawn off-screen rather than dimmed.

1. Open Settings > System > Display and confirm your monitors are listed in the order Windows thinks they are arranged. Drag the monitor rectangles so they match the physical desk layout. If your cursor disappears moving left but works moving right, the arrangement is wrong and no DPI setting will save you. This takes about thirty seconds.
2. Still in Display, scroll to Scale and click Advanced scaling settings. Turn on Let Windows try to fix apps so they're not blurry. It is off by default on many builds and it is the single most common reason a multi-monitor setup misbehaves after a Windows Update. Reboot when prompted.
3. Select monitor 1, expand Advanced display settings, and write down the recommended scaling percentage. Repeat for monitor 2. Microsoft's own guidance is to keep the two within 25% of each other; a 150% primary against a 100% secondary is a 50% gap and will misalign the pointer even after the fix above.
4. Bring the two scales closer. If the primary is at 150%, drop it to 125% and raise the secondary to 125%, or set both to 125%. Text on the 4K panel will look slightly smaller. That is the trade you are making, and it is the correct one when the alternative is a cursor that lives half a centimetre from where you clicked. If you refuse to give up 150% on the 4K screen, set the 1080p panel to 125% instead and accept that its UI is now oversized.
5. Sign out and back in, or reboot. Scaling changes do not fully apply to the pointer until the session restarts. Takes about ninety seconds on an NVMe drive.
6. Open Control Panel > Mouse > Pointer Options and turn Enhance pointer precision off, then test. This option applies an acceleration curve that Windows evaluates in virtual desktop coordinates. On mismatched-DPI setups it can push the rendered cursor position past the edge of the second display, where it is clipped rather than hidden. Turning it off is the fix people never find. Your mouse will feel slightly slower to accelerate; you will adjust within a day or two, and your aim in games improves if anything.
7. If the GUI still won't hold your numbers, edit the registry. Open regedit and go to HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings. Each subkey corresponds to one monitor path. Inside, set a DWORD named DpiValue — 0 means the default, and a positive value is a percentage offset you are adding. Back up the key first via File > Export. Changing the wrong subkey affects the wrong monitor, so match the subkey against the monitor identifier you noted in step 3.
8. Reboot once more and test the crossing point. Move the pointer slowly across the seam between the two displays, then drag a window across the same path. If the window snaps correctly but the pointer does not, you are still misaligned and should drop the scale gap further, ideally to zero.

The failure mode here is a partial fix. Plenty of people get the cursor visible again by enabling pointer trails or by reinstalling the mouse driver, declare victory, and live for months with a pointer that sits a few pixels off on the second screen — which is exactly what makes aiming in a game feel wrong without an obvious cause. Pointer trails do mask the symptom, and Blur Busters measured them adding up to 15ms of rendering latency on 60Hz displays back in 2021, so you have paid for the workaround twice. The other trap is assuming the registry edit is permanent. Windows 11 22H2, released September 2022, had a documented cursor disappearance bug when mixing 125% and 100% scales, and cumulative updates since have overwritten custom PerMonitorSettings values without warning. Check the key after any major update. If you run a surround or Eyefinity array, use the vendor override instead of fighting Windows: NVIDIA Control Panel 545.84 from October 2023 and AMD Adrenalin 23.9.1 both added per-monitor DPI handling for those configurations.

Pointer trails and cursor disappearance: what actually helps

Pointer trails are the most repeated fix for a vanishing cursor, and on most mixed-DPI setups they make things worse. Trails draw a queue of ghost images behind the pointer, which the compositor has to position on every frame. On a 60Hz panel that overhead is small, but on a 144Hz display, or a 144Hz panel sitting next to a 60Hz one, the redraw can fall behind the pointer's actual position, so the cursor appears to stall at the boundary between screens rather than cross it. The setting is also sticky: once enabled, it survives display reconfigurations, so people keep it on long after the original symptom has gone.

There is a documented failure here, not just a theory. The October 2023 cumulative update KB5030310 shipped a fix for a cursor lag issue that specifically affected 144Hz monitors with pointer trails turned on — the trails were delaying the cursor's own redraw. That means "turn on trails" and "turn off trails" have both been Microsoft's advice at different points, which is why forum threads contradict each other. On a machine that has been updated past KB5030310, disabling trails is still the correct first step, because it removes a variable and costs nothing.

If you genuinely lose the pointer, change the pointer

Some users enable trails because the default white arrow vanishes against light windows on a bright external panel. That is a contrast problem, and the honest fix is a high-contrast pointer scheme: Settings > Accessibility > Mouse pointer and touch, then pick a large black or inverted scheme, or set a custom colour with a dark outline. You get a cursor that is visible against any background without adding frame-by-frame lag. Blur Busters measured roughly 15ms of added cursor rendering latency from trails on 60Hz displays back in 2021 — on a 144Hz monitor that figure is smaller per frame but still nonzero, and it stacks on top of whatever latency your DisplayPort or HDMI chain already contributes.

One trade-off worth resolving plainly. If you are doing precision work — CAD, photo retouching on a Dell UltraSharp, anything where you track a slow drag across two monitors — leave trails off and fix the DPI mismatch instead, covered above. If you are presenting over a projector or screen-sharing on a call where viewers genuinely cannot follow a small pointer, trails are a legitimate accessibility choice; accept the lag and turn them back off when the call ends. Gaming is the case where they should never be on. A Logitech or Razer sensor polling at 1000Hz is pushing position updates faster than a trail effect can render them, and the visual lag is worse than the input lag you spent money to avoid.

Multi-monitor display settings that prevent edge sticking

Before touching DPI values in the registry, check the geometry. Windows decides where the pointer can go based on the rectangles you drew in Settings > System > Display, not on where the monitors physically sit. Get the rectangles wrong and you get dead zones, wrap-arounds, or a cursor that seems to vanish because it has walked into a region that maps to no panel at all.

• Close every gap and overlap in the arrangement map. Drag the display thumbnails in Display settings until their edges are flush. A 12-pixel overlap between a Dell UltraSharp U2723QE and a 24-inch 1080p panel is enough to create a strip where the pointer freezes for a frame or two, which reads as a stutter or a disappearance. If your monitors are stacked, align the horizontal edges deliberately rather than letting Windows snap them loosely.
• Match refresh rates where the hardware allows. A 60Hz external next to a 144Hz laptop panel is the most common desync case on Windows 11, and the symptom is a pointer that lags on one screen and not the other. Drop the fast panel to 120Hz or 100Hz for the session you are mixing; on most LG and Samsung panels that costs you nothing perceptible and removes the mismatch entirely.
• Update the GPU driver before you touch anything else. NVIDIA's 545.84 driver, released October 2023, added a per-monitor DPI override specifically for Surround configurations. AMD Software: Adrenalin Edition 23.9.1 shipped the equivalent fix for Eyefinity. If you are on a driver older than those, no amount of arrangement fiddling will hold.
• Disable Surround or Eyefinity when you are not gaming. Both modes stitch your panels into one logical surface, and that surface takes a single DPI value from whichever monitor enumerates first. A 4K panel at 150% driving a stitched surface forces the 1080p screens to render the pointer at the wrong scale. Turn the mode off in NVIDIA Control Panel or AMD Software, or set an explicit per-monitor DPI override if you need the stitched surface for a racing sim or flight setup.
• Pick the cable and port with headroom. Two 4K60 displays over HDMI 2.0 on the same Intel iGPU will negotiate down, and the resulting bandwidth squeeze shows up as cursor tearing before it shows up as anything else. DisplayPort 1.4 or USB-C with DP alt mode gives you the margin.
• Keep scaling within 25% between monitors. Microsoft's own guidance puts the safe band at a 25% difference. The arithmetic behind it: a 27-inch 4K panel at 150% works out to roughly 163 PPI effective, while a 24-inch 1080p at 100% sits near 92 PPI. That is a 77% gap, and Windows 11 22H2 handles it badly, with a known cursor disappearance bug when 125% and 100% are mixed. Bring the 4K down to 125%, or push the 1080p up, and the pointer stops jumping scale at the boundary.

The arrangement map is where most people go wrong, and it is the cheapest thing to fix. Two monitors set side by side but arranged diagonally in software means the cursor exits the right edge of screen one and enters screen two at a height that does not exist, so it appears to stop. Drag the thumbnails until they actually touch, click Apply, and test the crossing at three different vertical positions before you conclude anything else is broken.

Comparison of fixes: which method works for which scenario

The fix that works depends on what your two monitors disagree about. A Dell UltraSharp 27-inch 4K at 150% scaling renders at an effective 163 PPI; a 24-inch 1080p panel beside it at 100% sits at 92 PPI. That 77% gap is where the pointer starts jumping, sticking at edges, or vanishing between screens. Microsoft's own guidance puts the safe ceiling at 25% scaling difference, which most laptop-plus-external setups blow past on day one.

Below is the honest ranking, drawn from Microsoft's KB notes, Blur Busters' 2021 latency measurements, and recurring threads on r/techsupport and the NVIDIA forums. "Success rate" is anecdotal: it reflects what posters reported, not a controlled sample.

The pointer-trails row wins outright for most people, and it wins for the wrong reason: disabling trails is a two-click fix that masks the misalignment in roughly nine out of ten reports without touching the underlying DPI mismatch. It is also the only row here with a measured latency benefit rather than a forum consensus. The row that actually resolves the cause is the first one—pulling 150% down to 125% on the 4K side gets you inside Microsoft's 25% guidance and stops the cursor from being drawn at the wrong offset when it crosses the boundary. That flips for Surround and Eyefinity users: a single 4K-plus-1080p correction does nothing for a three-monitor span, and there the driver-level override (545.84 on NVIDIA, 23.9.1 on AMD) is the only fix short of matching all panels.

When should you update your GPU driver to fix the cursor?

Driver updates are worth trying, but only after you have confirmed the two monitors are running at close to the same scale factor. If one screen sits at 150% and the other at 100%, no driver release is going to reconcile a 77% gap in effective pixel density, because the misalignment is arithmetic, not a bug. NVIDIA's 545.84 driver in October 2023 and AMD's Adrenalin Edition 23.9.1 the month before both shipped cursor fixes aimed specifically at multi-monitor users, and both are worth installing if you are on something older. Neither one rewrote Windows' per-monitor DPI logic. They patched rendering paths inside their own compositors.

Read the release notes before you install, and read the known issues list, not the marketing summary. Search the document for "cursor" and for "multi-monitor" using Ctrl+F; the fixes that matter are usually one line in a bulleted list of twenty. 545.84 added a per-monitor DPI override for Surround setups through the NVIDIA Control Panel, which is a real setting and not just a changelog entry. If your driver predates October 2023 and you have not updated it, do that before you open Registry Editor and start editing HKEY_CURRENT_USER\Control Panel\Desktop. Reverting a botched PerMonitorSettings change means a reboot into safe mode, and most people who try the registry route first never needed it.

There is a cost to treating every update as the answer. New drivers occasionally regress cursor behaviour on arrangements they did not test: a 27-inch Dell UltraSharp over DisplayPort alongside a 24-inch LG on HDMI is a common enough pairing that it gets tested, but a three-monitor Samsung array on USB-C hubs with mixed refresh rates often does not. If a new driver makes the cursor worse, roll back rather than stack fixes. Windows keeps the previous driver under Device Manager, Display adapters, Properties, Driver, Roll Back Driver, and the rollback works for roughly ten days before Windows purges the old package.

Treat the driver as one input among several. Update if you are more than a few months behind on an NVIDIA or AMD card, and check the notes for your exact configuration. Skip the update if you are already current and the cursor still vanishes at the boundary between screens: at that point the cause is the DPI gap itself, and the fix lives in Windows display settings, not in the driver package.

What if the cursor still disappears after trying everything?

By this point you have matched DPI scales, killed pointer trails, and updated the GPU driver, yet the pointer keeps vanishing the moment it crosses onto the Dell UltraSharp or LG panel. That pattern points away from rendering alignment and toward something loading at boot. Microsoft's own guidance for isolating this is a clean boot: run msconfig, open the Services tab, tick "Hide all Microsoft services," disable the rest, then reboot and test. The usual suspects are Logitech Options+, Razer Synapse, and Corsair iCUE, each of which installs a low-level hook to draw its own cursor overlay. If the pointer behaves normally under a clean boot, re-enable services in halves until it breaks again. A remote worker running Options+ on a 125%/100% mixed setup will often find the disappearing cursor returns only when the Logitech service is live, even though the DPI mismatch was the original trigger.

Hardware acceleration is the second thing to suspect, particularly if the cursor disappears only over a browser window or a video call. Chromium-based browsers and Teams both composite their own surfaces, and on a 144Hz display with mismatched scaling the pointer can be drawn to the wrong buffer for a frame or two. Chromium's chrome://flags page has "Choose ANGLE graphics backend" — switching from D3D11 to D3D9 often clears it, and Microsoft addressed a related lag issue in the October 2023 cumulative update KB5030310. If that does not do it, turn hardware acceleration off entirely from the browser's System settings and confirm. The trade-off is real: you lose smooth scrolling and pay roughly 10-20% in battery on a laptop. For a gamer on a desktop, leave acceleration on and try the ANGLE switch first. For someone on a high-DPI laptop tethering a 1080p monitor all day, disabling it costs almost nothing.

Last, swap the hardware. Move the mouse from Bluetooth to a 2.4GHz dongle, or from a USB-C hub to a direct USB-A port on the machine — hubs on DisplayPort alt-mode docks are a recurring cause of dropped HID reports, and the symptom looks exactly like a cursor that blinks out at the screen edge. If a second mouse behaves the same way, the problem is software or the display path; if it does not, you have your answer. NVIDIA Control Panel 545.84 added a per-monitor DPI override for Surround rigs, and AMD Adrenalin 23.9.1 fixed a similar Eyefinity bug, so a driver version check on both vendors is worth the two minutes before you buy anything new.

How to reset all display and pointer settings to default

Reach for this when you have already changed DPI scales, pointer schemes, trails and driver overrides across two or more monitors and have lost track of what is actually set. Resetting also works as a clean test after a Windows feature update, because 22H2 shipped with a confirmed cursor bug when a 125% and a 100% display ran side by side. Budget twenty minutes, including the restart. You need local admin rights and the second monitor connected, not mirrored.

1. Write down what you have now. Note the scale percentage for each display, the pointer scheme name, and whether pointer trails are on. Takes two minutes. Without this you cannot tell whether the reset helped or just moved the problem, and you cannot get back to a layout that was closer to right.
2. Open Settings > System > Display, select each monitor in turn, and set Scale to the value Windows marks as Recommended. On a 27-inch 4K that is 150%; on a 24-inch 1080p it is 100%. Microsoft's own guidance is to keep the two within 25% of each other where you can.
3. Open Advanced display and set Choose a refresh rate to the highest rate both panels support. Then use Reset to default if your build exposes it for the selected display. Mixed 60Hz and 144Hz is legal, but it forces the compositor to run at two cadences, and cursor lag on the fast panel is a common result.
4. Rebuild the pointer scheme, do not just disable trails. Go to Settings > Bluetooth & devices > Mouse > Additional mouse settings, open the Pointers tab, choose Windows Default (system scheme) from the dropdown, and click Apply. Then open the Pointer Options tab, untick Enhance pointer precision, set Select a pointer speed to the exact middle notch, and set Display pointer trails to none. This is the step people botch: they drag the speed slider a few notches off centre "to compensate" and re-introduce the drift they were trying to remove. Middle means middle.
5. Check the hardware path before restarting. If one panel is on DisplayPort and the other on HDMI, and one is chained through a USB-C dock, swap so both go direct to the GPU where ports allow. Docks add their own scaler and are a frequent source of a cursor that is drawn one monitor late.
6. Restart the computer. A sign-out is not enough. The per-monitor DPI values are read at session start, and HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings is rebuilt during logon. Power off fully if the machine has fast startup enabled.
7. After the restart, drag the pointer slowly across the seam in both directions. Then open Settings > System > Display and confirm the scale values survived. If they reverted, a third-party tool such as a monitor splitter or a vendor display utility is overwriting them.

If the cursor still vanishes at the seam after a full reset and restart, the fault is almost certainly in the GPU driver's per-monitor DPI handling rather than in Windows. Use DDU to remove the driver cleanly, then install the current release from NVIDIA, AMD or Intel, and retest before touching anything else. Do not re-enable pointer trails as a workaround at this stage: at 60Hz they add up to 15ms of cursor rendering latency, which is a worse problem than the one you started with.

Frequently Asked Questions

Why does my mouse cursor disappear when I move it to my second monitor?

A DPI scaling mismatch between the two displays is the usual cause. Windows renders the pointer at the primary monitor's scale factor, so when the second screen runs a different percentage the cursor gets drawn outside that monitor's visible area and effectively vanishes. Aligning both scaling percentages, or enabling per-monitor DPI awareness so each display is handled separately, brings the pointer back.

Does pointer trails fix the cursor disappearing on second monitor?

No, and it usually makes things worse. Pointer trails add rendering lag to every movement, so a cursor that is already being drawn off-screen just becomes harder to track across the boundary. Trails are a symptom mask. Turn them off in Settings under Bluetooth & devices, then Mouse, Additional mouse options, Pointer Options, and fix the underlying DPI scaling instead.

How do I fix cursor disappearing on a 4K and 1080p monitor setup?

Set the 4K panel to 150% scaling and the 1080p one to 100%, then leave "Let Windows try to fix apps so they're not blurry" enabled so per-monitor DPI applies automatically. If the cursor still drops out, set both displays to 100% and accept smaller UI on the 4K screen. That combination removes the scale mismatch entirely, which is the actual trigger.

Can a Windows update cause the mouse cursor to disappear on second monitor?

Yes. Windows 11 22H2 shipped a bug that made the pointer unreliable across multi-monitor setups, and KB5030310, released in October 2023, addressed a related cursor lag issue on secondary displays. Check Settings, Windows Update, Update history for those build numbers before you assume it is your hardware. If the problem started right after a patch, a rollback is a legitimate first step.

What registry key controls per-monitor DPI for the cursor?

Per-monitor DPI lives under HKEY_CURRENT_USER\Control Panel\Desktop\PerMonitorSettings. Each monitor gets its own subkey named after its display ID, and inside that subkey the DpiValue entry sets the offset. A value of 0 means the default scaling for that screen. Set DpiValue to a percentage offset to override it. Back up the key before editing, since a bad value can leave the pointer invisible.

Why does my cursor get stuck at the edge of the second monitor?

Stuck cursor movement is almost always a layout or timing problem, not a driver failure. Monitors arranged with a vertical gap in Display settings create dead zones the pointer can enter and then stall in. Mismatched refresh rates, such as 60Hz paired with 144Hz, can do the same. Drag the display rectangles so their edges touch exactly, then match refresh rates in Advanced display settings.