Hello,

today I noticed that DF 10.1.2 on Windows 10 seems to have problems changing the wallpaper. Trying to open the Wallpaper settings does not work. The settings window does not open.
Trying to restore a backup of the settings works, but with an error message that the wallpaper file cannot be opened.
Trying to backup the settings gives a hint about what's going wrong: I get an error message that the folder location on the internal SSD cannot be accessed. My user folder is offered as an alternative, but that doesn't work either.
It seems to me that DF lost it's access rights to any folder on the SSD.

Further Tests:

My account on the PC is a restricted account and here I have problems.
On the admin account everything works fine. DF has access to the SSD.
Another user has a restricted account on that PC and here DF also works fine. No access problems on the SSD.

Uninstalled and reinstalled DF. My settings were apparently not deleted during uninstall. The problem persists.

Tried the Troubleshooting section:
No information shown in the window. I am not able to change the log setting (L0 - L3). After changing to L3, clicking 'apply', leaving the section and re-entering it, the setting is L0 again. Apparently the SSD access problem also prevents logging.

Last chance:
How can I uninstall DF and remove all settings, in order to do a clean install?
Or does anybody have an idea how to get DF running on my account again?

Thanks in advance,
Christian

I tried to export all settings of all users and found that the other restricted account also has permission restrictions.
Exported all settings to an external disk. The I uninstalled DF and removed all relevant folders from:
- Users AppData folders
- C:\Program Files
- C\ProgramData (Nothing in C:\Program Files (x86))

I went through the registry and deleted all keys relevant to DisplayFusion

Then I reinstalled DisplayFusion: Same problems.

Any other ideas?

I can edit these registry keys.


There's nothing there.

OK, that's interesting.
I stopped DisplayFusion, then went into the registry and set this value to '3':

Opened DisplayFusion again and checked the 'Troubleshooting' section: Log level is still '0'.
Tried to set it to '1' and clicked 'Apply'. Then closed the window and opened the 'Troubleshooting' setting again.
Log level is '0' again.
Through all this the registry entry did not change and stayed at '3'.

This key does not exist:


Here's an additional information: I'm running monthly image backups from my system SSD. I restored the image from September 1st, yesterday. The problem was gone and everything was working again.
Then Windows update run the 'Cumulative update für Windows 10 Version 22H2 (KB5043064)'. Everything was still fine after restart.
But today I started the PC again and the problem is back.

It's my personal Computer

A little update:
I restored the system image from September 1st, again, as described in Post #7. Everything worked fine again.
I avoided the Windows update KB5043064 for some days and no problems appeared.
Finally installed that update again and the problem is back.

Something is changing with KB5043064.
Can you check?

Thanks for checking. I was thinking about formatting the SSD and reinstalling the system from scratch. However, I checked on the laptop of my son, i.e. a different computer.
He's not using DisplayFusion actively, so he didn't notice it, yet. But he has exactly the same problem.

The only commonality to my PC is that I installed his laptop for him years ago. And it's running Windows 10 Pro.
Did you try the issue on Windows 11 or Windows 10?

Here's the information about the system:
Windows 10 Pro
22H2
Build 19045.5011
Windows Feature Experience Pack
1000.19060.1000.0

I installed Beta 8 and it seems to work. No problems with the wallpaper settings and it is possible to export the settings.

Curious:
During all my tests I restored the system image from September 1st multiple times. Every time the problem reappeared after installing the cumulative Windows Updates from later dates.
Last time I postponed these updates until today and I wanted to have the issues reappear before trying Beta 8. But the issue did not reappear after the windows update. I'm scratching my head over that. Did Microsoft repair something?
Fortunately I also had a system image from a time where the issue was present. I loaded that and tested Beta 8 there. The Problems dissapeared with Beta 8.