I have Windows 11, up to date as of 12/21/2025, and displayfusion v12.0.1 (updated today). Unfortunately, the wallpaper setup I use doesn't seem to be working any more. I have three monitors, APOD slideshow on one, a slideshow of wallpapers from a local directory on my computer on the main monitor, and google earth images slideshow on the third. Unfortunately, while the scaling setting seems to be changing when changed in displayfusion, the wallpaper images do not seem to be being set properly or put into the right locations. All three screens only display the single image defined in the Windows background configuration now. It was working properly yesterday, so I strongly suspect the v12.0.1 update.

Since this is the first time I've had an issue with DisplayFusion, I'm not sure of the debugging process, but I've attached a DisplayFusionDebugInfo zip file.

Here's the debug info collected according to your instructions. At 12/24/2025 2:40PM or so, I went into the Wallpapers view and checked each setting, then clicked "Apply" and finally, "OK". Displayfusion made a popup saying it was downloading images and nothing happened on the screen after that. A couple minutes later I took the debug info file.

I had already configured an APOD API key.

Thanks and happy holidays!

Having a similar issue here. I have three monitors, and it is set to span the image across all three. The center monitor sometimes displays part of a different image than the other two. When I logged in this time, it had the same image spanned across only two screens, and then the third had the same image as if it was spanned properly.

Usually it displays something different on the center monitor. It's a section of an image as if it is spanned across the three, but not what is supposed to be displayed across them.
I initially thought it was due to some issues I was having with Windows, so I re-installed Windows. Then was disappointed to see that the issue still existed.

I have attached the logs requested.

Adding a screenshot of the settings and issue. This time it appears showing the Windows background instead of one of the images.

FWIW, I tried this at your emailed instructions. (Thank you for the quick reply.) It didn't work for me. Furthermore I noticed that DF is no longer auto-launching, despite being in my Startup apps.

I've attached my log, collected at 10:27 AM Pacific Tuesday.

Note I've replied to another thread (Kieth L) with this info as well.

Initially, it appears to have worked. I won't know for sure until after I've woken the computer from standby a few times, or it changes on it's own a few.

Nope, that did not change anything.

Attached is a new log I set up to record when I made the changes last night.

An update. After a couple of system restarts, it seems to return to normal.
However, after the system goes to Sleep the issue returns upon waking it.

For me, this fixed the wallpaper issue.

However (as I mentioned in a similar thread), it doesn't fix that DF won't launch from the context menu, nor (as I just discovered) from the installed Desktop shortcut.

I thought this solved the problem for me as well but it did not.
A bit of information worth sharing;
The UAC screen which is normally plain black was the correct images (image slideshow) when I went to install the beta.
I did not delete the file suggested in the conversation, and when the installer ran, the images appeared correctly.

The problem seemed to be that whatever DisplayFusion was rendering at the time was incorrect.
Sorry I don't have a log to share.

I can also confirm that on my setup the context menu does indeed launch DF's settings however there is a problem;

The images do not change when using the context menu's "Go to next image in slideshow" and crashed to a black screen.
The only way I had gotten them to change properly is via pulling up the wallpaper settings menu and changing profiles and then going back to the intended profile.
This I can provide a log for.

I uninstalled DF (keeping settings and proficiencies), then reinstalled using the provided link, and everything works. Thanks!

Here is an image of what happened when trying to go to the next image in the slideshow.

I checked to see if the image was correct behind the UAC layer, and it was also black in the background as well.

I restarted the PC to see if it would fix things. The result:
Monitor 3 (Primary monitor), the image shown in the post here was on the lock screen, and all monitors when logged in were still blacked out.

Important note:
This only started acting up the moment I installed Nvidia Driver 591.74.

Tried deleting the "TranscodedWallpaper" file, upon restart no change to the behavior. (The "TranscodedWallpaper" file instantly recreated itself when deleted.)
Here is a fresh log from that restart.
Behavior: Lock screen is still the only image displayed, all monitors are black when logged in.

This did not. Attached log.
Attempting to force the slide gives the notification but no change.

Yes and no.

Behavior:
Now, the images do change, but they take some time, and are not entirely synced up to the preview in the window.

On the first initial load, it did load the wallpapers on each monitor. This is good.
However, when using the cotext menu's "Load next slideshow image" it would take some time to sort the images. This in itself is fine, but it didn't seem to switch until the moment I brought up the settings menu.
The images were different in the settings menu when it came up, and then set to the images in the preview as expected. This is also good.

After bringing up the settings menu, I wondered "Would the image change if I left the settings menu up?"
It would then change the images, but to a set of images which did not reflect the settings menu.

This is where the odd behavior would begin. The preview window would now have changed, however the wallpapers would not have changed by this point.

I feel like I'm not overdoing things, and being patient between each call. I'll attach the log here, and a subsiquent image of the behaviour. While the images are displaying, it is fine. However there is some quirky behavior that may lead to the discovery of the underlying issue in this regard, as you've come so far already.

I hope this helps.

This is the behavior that appears when closing and re-opening the wallpaper settings menu.
Where before, opening the settings seemed to kick things into gear, this is how it stays now.

I'll try using the context menu again to see if it changes, or is truly stuck in some way.

Correction:
The images changed, but they did not reflect the images in the preview. I beleive this was the behavior.
The initial images that were there when I launched the new build were stuck when using the context menu, with those same images being in the preview screen.
When proceeding to the next slide was when the images changed, but they did not match the preview images, but only when I closed and reopened the settings menu.

Sorry if this is complicated or based on coincidence.

This time it did change, but the settings menu did not update until closing and reopening.
I'll provide the unchanged (not yet closed) screenshot, and then the changed (closed and reopened settings) screenshot, followed by the final log.

Closed and reopened settings.

The full log from today's Beta 5 install from start to finish.

It is not. Provided image of those settings.

At current it is functioning correctly. Those bits of information were to hopefully offer something that I might not be seeing, such as some underlying issue with synchonization.

As far as testing with OBS off, as it's currently working as intended, it'd be hard to tell. Those bugs mentioned were just the oddites prior to DF returning to functional stability in regards to the wallpaper issues.

I was unaware it was running in fullscreen on that window, but that would make sense thinking about it with my setup.
That display is actually a dummy display used to project OBS on this secondary PC. The purpose of the different wallpaper image is through OBS that screen can be monitored if the preview window is currently active using a seperate scene.

That aside, since it's currently functional and you're not seeing any issues on the log's end, I can say I'm happy to report that it is indeed functioning. I appreciate all the help! Keep up the amazing work!

If I have any more active problems with the wallpapers, I'll report those issues in a new thread.

Edit:
The upon review; I hadn't even noticed on Beta 5 the wallpapers are natrually cycling at the expected times as well. All is well!

Sorry to have dropped out of the discussion for a while, but I was very ill for a few weeks. Coming back to the issue, I tried the update links you had asked others to try, but it seems to have expired. So I decided to update to the current Beta build (v12.0.2 Beta , and at least on the first startup, the wallpaper setup I had configured DOES seem to be working. I will let you know if it stops working.

Thanks,
J