Manage apps to start up with Windows?

[boxfoot]

Hi,

I'm not sure how this would work, but would love if we could think of a way for scoop to manage or support automatically starting programs with Windows. From what I've seen, many apps that usually manage this on their own (like Slack, Keepass, etc.) don't seem to do it properly when installed via scoop (maybe their usual registry writing isn't working or something.)

It's not too hard to manually open the shell:startup folder to add shortcuts to scoop apps, but can be a bit tedious to use window's UI. Also, the April Windows 10 update just erased that folder for me and all the links I had set up, which was frustrating.

It would be great if there could be a solution like teaching scoop to start certain shims on start-up, or having a scoop windows-start command (needs a better name) that would start all apps with a given flag. I'm sure there are multiple ways to think about this, and am curious if other folks would even find it useful...

[Calinou]

We could borrow the terminology used by systemd services. For instance, this would register an app to be started automatically:

scoop enable <app>

And to unregister it:

scoop disable <app>

There is one problem though: manifests currently do not declare a "main" executable, which would be required in case there are multiple executables added to the PATH or multiple shortcuts added to the Start Menu.

[chawyehsu]

Linking the shortcut in Scoop Apps to shell:startup if one needs start up, maybe a choice.

[brunovieira97]

On the command to be used, I'd say enable and disable aren't the best ones. This could easily mean enabling or disabling an app entirely.

Probably, by using a list maintained by Scoop itself (on a local file of some sort), having a command like:

scoop startup [ list | add | remove | cleanup ]

There is one problem though: manifests currently do not declare a "main" executable, which would be required in case there are multiple executables added to the PATH or multiple shortcuts added to the Start Menu.

Maybe with a new - optional - property on manifests called mainFile, that would be used when passing the app name to scoop startup add <app>?

When there is no mainFile specified on the manifest, maybe presenting an error and proposing the user:

• Editing the scoop-startup file manually
• Typing the mainFile path (from the app's root folder perspective, with relative path)

[Midnex]

Hoping something has come of this, or is planned. There are many apps that do not start as services that should be running all the time. Such as Teamviewer or Microsoft Teams. Other apps such as Everything that start their own services, and the app itself doesn't need to be started.

[AucaCoyan]

For the people that come here from google I did a workaround:

1. Go to this folder in your pc

C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Scoop Apps

and there are a shortcut for every scoop app that has some Start Menu component.

2. Press Win + R to run a command and write

shell:startup

this opens a folder that windows excecutes every time it loads the desktop.

3. Copy the .lnk files you want to startup with windows

[sylph520]

Totally agree, it would be nice to manage the auto startup behaviors of scoop installed app like systemd of Linux. Looking forward to the progress of this issue. 😊