startOnUserLogin isn't working anymore (on 1.12, Windows 10) #16659

Closed
opened 2026-01-31 05:18:49 +00:00 by claunia · 11 comments
Owner

Originally created by @MS-Manikandan on GitHub (Feb 5, 2022).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version

1.12.10334.0

Windows build number

10.0.19044 .0

Other Software

No

Steps to reproduce

I have recently upgraded windows terminal Version: 1.12.10334.0

Expected Behavior

If startOnUserLogin key was set to true in settings.json file and Launch on machine startup was toggled on in windows terminal/terminal settings, it should launch on startup.

Actual Behavior

After updating to windows terminal latest Version: 1.12.10334.0, it doesn't launches on startup, windows terminal wasn't found on taskmanager startup programs and windows settings startup apps, even though startOnUserLogin set to true, in the settings.json file.
image
image

Originally created by @MS-Manikandan on GitHub (Feb 5, 2022). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version 1.12.10334.0 ### Windows build number 10.0.19044 .0 ### Other Software No ### Steps to reproduce I have recently upgraded windows terminal Version: 1.12.10334.0 ### Expected Behavior If startOnUserLogin key was set to true in settings.json file and Launch on machine startup was toggled on in windows terminal/terminal settings, it should launch on startup. ### Actual Behavior After updating to windows terminal latest Version: 1.12.10334.0, it doesn't launches on startup, windows terminal wasn't found on taskmanager startup programs and windows settings startup apps, even though startOnUserLogin set to true, in the settings.json file. ![image](https://user-images.githubusercontent.com/42301172/152631768-59c69a54-72fb-4fc4-b029-abb94086afdc.png) ![image](https://user-images.githubusercontent.com/42301172/152631810-cd5b0043-e44b-41a4-8dd3-155ea7060cf0.png)
Author
Owner

@BrianHo888 commented on GitHub (Feb 5, 2022):

My mRemoteNG startup with a blank screen after Windows Update to 21H2. I tried to open confCons.xml but it won't load the configuration. Does anyone experience this issue and have solved this problem?

@BrianHo888 commented on GitHub (Feb 5, 2022): My mRemoteNG startup with a blank screen after Windows Update to 21H2. I tried to open confCons.xml but it won't load the configuration. Does anyone experience this issue and have solved this problem?
Author
Owner

@lino-man commented on GitHub (Feb 5, 2022):

Man, this app is so buggy, but so buggy, that u people can't imagine. It is a cyberpunk terminal. In 2024 I'll try it again.

@lino-man commented on GitHub (Feb 5, 2022): Man, this app is so buggy, but so buggy, that u people can't imagine. It is a cyberpunk terminal. In 2024 I'll try it again.
Author
Owner

@zadjii-msft commented on GitHub (Feb 6, 2022):

I suspect this has to do with the name change, but I have yet to understand why...

@zadjii-msft commented on GitHub (Feb 6, 2022): I suspect this has to do with the name change, but I have yet to understand why...
Author
Owner

@zadjii-msft commented on GitHub (Feb 10, 2022):

onecore\base\AppModel\Runtime\Src\PackagePath.hpp(144)\kernelbase.dll!00007FFFC94D6FD1: (caller: 00007FFFC94D6AEE) ReturnHr(5) tid(7458) 80073D5B The package does not have a mutable directory.
TerminalApp.dll!00007FFEE024B371: LogHr(1) tid(7458) 80070057 The parameter is incorrect.
Exception thrown at 0x00007FFFC94B230C (KernelBase.dll) in WindowsTerminal.exe: WinRT originate error - 0x80070057 : 'The parameter is incorrect.'.
Exception thrown at 0x00007FFFC94B230C in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000FEEB51D890.
Exception thrown at 0x00007FFFC94B230C in WindowsTerminal.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
D:\dev\private\OpenConsole\src\cascadia\TerminalApp\AppLogic.cpp(1023)\TerminalApp.dll!00007FFEE0919A86: (caller: 00007FFEE030BDED) LogHr(2) tid(7458) 80070057 The parameter is incorrect.
    Msg:[winrt::hresult_error: The parameter is incorrect.] [winrt::TerminalApp::implementation::AppLogic::_ApplyStartupTaskStateChange]

@zadjii-msft commented on GitHub (Feb 10, 2022): ``` onecore\base\AppModel\Runtime\Src\PackagePath.hpp(144)\kernelbase.dll!00007FFFC94D6FD1: (caller: 00007FFFC94D6AEE) ReturnHr(5) tid(7458) 80073D5B The package does not have a mutable directory. TerminalApp.dll!00007FFEE024B371: LogHr(1) tid(7458) 80070057 The parameter is incorrect. Exception thrown at 0x00007FFFC94B230C (KernelBase.dll) in WindowsTerminal.exe: WinRT originate error - 0x80070057 : 'The parameter is incorrect.'. Exception thrown at 0x00007FFFC94B230C in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000FEEB51D890. Exception thrown at 0x00007FFFC94B230C in WindowsTerminal.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000. D:\dev\private\OpenConsole\src\cascadia\TerminalApp\AppLogic.cpp(1023)\TerminalApp.dll!00007FFEE0919A86: (caller: 00007FFEE030BDED) LogHr(2) tid(7458) 80070057 The parameter is incorrect. Msg:[winrt::hresult_error: The parameter is incorrect.] [winrt::TerminalApp::implementation::AppLogic::_ApplyStartupTaskStateChange] ```
Author
Owner

@zadjii-msft commented on GitHub (Feb 11, 2022):

Well, my theory is definitely right. Definitely regressed in #12264. Just changing the DisplayName to Foo fixes this. There may be a bug in the platform for how it handles nested resources like this. I've got mail out. We'll see where that goes.

If it is a platform bug, we're in a pretty bad spot. We won't be able to localize that string in all the rest of the languages the Terminal is localized in. We could maybe move the context menu strings into the appx's resources... maybe? I'm not even sure that would work.

Hopefully it isn't.

@zadjii-msft commented on GitHub (Feb 11, 2022): Well, my theory is definitely right. Definitely regressed in #12264. Just changing the DisplayName to `Foo` fixes this. There may be a bug in the platform for how it handles nested resources like this. I've got mail out. We'll see where that goes. If it is a platform bug, we're in a pretty bad spot. We won't be able to localize that string in all the rest of the languages the Terminal is localized in. We could maybe move the context menu strings into the appx's resources... maybe? I'm not even sure that would work. Hopefully it isn't.
Author
Owner

@J-HS-L commented on GitHub (Feb 16, 2022):

Is this & #12480 resolved? Apologies in advance if I've completely missed it but;
Where is the detail outlining; [1] What the prob. was, & [2] What the fix was?

TY.

@J-HS-L commented on GitHub (Feb 16, 2022): Is this & #12480 resolved? Apologies in advance if I've completely missed it but; Where is the detail outlining; [1] What the prob. was, & [2] What the fix was? TY.
Author
Owner

@zadjii-msft commented on GitHub (Feb 16, 2022):

We just recently had to move them from being in the packages root resources file to another one elsewhere in the tree. When we made that move (from ms-resource:AppNameDev to ms-resource:TerminalApp/ContextMenu/AppNameDev, now the startup task doesn't work anymore. But everywhere else that resource (ms-resource:TerminalApp/ContextMenu/AppNameDev) is used seems to work just fine. Turns out there's a platform bug that prevents this from working as expected.

The fix in #12491 was to copy our localized resources in TerminalApp/ContextMenu up into the root resources, so we could refer to them as just ms-resource:AppNameDev again. That's a viable workaround while we work on the platform fix.

@zadjii-msft commented on GitHub (Feb 16, 2022): We just recently had to move them from being in the packages root resources file to another one elsewhere in the tree. When we made that move (from `ms-resource:AppNameDev` to `ms-resource:TerminalApp/ContextMenu/AppNameDev`, now the startup task doesn't work anymore. But everywhere else that resource (`ms-resource:TerminalApp/ContextMenu/AppNameDev`) is used seems to work just fine. Turns out there's a platform bug that prevents this from working as expected. The fix in #12491 was to copy our localized resources in `TerminalApp/ContextMenu` up into the root resources, so we could refer to them as just `ms-resource:AppNameDev` again. That's a viable workaround while we work on the platform fix.
Author
Owner

@MS-Manikandan commented on GitHub (Mar 13, 2022):

Hi, could you let us know Is this issue is fixed?, I updated to v1.12.10393.0 but still I couldn't find Terminal under startup apps on windows 10.

@MS-Manikandan commented on GitHub (Mar 13, 2022): Hi, could you let us know Is this issue is fixed?, I updated to [v1.12.10393.0](https://github.com/microsoft/terminal/releases/tag/v1.12.10393.0) but still I couldn't find Terminal under startup apps on windows 10.
Author
Owner

@zadjii-msft commented on GitHub (Mar 14, 2022):

This is fixed in #12491 but that hasn't shipped yet unfortunately. The team's been dealing with some unexpected absence over the last few weeks. We appreciate your patience while we work on pushing that out.

@zadjii-msft commented on GitHub (Mar 14, 2022): This is fixed in #12491 but that hasn't shipped yet unfortunately. The team's been dealing with some unexpected absence over the last few weeks. We appreciate your patience while we work on pushing that out.
Author
Owner

@ghost commented on GitHub (Mar 25, 2022):

:tada:This issue was addressed in #12491, which has now been successfully released as Windows Terminal v1.12.1073.🎉

Handy links:

@ghost commented on GitHub (Mar 25, 2022): :tada:This issue was addressed in #12491, which has now been successfully released as `Windows Terminal v1.12.1073`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.12.1073) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Mar 25, 2022):

:tada:This issue was addressed in #12491, which has now been successfully released as Windows Terminal Preview v1.13.1073.🎉

Handy links:

@ghost commented on GitHub (Mar 25, 2022): :tada:This issue was addressed in #12491, which has now been successfully released as `Windows Terminal Preview v1.13.1073`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.13.1073) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16659