Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The anti-virus and pc cleaner software can both definitely affect this. Please check them entirely for such blocking features and either configure them to allow Wallpaper Engine or disable the respective feature.
The VPN has nothing to do with this, but the others can, yes.
Yes, it's always possible that Microsoft breaks things with updates, they are not guaranteeing that updates or even Windows 11 is working flawlessly.
If it worked before and then stopped working the next day, anything that happened on that day should be looked at first. If you installed multiple new programs that manage other programs (an anti-virus and cleaner like you said) and additionally installed a major Windows update, then any of those things could be the reason.
Maybe completely uninstall the programs you newly installed, then go into Wallpaper Engine and turn the auto start off, then on again to re-register it.
There are a considerable number of reports that 22H2 is buggy, it was just released, many people get entire system crashes.
https://www.windowslatest.com/2022/09/23/windows-11-22h2-issues-fps-drops-bsod-installation-stuck-and-other-bugs-hit-users/
https://www.windowslatest.com/2022/09/24/nvidia-confirms-windows-11-22h2-is-causing-performance-issues/
https://www.guru3d.com/news-story/nvidia-geforce-cards-have-issues-after-windows-11-2022-(22h2)-update.html
It was working without issues for a while, then it suddenly stopped working. So the question is what changed and caused it to stop working. You mentioned that a number of fundamental changes happened at once, so the best we can do is suggest you to look at them one by one and re-register the auto start in case anything just went ahead and disabled it, like the cleaner you mentioned.
So Kaspersky is interfering with the auto start? Then you should configure it to ignore Wallpaper Engine and/or not to interfere with auto starting programs and services generally.