No Menus available after Monitor switch

Hi all

At first I noticed this issue while working in a KVM setup when I need to swich my monitors between workstations. But those days are over now and I'm back to my single machine with two monitores attached.

I'm sot 100% sure when this all started but it was some DR 17.x ...

So, the Dual-Screen Mode is activated and everything works fine ... I went off to my break and the screens didn't just swiched to the screensaver but after 15 min to powersave mode.
When I came back and tap the mouse, I noticed that my second monitor came back a bit quicker than the first, making him 1st screen for a second until the other was fully back on and Windows 10 swaped them back to their original settings.

However this "one second" is enough for DR to "belive" it has lost one monitor and eventually switches "half way" into a single-monitor state. Unfortunately when something like this occures, you'll no longer be able to click on any menus from the top-menu bar.
Whatever you do no options will be shown ... no "save project" no "quit DR". Only Alt+F4 (or Taskmanager) can kill the program.

You should not let your computer sleep or hibernate with Resolve open. When it awakes not all processes within Resolve automatically start so causing problems. Resolve is not alone in this as Pro Tools behaves in a similar fashion.
From the setup guide.

Power Settings.JPG (47.83 KiB) Viewed 255 times

Similarly you should change the power management settings for USB.

USB Power Management.JPG (81.99 KiB) Viewed 255 times

You should not let your computer sleep or hibernate with Resolve open...

Well the computer does not go into hibernate ... only the monitors switch to powersaving mode

A monitor going into Powersave mode, or a screen saver, will take away that monitor from Resolve.

true ... and once you tap your mouse or hit any button ... the monitors wake up and are available again ... so what's your point ?

IMO two thing happen here ... given the fact that one screen is "faster" (back on) Windows accidently assign it as Monitor #1 instead of #2. When screen 1 is back, it revers the assignment to the initial/correct but hal already passed the wrong information to DR

Second: DR got info from Windows and switches "half-way" from dual to single Screen mode. But here the error/bug occures and no top-menus are clickable anymore ...