Can't disable startup

[jacobrreed]

Windows Terminal version

1.21.3231.0

Windows build number

10.0.26100.0

Other Software

Docker (disabled on startup, does not launch)
AthenaOS WSL

Steps to reproduce

1. Install WSL (any distro, currently using AthenaOS WSL)
2. Install Windows Terminal
3. Install Docker Desktop
4. Disable docker on startup
5. Disable Launch on Machine startup in Windows Terminal settings
   
6. Check shell:startup
   
7. Check shell:Common Startup
   
8. Check task manager startup apps
   
9. Check Windows Settings App -> Apps -> Startup (NOTICE HERE, Terminal is checked on and greyed out so it can't be disabled??)
   
10. On Fresh windows start, terminal auto opens and launches WSL

Things I have tried to alleviate:

1. I have disabled WSL, which still causes Terminal to launch at startup, but will just launch with a WSL error because WSL is not running
2. I have turned off showing recent files in explorer
3. I have ensured Linux subsystem folders are not expanded or manually pinned to quick start
4. Ensured docker desktop with WSL support does not run at startup
5. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal

Expected Behavior

I expect Windows Terminal to not autostart when computer starts, I also expect to be able to disable Windows Terminal from Settings App -> Apps -> Startup, currently it is enabled and greyed out with no way to disable it.

Actual Behavior

Windows terminal launches at startup everytime.

[jacobrreed]

To note from above, this will fix the issue:

5. https://www.winhelponline.com/blog/wp-content/uploads/2023/06/store_appx_startup_fix.zip registry hack which allows me to actually change Startup Apps under Settings App to disable Windows Terminal

Although I don't understand why this is necessary

[WhatsACloud]

Hmm that seems very odd. I followed the replication steps but I couldn't reproduce the bug. I suspect there might be something else at play. Could you answer the following questions so I can diagnose this issue further?

1. Have you tried uninstalling and reinstalling Windows Terminal to see if the bug still occurs? (a bit simplistic, but it might work. If you have loads of settings tweaked, I believe you can export it by saving the settings.json somewhere.)
2. when did this bug start occurring? Right after downloading it, or did it randomly start one morning?