After OS sleep, need to restart explorer to make switching effective

[xgdgsc]

like #344

• WDD Version: 5.5.0 on WoA
• OS Version: windows 11 24h2 (RP channel)

Steps to Reproduce:

1. OS sleep during switch time
2. resume from sleep
3. The switched wallpaper appears in Win+tab thumbnail but not on actual desktop.

Are you using the Microsoft Store version of WDD?: Yes

I believe it' s more of a Win bug (and reported to MS via feedback already), just wondering if there can be any workaround here?

[xgdgsc]

Clicking on "Show desktop icons" would also make it switch the wallpaper properly.

[t1m0thyj]

@xgdgsc If you select "Refresh Wallpaper" in the WinDD system tray menu, does this also work to switch the wallpaper properly?

[xgdgsc]

No. That doesn' t work.

[pull2play]

I updated to 24H2 yesterday and I just want to add that on my system this bug extends to any reboot as well. The only fix is the icons on/off trick, and only until the machine wakes up or is restarted. After that, the wallpaper will get stuck again. This is on the latest version of WDD (5.6.0) downloaded here and 24H2 (26100.1882).

[wildyaboku]

I also updated to 24H2 and the wallpaper has stopped updating entirely unless using the above icon trick or restarting explorer. The "refresh wallpaper" tray action does not work. It seems 24H2 has broke something.

[t1m0thyj]

See #631 (comment)

[pull2play]

See #631 (comment)

I tried the replacement exe but it didn't change anything. The wallpaper remains static after reboot. The icon trick is still the only solution.

[pull2play]

See #631 (comment)

I don't know whether MS pushed an update that I didn't notice or what happened, but everything is working as it should now. I'm still using the replacement exe.

[t1m0thyj]

Wallpaper Engine also reports this issue has been fixed in a recent Windows update:

Microsoft seems to have fixed this issue today, use the "Check for Updates" in the Windows Update settings to grab the KB5050009 update:

https://support.microsoft.com/topic/january-14-2025-kb5050009-os-build-26100-2894-bdbfb097-ea20-487d-9171-718d15e26f1b

It's advertised as a security fix but it also seems to contain the bug fix that we discussed with Microsoft, so everything should work well for users affected by this specific problem.

Could more folks who had the issue report back if the Windows update has fixed it?