I purchased Scrivener and ProWritingAid in July, 2026 and everything worked perfectly until yesterday. Now, the blue and red lines from ProWritingAid that suggest where I should make corrections (missing commas, periods, misspellings, etc.) appear at strange positions on the screen instead of directly under the corresponding text. The corrections still work but I have to hunt around for what was corrected. In addition, when I click on any option on the main toolbar (File, Edit, Insert, etc.) I see that the panel that opens up does so far to the right, not directly under the selected option.
This doesn’t happen all the time. Sometimes I can fiddle with the Scrivener screen, moving it between my two monitors (both 1080P and both set to the same resolution) and it seems to fix the problem but then it starts again a while later. I believe that this is a problem with Scrivener, not ProWritingAid and that it has to do with something about my graphics settings. I have tried playing around with the Display Settings and Personalized Settings, but the problem persists. Does anyone have a suggestions that would help to solve the problem? My laptop is an Dell Alienware with built-in RTX3070 video card. Maybe there is something about how Scrivener interacts with the video card that is the problem.
One quick test I would try, to see if PWA is the common factor, is to disable its integration with Scrivener temporarily or better yet quit it entirely, restart Scrivener, and see if the problem with the menus appearing far away from the menu buttons, still persists. If it does reproduce even with PWA turned off, then yes it might indicate there is some kind of compatibility issue (maybe even hardware, but I think that particular card is common enough) that is causing a mismatch between where the window is, and where higher level interfaces think it is.
OK, I exited Scrivener, signed out of PWA and even went to the Task Manger and ended the PWA task to make sure that it was completely turned off. After that I ran Scrivener again and the problem persists. What is strange is that the issue happens on the external monitor all the time now but doesn’t seem to happen on the main laptop monitor, but I have seen it happen a few times on the main laptop monitor.
So, I did one more test by switching the monitor position on Display Settings. I changed monitor 1 to be my external monitor and monitor 2 to be the laptop monitor. Now Scrivener seems to work correctly on both monitors. After switching it back as before, Scrivener again does not work correctly on the external monitor. So, after doing a few more searches on the internet to search for a solution I came across a comment that said to make sure that the “Scale” should be set to the same exact number for both monitors in the Display Settings section of Windows 11. My settings were 100% for one of the monitors and 125% for the other. Now they are both set to 100%.
That seems to have worked. If the problem keeps coming back I will report here, otherwise I will consider this problem solved.
Thanks for the update! Glad to hear you’ve come across a useful workaround. Hopefully 100% on both screens isn’t too small for one. I bet all of this falls under general display issues we’ve been seeing in more recent Windows 11 installations, where mismatched monitor settings can cause layout issues. I don’t recall the menu detachment thing being a part of that, but UI text sizes not resetting properly, icons being too small or large, and that sort of thing, is definitely more common. This can be a lot worse if the monitors themselves are very different (4K vs some little regular res laptop screen).
The main problem is that the coding framework Scrivener is developed in is getting a little long in the tooth (I think it might even be from when Windows 11 was still in the Canary phase). We’re overdue for an upgrade of that, and have in fact been gradually working toward that with our other coding projects. Scapple, for example, is going to be running close to the latest. Hopefully by the time we get back to working on a Scrivener update we’ll have all the thorns worked out and it can be easily adapted.