Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Startup apps don't start until logging off and on

Solved. (See my answer.)

I have a couple of startup apps using the desktop bridge. In the past they used to work fine. Now, probably after some Windows update, after a reboot they don't start when I first log on, and don't even appear in the startup tab in Task Manager. After I log off and on again, they immediately start, and also appear in the task manager.

More Info

They all use desktop:Extension Category="windows.startupTask". And in sign-in options I have "use my sign-in info to automatically..." turned off.

EDIT

The issue resolved itself after the last Windows update July 2019.

EDIT 2

Spoke too soon. The problem is back. And it doesn't (always?) resolve itself after logging off and on. And it seems like after a couple of minutes (much more than the 10 seconds of startup delay) they do (sometimes?) appear in the startup list (but perhaps only after I start them manually?).

like image 660
ispiro Avatar asked Jul 08 '19 13:07

ispiro


People also ask

Why are my apps not opening on startup?

On most Windows computers, you can access the Task Manager by pressing Ctrl+Shift+Esc, then clicking the Startup tab. Select any program in the list and click the Disable button if you don't want it to run on startup.

How do you fix apps that open on startup?

Go to Settings > Apps > Startup to view a list of all apps that can start up automatically and determine which should be disabled.

Does disabling a startup app mean you can't run it?

As a general rule, it's safe to remove any startup program. If a program starts automatically, it usually provides a service that works best if it's always running, such as an antivirus program. Or, the software may be necessary to access special hardware features, such as proprietary printer software.


1 Answers

Isolating the cause was difficult because the problem seemed to manifest itself in a random manner. Sometimes solving itself, sometimes not...

The reason was that it was caused by a semi-external reason. I had an application that was registered as a startup app but wasn't "installed". It was still in development and was running from Visual Studio. And its drive was not available immediately when logging on. As soon as that drive would become available, that and the other startup apps would be added to the startup list.

like image 143
ispiro Avatar answered Oct 30 '22 14:10

ispiro