[BUG]: Running autostart from elevated terminal still doesn't have privileges #707

Closed
opened 2026-01-05 14:52:29 +01:00 by adam · 1 comment
Owner

Originally created by @27labs on GitHub (Dec 1, 2025).

Summary

When restarting after running komorebi enable-autostart from an admin terminal, the program still fails to tile the windows of elevated executables.

Version Information

OS Name: Microsoft Windows 11 Education
OS Version: 10.0.26200 N/A Build 26200

komorebic 0.1.38
tag:v0.1.38
commit_hash:ffa76ea2
build_time:2025-09-13 18:40:25 +00:00
build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc

Komorebi Configuration

{
  "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.38/schema.json",
  "app_specific_configuration_path": "$Env:USERPROFILE/applications.json",
  "window_hiding_behaviour": "Cloak",
  "cross_monitor_move_behaviour": "Insert",
  "default_workspace_padding": 3,
  "default_container_padding": 3,
  "border": false,
  "border_width": 3,
  "border_offset": -1,
  "theme": {
    "palette": "Base16",
    "name": "Ashes",
    "unfocused_border": "Base03",
    "bar_accent": "Base0D"
  },
  "monitors": [
    {
      "workspaces": [
        {
          "name": "Main",
          "layout": "BSP"
        }
      ]
    }
  ]
}

Hotkey Configuration

Configuration done through Power Toys Keyboard Manager.

whkd is not installed.

Output of komorebic check

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Sam

Looking for configuration files in C:\Users\Sam

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\Sam\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Originally created by @27labs on GitHub (Dec 1, 2025). ### Summary When restarting after running `komorebi enable-autostart` from an admin terminal, the program still fails to tile the windows of elevated executables. ### Version Information OS Name: Microsoft Windows 11 Education OS Version: 10.0.26200 N/A Build 26200 komorebic 0.1.38 tag:v0.1.38 commit_hash:ffa76ea2 build_time:2025-09-13 18:40:25 +00:00 build_env:rustc 1.89.0 (29483883e 2025-08-04),stable-x86_64-pc-windows-msvc ### Komorebi Configuration ```json { "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.38/schema.json", "app_specific_configuration_path": "$Env:USERPROFILE/applications.json", "window_hiding_behaviour": "Cloak", "cross_monitor_move_behaviour": "Insert", "default_workspace_padding": 3, "default_container_padding": 3, "border": false, "border_width": 3, "border_offset": -1, "theme": { "palette": "Base16", "name": "Ashes", "unfocused_border": "Base03", "bar_accent": "Base0D" }, "monitors": [ { "workspaces": [ { "name": "Main", "layout": "BSP" } ] } ] } ``` ### Hotkey Configuration ```shell Configuration done through Power Toys Keyboard Manager. whkd is not installed. ``` ### Output of komorebic check ```shell No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Sam Looking for configuration files in C:\Users\Sam Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\Sam\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag ```
adam added the bug label 2026-01-05 14:52:29 +01:00
adam closed this issue 2026-01-05 14:52:29 +01:00
Author
Owner

@LGUG2Z commented on GitHub (Dec 16, 2025):

There is no support for auto-starting as an Administrator user and the docs don't make any claim that the enable-autostart command supports this use case

shell:startup, which komorebic enable-autostart uses under the hood, is explicitly scoped to the user running the command

I'm not against someone opening a PR to add support for enabling autostart as admin through other means, but I'm closing this because it's not a bug either in implementation or documentation

@LGUG2Z commented on GitHub (Dec 16, 2025): There is no support for auto-starting as an Administrator user and the docs don't make any claim that the `enable-autostart` command supports this use case `shell:startup`, which `komorebic enable-autostart` uses under the hood, is explicitly scoped to the user running the command I'm not against someone opening a PR to add support for enabling autostart as admin through other means, but I'm closing this because it's not a bug either in implementation or documentation
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#707