Thanks for the details. Though I wasn't able to reproduce the problem. I do not have a screen with "Pixel Refresh". And mere powering-off/disconnecting a screen does not seem to cause any problems.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include a link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Update: during bug reproduction attempts I had launched three instances on WinSCP, but only two of them were hung. Well, that's unusual. Begs to ask the question what made that one session so special? Not a question of fore/background, but rather only thing I can figure is it was connected to remote folder with just 2199 subfolders in it. The other two, they were substantially bigger sessions (all 3 at idle nonetheless), weighing in at 36313 subfolders each.

Here's one way:

1. Have one of these cursed screens with need to do "Pixel Refresh"
   
   
2. Run WinSCP, and leave it running (foreground or background, doesn't matter)
   
   
3. Screen triggers Pixel Refresh on its own periodically, but here's how to trigger it manually. Hit the screen's menu for Pixel Refresh. Settings -> All Settings -> General & Privacy -> Panel Care -> Pixel Refresh -> Start Now.
   
   
4. Process will take ~30 minutes, by the end of which screen is powered off. Power screen back on, and find WinSCP curled up to a small space in its respective upper left window corner, and consuming CPU furiously.
   

Thanks for the details. I'll try to reproduce it.

Right, scaling, it's 200 %

Screen resolution 3840 x 2160

But it was already doing that with earlier screen, 1920 x 1080 at 100 % scaling.

A desktop computer with single screen which is attached to Geforce 1080, CPU built in graphics disabled. There is no permanent screen that's not going anywhere, as in laptop.

Problem somehow relates to how Windows 10 (and probably 11) no longer has "virtual graphics adapter" inside it as Windows 7 and earlier used to have. When the primary (and only) screen is gone, it's now "headless", and operates in little unusual ways. This becomes evident with various remote desktop tools, such as VNC and its many variants. I found it necessary to install HDMI dummies (simulating connected screen with various screenmodes available) into my headless boxes, which would not play ball in any other way. What seem to be hardware accelerated surfaces, no longer draw (so they remain blank), because there's nothing to draw on. Despite the GPU still being there.

Thanks for your report. What is your monitor setup? Do I understand right that you are running WinSCP on a primary external display and your disconnect that. And WinSCP gets moved into the internal display (which is now becoming the primary/only display). What is scaling of both displays?

When WinSCP is running and the display device is disconnected (monitor powers off, unplugged HDMI/DisplayPort cable, or when whatever event temporarily removes the monitor – such as something like "Samsung Display Optimization" kicking in without asking, which was the latest for me), the application window collapses into a tiny unreadable frame and CPU usage on one of the cores spikes to 100%. If there were transfers underway, they continue in the background, but the UI becomes unusable/unresponsive until WinSCP is forcibly killed.

Likely WinSCP is not handling missing primary display correctly. Possibly related to unhandled WM_DISPLAYCHANGE or WM_DEVICECHANGE messages in the UI thread?

OS: Microsoft Windows 10 Enterprise LTSC (x64) Build 19044.6218 (21H2)
WinSCP v6.5.3 (Build 16364 2025-07-16)
GPU: Geforce GTX 1080
Screen: Samsung Odyssey G8 32" 4K OLED (but said quirk has happened on other screens and other gpus)