安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
On my device, whether I've tried to turn off & on desktop icons via Windows (including controlling the desktop icon opacity on the Wallpaper Engine settings) and then restart computer (vice versa every I restart computer), the Wallpaper Engine is not broken and the wallpaper fully loaded either with audio media or not.
I dunno if this trigger that make Wallpaper Engine recovered to use on 24H2 due to I've using DWMBlurGlass[github.com], ExplorerBlurMica[github.com], and TranslucentFlyouts[github.com] altogether recently, which for DWM & Flyouts, it require to download Symbols from the microsoft server.. or not from those...
All three of them I've used are the latest version one.
As I'm writing this,
the DWMBlurGlass one are recently being updated to support 24H2 about two weeks ago,
TranslucentFlyouts last update is about 9 months ago,
and the ExplorerBlurMica last update is about 10 months ago.
Even I've disable all three of them, including TranslucentTB, the Wallpaper Engine is worked even after following your statement (on/off-ing the desktop icon both before and after restarting computer)
If you want, I can try reproduce it with video record and debug log tho for the desktop icon on & off condition, and when those 3 apps on and off condition tho. But, this'll takes time for me :'
Just you need to know, that this KB5048667 / 26100.2605 also fixed the built-in Windows Slideshow option as desktop background on Windows Settings. At the previous month update, this problem didn't fixed, but from this update, it's fixed on me.. though microsoft didn't write about this on the windows release health documentation or even on it's KB release note...
It maybe also related with this tho.. Idk man, this is really unexpected :')