Invalid preview when using scaling

[normanr]

I have scaling set to 125% (Settings > System > Display > Scale) and Desktop Icon Backup Manager shows my 1920x1080 resolution as 1536x864 (with pixel density of 1.25), all probably fine, whatever.

When I restore my layout (which works flawlessly), the preview thinks that the icon at the top-right hand side of the monitor (at 1822x2) will move (I assume because it thinks the screen is only 1536 pixels wide). If I reset scaling to 100%, then the icon sits at 1838x2 (and it doesn't think that it'll move when restoring, but obviously everything is smaller than I'd like).

[mapi68]

I definitely hear you on this: I was already aware of this specific preview glitch that occurs when Windows Display Scaling is active.
It’s a classic high-DPI scaling issue where the software struggles to "map" the actual physical pixels to the scaled logical pixels.As you noticed, when you set your scaling to 150% at 4K (or 125% in your current setup), the OS reports a "logical" resolution that is lower than the actual hardware resolution. In your case, 1920 / 1.25 = 1536.
Because the preview window is likely calculating icon positions based on that logical width of 1536, any icon sitting out at 1822 appears to be "off-screen" to the manager, even though it's physically right there on your monitor
When you switch to 2K at 100%, the logical and physical pixels match (1:1 ratio), which is why the preview displays perfectly.Why this happens:Logical vs. Physical: Windows tells the app the screen is 1536 pixels wide to make text readable, but your icons are still technically pinned to the 1920 physical grid.Coordinate Mismatch: The preview engine sees an icon at X-coordinate 1822 and thinks, "Wait, the screen ends at 1536, this icon must be moving!
It’s frustrating because the restore function usually handles the math correctly in the background, but the visual preview hasn't been taught how to translate those coordinates back through the scaling factor yet.If you can live with the preview looking a bit wonky, the good news is that your actual layout remains safe since the "flawless" restore proves the underlying coordinates are being saved correctly!