Keith,

You wrote: "There's currently a bug with the Monitor Profiles where they can get overwritten with bad values in some cases. This will be fixed up for the next 9.0 Beta. We will let you know as soon as it's available to try out."

Any update on this? It's really frustrating!! At one point I did something that triggered DF to tell me that the three extra monitors were not attached anymore and did I want to save the now-corrected profile. I said yes, and the problems went away.

Thinking the problem had been fixed, I then switched to the other profile. Sigh. Problem back.

I've deleted the Monitor3, Monitor4, Monitor5 entries from the profile in the registry, uninstalled graphics driver and card, installed a different card, but the problem persists. Can you tell me what I inadvertently did before to trigger DF to fix the problem?

Also, the WallpaperHistoryV4 file now has duplicate set entries. WallpaperHistoryLocalComputer201 was renamed WallpaperHistoryLocalComputer203 and the ...201 set was restarted. It did this for each set in the database. Will this get fixed or should I just delete WallpaperHistoryV4 when this fix comes out?

I couldn't wait for the next beta so a few days ago I restored a system image I had taken a couple of weeks prior to getting caught up in this mess. In my case the left and right monitors #2 and #3 had become swapped (#1 in the center) and nothing I did could get the monitor profile to correct itself again. In the system|display properties there were six monitors, 1-2-3 active, 4-5-6 inactive and unselectable.

After restoring the system image monitors #2 and #3 were partially restored. While the monitor profiles (splits) were now showing on the correct physical monitor, and proper left-right mouse cursor movement had been restored, the monitor IDs had become permanently swapped: monitor #2 was now #3, and #3 was now #2. But no more monitors 4-5-6.

Interestingly, the wallpaper profiles remained attached to the monitor ID numbers so the wallpaper slide show images were showing up on the wrong physical monitor. This was easy enough to fix though.

Whether you intended it or not, it seems DF found a way to permanently re-assign the ID number Windows assigns to physical monitors, permanent to the extent of overriding a system image restore.

Well, this was a beta release, so I had been warned. But I am going to be much more cautious in the future about installing betas.

Same problem here. DF worked well for 1 year but now after updates I have to create again and again the profiles which is kinda annoying.

"An error has occurred while applying your new monitor config....Error HR 31"

Any effective fix to this?

Current release installed:
PRO 10 (beta 7)

Looking forward to hearing from you.
Andre

Hey there!
thanks for getting back to me.

No 100% sure but the profiles stopped working regardless of the updates (DF or Windows).

Thanks
Andre

Sorry for bumping an old thread by the way

Hi there!

My docking station might be the reason of corrupted profiles.
I will try in the evening to connect the external display directly to my laptop with a DP cable.

My 27" external display is shared among 2 laptops through a docking station.
Basically I am switching laptop once per day (second laptop got an older version of DF, also profiles created on that laptop worked 24 hours tops).

I'll report back sharing the result.
Thanks in advance for your support!

Hi Keith,
my guess was unfortunately correct.
All profiles work wonders if the laptop is connected directly to the external display.
Issues arise when there's a docking station between laptop and external display.

What do you think? Is there any fix/workaround?

Thanks!
A.

Hi Keith
any insight to share?

I realized profiles get corrupted only on one laptop.

Thanks!