Skip to content

Conversation

@SammCheese
Copy link

@SammCheese SammCheese commented May 30, 2025

I've noticed that the startup can sometimes be a bit slow.
So i have decided to try to speed the autostart up a bit, by adding the startup entry in the Registry instead of using shell:startup.

The PR also:

  • Ensures there will be no double autostart entries from the old method
  • Ensures that on disabling autostart, old startup entries will also be remove

(old startup entries referring to the shell:startup method)

The Tests show an average startup improvement time of 6s across 3 runs each, despite strong variations and inconsistencies due to the nature of windows' boot process.

29,3s p. average for shell:startup
22,9s p. average for registry

EDIT: the registry autostart is now locked behind the --registry flag.
By default, shell:startup is used and will (when enabled) also attempt to remove the komorebi autostart registry entry if it exists.
When the --registry flag is used, it will first try to remove the shell:startup shortcut (if it exists) and then create the appropriate registry startup entry.

@SammCheese SammCheese force-pushed the registry-autostart branch from cfe20c4 to 284a6bb Compare May 30, 2025 16:49
@SammCheese SammCheese marked this pull request as ready for review May 30, 2025 16:58
Use shell:startup by default instead of registry, with the option to autostart via registry using
the --registry flag
@RoakStatic
Copy link

The speed of the Autostart feature was one of the primary factors that I almost dropped Komorebi, but I figured I owed it to myself to see if I could improve on it seeing as similar applications such as SeelenUI are already running by the time you land on your desktop after logging in.

I've been able to get Komorebi to load by least 5 seconds after login by creating a Scheduled Task to run the komorebic-no-console.exe start --bar command.

  1. Open Task Scheduler and create a new folder named Komorebi
  2. Create a new task within that folder and call it Komoebri UI Service
    2.a) Select Run with highest privileges
  3. Under the Triggers tab select New, then set Begin the task: to At log on of any user
  4. Under the Actions tab select New, and do the following;
    4.a) Action: Start a program
    4.b) Program/script: komorebic-no-console.exe
    4.c) Add arguments (optional): start --bar
    4.d) Start in (optional): C:\Program Files\komorebi\bin

@SammCheese
Copy link
Author

The speed of the Autostart feature was one of the primary factors that I almost dropped Komorebi, but I figured I owed it to myself to see if I could improve on it seeing as similar applications such as SeelenUI are already running by the time you land on your desktop after logging in.

I've been able to get Komorebi to load by least 5 seconds after login by creating a Scheduled Task to run the komorebic-no-console.exe start --bar command.

1. Open Task Scheduler and create a new folder named **_Komorebi_**

2. Create a new task within that folder and call it **_Komoebri UI Service_**
   2.a) Select **Run with highest privileges**

3. Under the **Triggers** tab select **New**, then set **Begin the task:** to **_At log on of any user_**

4. Under the **Actions** tab select **New**, and do the following;
   4.a) Action: **_Start a program_**
   4.b) Program/script: **_komorebic-no-console.exe_**
   4.c) Add arguments (optional): **_start --bar_**
   4.d) Start in (optional): **_C:\Program Files\komorebi\bin_**

I did consider Task Scheduler for this PR as its very very quick to execute its tasks, but i felt like that might be a bit too invasive for users. Thats why i opted into the windows-recommended way of starting programs via registry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants