Hello, not sure what was changed in the latest beta, but my 3 monitor (extended) profile stopped working after updating to it (maybe related to this thread).

I have a 3 Monitor (Duplicate) profile where my middle monitor is the primary, but my left and right monitor are duplicated because I use my left monitor for my work PC during the day. After work, I'll try and use the 3 monitor extended profile to switch the left and right monitor from duplicated to extended display, but it just constantly causes my 3 monitors flicker until I go into the display control panel and switch the left and right monitor back to extended from duplicate.

After reverting to the release build the profiles started working again. Let me know if you want me to do testing or provide logs, or if it's a known issue in the latest beta.

Same kind of problem here with beta9. I have a profile for monitors and a profile for on tv. When I switch to the tv profile it goes into a weird loop where it constantly switches between the two profiles. I have to reset the PC to get out of it.

edit: I reverted to beta8 and that fixed it.

Glad it's not only me and that a rollback confirsm the issue is with Beta 9.

Well the the weird loop is indeed fixed, and switching profiles seems quite a bit faster, so that's very nice. However, when switching profiles it now consistently sets the wrong display as the primary display. Setting the correct primary display in nvidia control panel and saving the profile does not fix this behavior. It keeps changing the primary to the wrong screen. So sadly I can't use this version and switched back to beta 8 again.

I'm very sorry, but like I explained before, I don't feel comfortable uploading those logs. I value privacy (maybe a bit too much) and there's a ton of info in there.

I can tell you that I mainly use 2 monitor profiles. The first profile uses a Dell monitor and a Samsung monitor. The second uses an LG TV and a Denon receiver. The Dell and the LG are set as primary. But when switching profile with beta 10 it changes the primary to the Samsung and the Denon.

I'll download the beta and see if I have a similar problem.

Downloaded the latest beta and the issue with the monitor switching is fixed for me. I don't have the same issue with the primary not saving, but I also don't have a similar setup to JJack33. I have two Asus IPS Displays (don't remember the models, but they are close to 10+ years old) as my side monitors, and an HP x27q as my primary. I never change primary monitors with my profiles since the X27q is always my main display, and the other two are configured to extend or duplicate based on my needs.

I can see about setting up some more profiles and trying to replicate the issue after work today.

Thank you SniperFodder. I can see why it wouldn't be a problem with your setup. When I switch profile I switch to 2 completely different displays, so it will have to set a new primary. I suppose saving a monitor-profile doesn't save which screen is supposed to be the primary? But I'm just guessing here...

Well, in theory Display Fusion should be saving whatever you have in the windows settings when you configure your monitors. There's also a Set Primary Button so you can use to change which monitors you want to make primary in a profile.

Can you double check that your profile shows it greyed out for the ones you want, and if not use the button, then re-save the profile?

When I switch profile it sets primary to the wrong display. If I then go into monitor configuration and click the "set as primary" button it fixes it. I then save this profile. But upon re-enabling the profile later, it again changes the primary to the wrong display. So the set primary doesn't stick. Beta 8 does not have this problem. In fact I've never experienced this issue with any previous version, I don't think.

No difference. Exact same issue.

Ok I see that I'm not the only one: https://www.displayfusion.com/Discussions/View/windows-11-24h2-monitor-profiles-doesnt-work-properly-df110-beta-8/?ID=0192d4f1-3edf-7062-8f40-6c0bac86a62a

Except I'm still on Win11 23H2. For me the issues started with Beta 9/10. Beta 8 works fine.