Looks at the pictures first. The first shows that Desktop wallpaper thinks correctly that I have configured a mix of wallpaper and gradients and the monitor view of Monitor Configuration shows the actual mess displayed. When I press Apply on Desktop wallpaper, I get picture two. Note that Allow DisplayFusion to manage Desktop Wallpaper is checked in the first picture and unchecked in the second (after additionally pressing OK and redisplaying the dialog). To get the proper config to set, changing the sizing didn't work. But clicking Don't stretch smaller images did. I subsequently unchecked that.

I hope that gives you the scenario.

Odd stuff happening in log. Wallpaper config is about 8:24 ish. Windows logon a bit earlier. I'm also including the troubleshooter.

Sorry I didn't follow up before, but the wallpaper scramble is happening again. I had to change a setting on the Desktop Wallpaper panel (gradient) to force DF to reload the wallpaper and gradients I am using on my four monitors. (Very similar to my previous picture.) This symptom didn't reoccur until after bringing Windows 10 up to date with patches a week and a half ago. Prior to this, I would occasionally see a scramble but DF would unscramble within about 10 seconds, which seems to be the intended behavior on Windows 10 when Windows 10 asserts control after logging in to a locked session.

BTW, Allow DisplayFusion to manage the Desktop Wallpaper is checked.

I am attaching my exported settings, the log file which has FAIL warning about wallpaper, and (in a second reply) my troubleshooter.

Here is my troubleshooter output.

>So you're back to the original issue, where the wallpaper is scrambled after logging in, and just opening the Desktop Wallpaper window and clicking Apply doesn't fix it?

Yup, that describes it. I waited over 15 minutes, as can be seen in the log, until I endeavored to correct it. I also supplied what you requested last time when I lost track of the issue. (Sorry)

No help.

Since I logged in yesterday (on a machine that had been up for a week), I had scrambled wallpaper. Logged on today and found it still scramble. Went to this discussion. I hadn't gotten the notification email (betting it got junked) so I didn't realize you replied. I followed the instructions. No change. I tried changing the wallpaper by right-clicking the DF notification icon > Desktop Wallpaper settings > Wallpaper Profiles and switching between "default" and "Windows 10 Mark 1". In both cases, I momentarily see the proper wallpaper fade in, but it disappears to be replaced with the scramble.

Attaching the log which should show you want DF did. Oddly, logging only started when I opened DF to do what you requested in your previous reply.

My wallpaper is still scrambled.

EDIT: I haven't logged off yet. Maybe it will fix it going forward. Dunno.

I logged off (using Windows-Lock) and logged back in 45 minutes later. Still scrambled.

The sign-on I use is both for my physical machine and for all LAN resources so I reconnect to LAN drives. I don't know what a "Microsoft Account" is per se. My user name and password is defined to Windows and to the authenticating LAN resources including both Windows servers and IBM mainframe hosted file systems. Probably TMI. When I use Microsoft Remote Desktop to log in on alternate days from my Mac, it also uses the same username and password.

All syncing was off.

Okay, this is odd. I logged on to my locked computer, incidentally with the Settings dialog displayed since the 22nd (today's the 27th). The system was acting loggy and the DF caption bar buttons were AWOL. I closed the settings dialog, but no DF caption bar buttons. I pulled down the notification DF menu and it froze. Nothing I could do and after two or three minutes, I terminated DF and it's two hook processes.

While it took about 10 seconds to come down, my wallpaper positions including the gradients restored themselves. Everything is now correct, with DF off. I am going to assume there is a relation here. Find the DF log file attached. The last lines in the log are when I terminated it. I'm hoping something of interest is in there. It runs from the 22nd of December.

After I post this reply, I will restart DF. EDIT: It came up fine; no issues.

Will do. I gather you have no insight yet into what's causing the intermittent wallpaper problem. Everything is currently working properly.

Ugh! I moved a window and found my wallpaper messed up again. I started Desktop Wallpaper, tried pressing Apply twice with no correction, then unchecked Allow DF to manage wallpaper, pressed Apply causing everything to go black, then checked it and pressed Apply which caused the wallpaper and gradients to show on their proper monitors.

I am attaching the log.

At somewhere 2017/01/05 10:11 to 10:12 and 10:13, I snapped a window from monitor 1 to monitor 2. Following that, I followed the procedure above.

This may not find you the reason the wallpaper is improperly positioned, but it should show you why the apply doesn't work without unchecking, checking Allow DF to manage...

Good hunting.

Sorry that I missed your last reply on June 8th until now. Sometime after our conversation had ended on January 6th, following some subsequent beta release, my problem appeared to have been fixed. However, once I installed 9.1, I noticed a regression and decided to reopen this issue that I thought erroneously had been resolved.

I am now using 9.1b1. There is one difference from my original report: If I click Apply, the wallpaper always conforms to the schema shown in the dialog.

So, I have now applied the advanced setting "Wallpaper: Force Desktop Refresh After Wallpaper Change" from your June 8th reply. I followed your instructions and restarted DF. This, not unexpectedly, caused the proper layout of an image on monitor 1 and a gradient on 2 through 4. To test further, I switched user and came back. The screen at one point showed a mosaic of images then showed the right schema again.

So, I tried the other thing I do that might cause a problem. I remoted into my workstation using Remote Desktop. When I logged back into my workstation after that, the mosaic of the images reoccurred, but after about half a minute, and much blinking, went back to the proper schema.

I think you have a found a workaround for my problem. However, I hope it points you toward the problem code because something tells me an advanced setting is not really the best solution.

If there is a re-occurrence or regression with the workaround, I'll write again.