Wallpaper engine starts with windows, however, is set to not start with windows...

[Firesheart]

Hello all, I recently came across a couple of issues as of lately, and cant seem to find anything on it. Now, this may seem strange, but I have disabled start with windows in the wallpaper engine settings, however, every time I start up my pc, it still starts up with windows. Now, I wish I taken a screenshot of the second part of my problem, but haven't, so I'll be sure to do so next time, but while it starts with windows even when not selected to do so, I go to try and open it through steam as per usual, however, I get a error message saying its already running but not responding, do I wish to forcefully restart it. I click ok, and I get another error message saying that it was denied.
Link to the diagnostic tool log
https://drive.google.com/file/d/1S0Hdsj8b1e1IK3xZF7Z2bDDCwTDGgSOm/view?usp=sharing

Next time I do start up my PC and get the other error again, I'll be sure to take a screenshot.

the issue with startup with windows when not selected to do so in settings has been a issue with the previous update of wallpaper as well, I just didnt think much of it back then due to life reasons.

[Biohazard]

Maybe you have it installed multiple times, have you ever moved the installation files through Steam?

Also make sure that Windows is not manually starting Wallpaper Engine. If a shortcut was moved into the generic startup folder, then Windows will start it automatically, this has nothing to do with the options in the program so it can't be turned off that way. You can check here if something has put a shortcut to Wallpaper Engine into the startup folder of your Windows account: https://support.microsoft.com/en-us/windows/add-an-app-to-run-automatically-at-startup-in-windows-10-150da165-dcd9-7230-517b-cf3c295d89dd

[Firesheart]

Nope, installed it once, only updated here and there. Never messed with any of the files for the program, or really any as i do not wish to mess up any programs by accident
I do have multiple steam accounts, however its only this one that has Wallpaper engine.
As for the startup folder, it is empty, and task manager does not have it as a startup program.
https://drive.google.com/file/d/1OwgF8UXtkFEnqOj3_c6YFLaLoYXyEy0x/view?usp=sharing

[Biohazard]

Alright, if it's not in the task manager and not in that directory, then the service must not have been unregistered. Can you open the settings in Wallpaper Engine and turn the high priority auto start on and then off again? Unless the program is denied permission for some reason, that will remove the service.


If you can't do that, you could also remove the service manually, but it requires using the Windows command line I'm afraid. You have to open the command line as an administrator, for example like here: https://www.howtogeek.com/235101/10-ways-to-open-the-command-prompt-in-windows-10/#:~:text=Press%20Windows%2BR%20to%20open,open%20an%20administrator%20Command%20Prompt.

Then enter these two commands:

sc stop "wallpaper engine service"
sc delete "wallpaper engine service"

If it still automatically starts now then it must be due to some obscure reason that I'm not even aware of.

[Firesheart]

oh boy.... aren't we gonna have fun with this....
Startup is, has, and still is disabled in settings.
The command lines... I got a interesting error.... the service does not exist. I find this very interesting. I think this may be leaning towards a obscure reason? After this post I will be restarting my PC and see if it still persists. After all soon as i mention something murphy's law has it that everything would work splendid from then on so IDK...
(the setting for wallpaper engine
https://drive.google.com/file/d/1aahs_lJBUO8Bo5eT_LLORVUUDn3Kb1Ij/view?usp=sharing
(command prompt in Admin
https://drive.google.com/file/d/1aF_t8SgqzwO9xgqwW1nJSRjfPptMqTxF/view?usp=sharing

[Biohazard]

Originally posted by Sapphire (NKM01)(Moving):

Startup is, has, and still is disabled in settings.

If you turn this setting on and off again then it might help fix the issue if it was coming from Wallpaper Engine failing to properly unregister itself from automatically starting. However due to the error you are getting, it seems the service has been removed already too. The only things Wallpaper Engine can do are this service and the entry in the task manager, but it looks like both are gone.

In general there is no simple way to find out what is starting a program that I know of, but you can always close it from the task manager and delete it. Then whatever is doing this won't find it anymore.

[Firesheart]

I honestly think my PC has a mind of its own or that its possessed or something along those lines... Cause wallpaper engine still started up with windows.
manually closed it.... oh wait... I was going to do a screenshot of the other error. whoops. forgot to check if that also still occurred as well. oof me. I'll do that next time

[Firesheart]

Originally posted by Biohazard:

Originally posted by Sapphire (NKM01)(Moving):

Startup is, has, and still is disabled in settings.

If you turn this setting on and off again then it might help fix the issue if it was coming from Wallpaper Engine failing to properly unregister itself from automatically starting. However due to the error you are getting, it seems the service has been removed already too. The only things Wallpaper Engine can do are this service and the entry in the task manager, but it looks like both are gone.

In general there is no simple way to find out what is starting a program that I know of, but you can always close it from the task manager and delete it. Then whatever is doing this won't find it anymore.

hmmm... kay. I'll go to through those steps again. I'll probably uninstall wall paper, do a restart, then install it again. though thats gonna be time consuming with my slow bandwidth that I have, cause IDK what exactly I'd be looking for in task manager, as all I see is the background wallpaper engine by itself, but assuming, if a program is starting it, a restart without the wallpaper should stop it... hopefully.

[Firesheart]

... I think I found the culprit...

Darn advanced system care startup manager may have been starting it, though it shouldn't do so.... not exactly anyways. So yeah... I'll try another restart here in a bit and see if now this fixes the issue...

https://drive.google.com/file/d/1h_q05QLHkS8IW_srmpexkDy5FsG7rpZ4/view?usp=sharing

[Firesheart]

okay. Issue seems to be resolved now. thanks for thy help.