I'm trying to set up monitor profiles on a new computer running Windows 11, and the problem that I'm having is that one monitor won't disable. Graphics card is a 3070, The monitor that won't disable is one HDMI; the rest are on displayport. In the representation of the monitors on the screen it looks like it is disabled, i.e., it moves over to the right. It just doesn't go off. I didn't have this issue on my previous Windows 10 machine with the same monitor. I'm using the newst stable release of DisplayFusion Pro, 9.9.

Thanks, this seems to have resolved the issue. Although I'm noticing something else now, which is that the taskbar seems to be disappearing on some monitors. I haven't had time to play with it much, but I'm thinking that maybe after I had an application open full screen it's not coming back once the application is closed.

No. Is it possible that DisplayFusion is crashing so that I'm losing the taskbar on all monitors but one? I just noticed that I was in this state and so I tried to open DisplayFusion. The icon was in the notification area, but when I clicked on it it just disappeared. I restarted and the taskbars came back.

I have updated, which fixed the problem of the monitor not disabling. However, that's when I noticed the issue with the disappearing taskbars, which continues to happen. And it has now happened even when DisplayFusion was running, so it's not just crashes.

Attached. I was away from the computer and the taskbars were missing when I got back, which I think is what usually happens. This means that I can't give you an exact time.

Hmm, here's a funny story. I think that explorer.exe is crashing. And this sort of rang a bell with me. I felt like I had seen the issue before on my old computer, but I didn't remember what caused it. So then I looked at an old post of mine here, where I wrote the following in response to another user:

Probably not helpful, but I recently had a similar issue with explorer.exe crashing when the system was idle. While I initially expected that DF might be the problem, in my case it turned out not to be. For me the workaround, if not the solution, was going from using DP to HDMI for a specific monitor. I don't really understand why that fixed it, but the problems disappeared.

I had forgotten all about this, but I bet that is what is causing my issues now. I have a new PC but the same monitors. New graphics card only has one HDMI port, so some monitor that used to be on HDMI is now on DP. I just have to remind myself which monitor that is.

Right now handles are 1,082, user objects 194, GDI objects 124. However, this morning I moved that tricky monitor off of Displayport and the issue hasn't recurred. Someone on Reddit suggested to my that I might have a bad DP port cable with the pin 20 problem, which I didn't know about, so I have ordered a replacement.