Fix Blurry Apps on Windows 11 When Switching Between Monitors

Quick fix: Right-click the blurry app’s .exe → Properties → Compatibility → Change high DPI settings → tick Override high DPI scaling behavior → choose System (Enhanced). This re-renders the app for the new monitor instead of bitmap-stretching it.

You drag a window from your 4K laptop screen to a 1080p external monitor and the window goes blurry. Sometimes signing out and back in fixes it for one session. Tomorrow it’s blurry again. The fundamental issue: Windows didn’t tell the app the DPI changed, so the app keeps rendering at the original DPI and Windows stretches the bitmap to fit — producing soft text and blurry icons.

What causes this

Windows supports three levels of DPI awareness for apps. Unaware: the app renders at 96 DPI and Windows stretches its output for higher-DPI displays — produces blur when the destination DPI doesn’t match. System: the app renders at the primary display’s DPI at launch and never updates — produces blur when moved to a different-DPI monitor. Per-Monitor V2 (PMv2): the app responds to DPI changes in real time as you drag it between monitors — produces crisp rendering at all DPIs.

Most modern apps are PMv2-aware (Edge, Chrome, Office, Visual Studio). Older Win32 apps, Java apps, and Electron apps not built with multi-DPI support fall into the Unaware or System categories, and they go blurry on monitor switches.

Method 1: Apply per-app DPI override (most common fix)

Forces Windows to re-render the app cleanly on monitor switches instead of stretching the bitmap.

1. Right-click the app’s shortcut → Open file location. (For pinned Taskbar shortcuts, right-click the icon, then right-click the app name in the popup, then choose Open file location.)
2. Right-click the .exe → Properties → Compatibility.
3. Click Change high DPI settings.
4. Tick Override high DPI scaling behavior. Scaling performed by:.
5. Choose System (Enhanced) for the cleanest text rendering on Win32 apps. (Choose Application if the app handles DPI itself but fights Windows. Choose System for legacy apps with custom controls that break under Enhanced.)
6. Click OK twice. Close the app completely and relaunch from the same shortcut.

Drag the window between monitors. Text should remain crisp on both. If a specific dialog box looks wrong under System (Enhanced), switch to System — same fix for blur, slightly worse text quality but better control rendering.

Method 2: Force re-launch all apps on resolution change

Use when you have many apps to fix or want a fleet solution.

1. Open Settings → System → Display → Advanced display.
2. Note the connected monitors and their refresh rates.
3. For each monitor, set Scale on the main Display page so that scaling × resolution is approximately equal across monitors. Example: laptop 4K at 200% = effective 1080p; external 1080p at 100% = 1080p. Effective DPI matches.
4. This sidesteps the DPI-change event entirely because Windows treats both monitors as the same effective DPI.
5. Sign out and back in for all apps to pick up the new effective DPI.

Trade-off: you lose pixel density (text on the 4K screen is less crisp than at native 200%), but no app goes blurry on monitor switch.

Method 3: Replace with PMv2-aware apps where possible

The cleanest long-term fix for chronic blurry apps.

1. Identify which app is blurry. Common offenders: older versions of Notepad++, classic Notepad, some Java IDEs, some VPN clients, older AutoHotkey scripts.
2. Check if the vendor offers a newer version with PMv2 support — most have shipped updates since 2020.
3. For Notepad++, update to v8.x (added PMv2). For Notepad, use the Windows 11 modernized version instead of the legacy one.
4. For Java apps, install the latest Adoptium OpenJDK (Java 17+) which handles HiDPI well. Older Java 8 apps stay blurry.
5. For Electron-based apps (Slack, Discord), update to latest — most Electron versions since 2021 support PMv2.
6. Check current DPI awareness via Task Manager → Details tab → right-click columns → Select columns → DPI awareness. Apps showing Per monitor (V2) handle multi-DPI correctly; System or Unaware go blurry.

This is the right path when you can switch to a newer app version — the underlying issue is fixed at the source rather than papered over with override flags.

How to verify the fix worked

• Drag the app window from your highest-DPI monitor to your lowest-DPI monitor (e.g., laptop 4K to external 1080p). Text should remain readable and crisp during the move.
• Open Task Manager → Details tab. Right-click columns header → Select columns → tick DPI awareness. The app should now show System or Per monitor (V2), not Unaware.
• Resize the window. Text should remain crisp through the resize — no pixelation jumps.

If none of these work

If app stays blurry despite the override and even after replacing with a newer version, the app probably embeds a non-DPI-aware library (like an older OpenGL or Direct2D rendering pipeline) that the host can’t override. Try running the app with explicit DPI awareness via command line: start /D "C:\path\to\app" app.exe --force-device-scale-factor=1 works for Electron apps. For Java apps, set environment variable JAVA_TOOL_OPTIONS to -Dsun.java2d.uiScale=2 before launching. For everything else, the practical workaround is to keep the app on whichever monitor matches its native DPI — pin it to that monitor with PowerToys FancyZones so it never gets dragged into the blurry-side situation.

Bottom line: Blurry apps on monitor switches come from old DPI-handling code — per-app overrides catch most, matching effective DPI catches the rest, and updating to PMv2-aware versions fixes it at the source.