Dominik Gauss

I'm experiencing this, too. Though I'm starting wt from task scheduler on login. I'm using `%LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe -w _quake pwsh -nologo -window minimized -NoExit -Command "& { . $env:OneDrive\Dokumente\PowerShell\profile.ps1 }"` to...

My observations: - The task option "hidden" doesn't work - "-windowstyle hidden" does work if I supply it as argument to pwsh like `wt -w _quake pwsh -nologo -windowstyle hidden...

Not much luck over here. If I do it this way I do get a running terminal - but it is CMD not pwsh. It looks like an instance of...

Antonio's comment about using a stock profile gave me something to think about. The stock profile is basically just this: `"guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": true, "name": "PowerShell", "source": "Windows.Terminal.PowershellCore"` As Antonio...

I was about to write a lengthy reply and report what I experienced in the last two hours of testing when I apparently stumbled over the solution: The value following...

@DHowett with the correct and case-sensitive spelling of the profile I'm quite happy how it now works as I want it to. One question came up though: This https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=windows doesn't...