I've updated from beta 2 to beta 4 earlier this week, and I'm noticing two bad regressions on Windows 10.

I run three monitors using nVidia Surround, and have split them back in three with DF's monitor feature. I have no start menu app installed, using Win10 vanilla.

First off, the start menu will only open on the left monitor no matter what start button I push. This worked before.

Second, windows no longer fully maximize. They instead stretch to the virtual monitor resolution. This is most noticable in top tab browsers like Chrome and Opera: instead of merging the titlebar and top tabs the tabs remain below the title button, as happens when the apps are windowed.

Both worked as expected with Beta 2, and if I close DF, window maximizing works as well (of course, stretched across all screens).

Apologies if these are known, I couldn't find them in the most recent forum threads.

No, that process is not active.
I also did get the prompt from DF to disable nVidia processes after the recent driver update.

Thanks, that build works as expected for me.
Start menu now again opens on the monitor I click the button on (or where the mouse cursor is, if I use the key).

The change in maximized window handling makes sense as well. I can live with the few missing pixels in a web browser

Hey Keith!

I installed the version above and it fixed THIS!

Thank you!