The Maximize/Restore button closes the IDE when I click it. The IDE is stuck in Maximize mode on my second monitor, and when I click Restore the IDE closes.
1 Like
In the file C:\Users<User>\AppData\Local\RStudio\log\rdesktop.log I have the message:
2026-05-29T02:22:37.333Z ERROR Main window closed unexpectedly
Note if I remove the whole C:\Users\AppData\Local\RStudio folder to get back to default settings I still get the same fault.
1 Like
Which operating system (Windows, but 10 or 11?), and which version of RStudio?
1 Like
As a workaround, does double-clicking the title bar (which is another way to switch between normal and maximized for Windows applications) work? Double-click on an empty area of the title bar, not on the window controls.
1 Like
You can also try doing it via the keyboard. With focus on the window, use Alt +Spacebar to bring up the window's menu, where there will be a Restore option.
Double-clicking the title kills the IDE. Alt+Spacebar on now Windows brings up an input editor.
I'm running the latest version of R Studio 2026.05.1 Build 225 and have Windows 11 Pro 25H2 26200.8655 fully patched/updated.
1 Like
Alt+Spacebar on now Windows brings up an input editor
Interesting, that's been a standard shortcut on Windows since ~1985, so you have something overriding it. Powertoys, perhaps, or are you using an IME?
Anyway, that's just a curiosity, if double-clicking the titlebar also kills the IDE, then most likely trying to restore via the keyboard/system menu is going to do the same.
That said, does the standard Win+Down-Arrow also crash RStudio when it is maximized?
Did this start happening with 2026.05.1? Does it happen with any previous versions you've tried?
I recommend opening an issue with as many details as you can (RStudio version, R version, Windows version, monitor details including the arrangement and resolutions, DPI--especially if one monitor is high-dpi and another isn't--language-settings for Windows, whether it happens with any previous versions, etc.).
In the meantime I'll see if anybody else here can reproduce this (I don't have a multimon setup for Windows).
So far it is working for people who have tried it here, so it's isn't a universal problem.
Win+Down-Arrow also crashes RStudio when it is maximized.
It is a screen resolution issue, as my second monitor is 3840 x 2160, and I have the scaling set to 175%.
My primary monitor has the same resolution of 3840 x 2160 but a scaling of 150% as it's bigger (43" vs 32"). When I reduce the display resolution to 1920 x 1440 on my second monitor it works as expected and doesn't crash. This let me get the IDE back to my main monitor, where at full resolution it can be maximized and restored without crashing.
1 Like
I suspect now that R studio doesn't validate the saved window position before restoring. This is probably the cause of bug. Anyway, I have the IDE behaving again and know how to fix it if it goes wrong again. Thanks for your help Gary.
Final note - PowerToys was grabbing the Alt+Spacebar shortcut, and when closed this worked as usual.
1 Like
Where is your secondary monitor relative to the primary? As in, to the left, above, to the right, etc. Knowing if we're dealing with negative coordinates (left and/or above) would be a useful hint.
RStudio does have logic to deal with changes in monitor resolution/configuration when restoring, but your situation suggests there are cases it's not handling correctly (unless we're hitting an Electron bug, which is also a possibility).
Another question, you said the problem goes away when you switch secondary monitor to 1920 x 1440. When you do that, did scaling remain at 175%?
Another test that will help identify if this is a GPU driver issue, change RStudio to software rendering, then close and restart, and see if the problem still happens.
Tools > Global Options > General > Advanced > Rendering Engine set to Software.
Sorry, now I've fixed the bug it may be some work to recreate it. My second monitor is in the usual position of being beside the primary monitor on the left. When I changed the resolution on the second monitor, the scale was the automatically set to a default 125%. I've tried to recreate the bug, but now my settings are OK, setting the size of the IDE to greater than the screen size and maximizing/restoring on both screens works fine. It may just have been the desktop settings got corrupted somehow.
2 Likes