monitor issues after windows 11 upgrade

Are you running 100% Windows scaling on both monitors?

I tried this on my other AMD computer/internal GPU (with different monitors), and I didn't get the painting problem, but the "tips" were put up in the wrong places on the Quicken window. Something is clearly calculating the locations wrong.

[Merged Post]

Yes, 100% scaling on both

[Merged Post]

That is pretty interesting that it fix the problem. Basically by switching to hardware acceleration, you have switched the way the graphics is being drawn a very low level.

[Merged Post]

@Chris_QPW , in one of your prior posts you wrote that you tested this with one of the past releases and the issue is still there. I have lost count of how many posts I have participated in on this topic and shared my findings (and reported the problem to Quicken as well), but for me this issue has existed for years, maybe 5 years. On multiple computers, monitors, graphics types, monitor cables and ports (USB-C, HDMI, Display, VGA). I cannot recall if it existed in Win10 or not.

The common denominators of the problem, for me, are the following:

• Dell brand laptops (only one we have had in our extended family so I cannot speak for other brands)
• The laptops' "recommended" scaling is 125% (again, that is all I can speak of)
• Scaling being different between the two monitors. If I set the scaling to be the same regardless of value, no issues at all
• Quicken program - no other program has this issue

I gave up on this completely since I am convinced it is an issue with Quicken's code, as you suspected in one of your other comments, that will never get addressed. It is what it is.

If I'm not mistaken, this is the first time I have been able to reproduce the problem. That says nothing about what other people have experienced, only what I could reproduce.

To me now that I have reproduced it and considering now understanding this isn't "new", then there is one fundamental question, I have about the Quicken code, that only the developers can answer. And that is does Quicken override the paint function for the graphs?

If so, the problem might actually be in the Quicken code. If not, the problem is most likely in the graphics library they are using.

Frankly, it isn't that uncommon for Quicken code to get messed up on where to post tips and such when dealing with display setups they don't expect (which is pretty much seems to be anything other than one monitor). But the tips in the wrong place are a bit different than the graph painting problem in the sense that I absolutely know that the "tips" are done by the Quicken code, whereas it isn't that typical to override a graph's painting function, but it certainly can be done.

The Quicken developers might think me a nut for going on and on about the fact that they choose to override things like the main window, but that is based in the fact that what seems simple is in reality very complicated. When you have multiple monitors, with different resolutions/scaling and such, and have monitors that come and go, it gets very complicated to figure out exactly where everything is. That is something that normally is hidden by the low-level Windows system libraries. But of course, if you choose "roll your own" all of that complication has to be taken care of in your code.

Well, that solution didn't age well. After leaving Quicken running on my computer for several hours, I went back to it and it reverted to its old behavior of showing the amount on my secondary screen. Sigh.