starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal does not start -> errors in console and GUI (Dialog with "Wrong parameter") #18864

New Issue
Open
opened 2026-01-31 06:26:37 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 06:26:37 +00:00
Owner
Copy Link

Originally created by @torric on GitHub (Nov 10, 2022).

Windows Terminal version

1.15.2874.0

Windows build number

10.0.19044.2251

Other Software

No response

Steps to reproduce

I have installed Windows Terminal with winget successfully.
winget install Microsoft.WindowsTerminal

Try to start Windows Terminal from start menu or from console with wt.

Alias for app execution is set for Terminal / wt.exe.

Expected Behavior

Windows Terminal opens.

Actual Behavior

Click on Terminal in start menu -> Nothing happens

Normal user:

  • Powershell: wt 
ResourceUnavailable: Program 'wt.exe' failed to run: An error occurred trying to start process 'C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\wt.exe' with working directory 'C:\Users\<username>'. Falscher Parameter.At line:1 char:1
+ wt
+ ~~.

Admin:

  • Powershell: wt 
Fehler beim Ausführen des Programms "wt.exe": Falscher ParameterIn Zeile:1 Zeichen:1
+ wt
+ ~~.
In Zeile:1 Zeichen:1
+ wt
+ ~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Normal user or Admin: Starting from

C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\wt.exe

→ Dialog: "Falscher Parameter" (= Wrong parameter)

I have done a Windows 10 21H2 inplace upgrade and reinstalled Windows Terminal afterwards. Did not help.

Originally created by @torric on GitHub (Nov 10, 2022). ### Windows Terminal version 1.15.2874.0 ### Windows build number 10.0.19044.2251 ### Other Software _No response_ ### Steps to reproduce I have installed Windows Terminal with winget successfully. winget install Microsoft.WindowsTerminal Try to start Windows Terminal from start menu or from console with wt. Alias for app execution is set for Terminal / wt.exe. ### Expected Behavior Windows Terminal opens. ### Actual Behavior Click on Terminal in start menu -> Nothing happens Normal user: - Powershell: wt <Enter> ``` ResourceUnavailable: Program 'wt.exe' failed to run: An error occurred trying to start process 'C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\wt.exe' with working directory 'C:\Users\<username>'. Falscher Parameter.At line:1 char:1 + wt + ~~. ``` Admin: - Powershell: wt <Enter> ``` Fehler beim Ausführen des Programms "wt.exe": Falscher ParameterIn Zeile:1 Zeichen:1 + wt + ~~. In Zeile:1 Zeichen:1 + wt + ~~ + CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException + FullyQualifiedErrorId : NativeCommandFailed ``` Normal user or Admin: Starting from ``` C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\wt.exe ``` → Dialog: "Falscher Parameter" (= Wrong parameter) I have done a Windows 10 21H2 inplace upgrade and reinstalled Windows Terminal afterwards. Did not help.
claunia commented 2026-01-31 06:26:38 +00:00
Author
Owner
Copy Link

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

Hmm. You're on 1.15.2874, so you've already got the fix for #14104.

We might need an app launch trace, to forward to the MSIX activation folks to take a look. I don't recall what that path is off the top of my head, something like "app activation" (instead of "terminal", which the bot is about to recommend): /feedback

@zadjii-msft commented on GitHub (Nov 11, 2022): Hmm. You're on 1.15.2874, so you've already got the fix for #14104. We might need an app launch trace, to forward to the MSIX activation folks to take a look. I don't recall what that path is off the top of my head, something like "app activation" (instead of "terminal", which the bot is about to recommend): /feedback
claunia commented 2026-01-31 06:26:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Nov 11, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 06:26:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 15, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 15, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 06:26:39 +00:00
Author
Owner
Copy Link

@torric commented on GitHub (Nov 20, 2022):

The Feedback Hub is deactivated on my PC.
I can start the Windows Terminal app when I assign read and execution right to the folder "C:\Program Files\WindowsApps" for the specific administrator and non-administrator user and inherit them to sub folders.

I have the following findings for both users:

  1. Starting link "Terminal" from start menu does not work.
  2. Starting from start menu by typing "wt" works.
  3. Starting from cmd or PowerShell with "wt" does not work.
  4. Starting from an alternative file explorer by "wt" works.

It seems to have to do with the rights settings. The assigned groups (administrators, users) are not enough.

@torric commented on GitHub (Nov 20, 2022): The Feedback Hub is deactivated on my PC. I can start the Windows Terminal app when I assign read and execution right to the folder "C:\Program Files\WindowsApps" for the specific administrator and non-administrator user and inherit them to sub folders. I have the following findings for both users: 1. Starting link "Terminal" from start menu does not work. 2. Starting from start menu by typing "wt" works. 3. Starting from cmd or PowerShell with "wt" does not work. 4. Starting from an alternative file explorer by "wt" works. It seems to have to do with the rights settings. The assigned groups (administrators, users) are not enough.
claunia commented 2026-01-31 06:26:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 21, 2022):

when I assign read and execution right to the folder "C:\Program Files\WindowsApps

Do NOT mess with WindowsApps. Last time someone was messing with those on this repo, they had to reinstall Windows. Watch out.

I'm curious if the wt that's being launched is the same thing. I bet in one case, you're triggering the app execution alias, and in the other, you're running the actual binary (from WindowsApps, which should not be run directly).

You_ should be able to do a where wt in Command Prompt, but idk if you can do the same thing effectively from the Run Dialog, without somehow invoking CMD itself.

@zadjii-msft commented on GitHub (Nov 21, 2022): > when I assign read and execution right to the folder "C:\Program Files\WindowsApps Do NOT mess with `WindowsApps`. Last time someone was messing with those on this repo, they had to reinstall Windows. Watch out. I'm curious if the `wt` that's being launched is the same thing. I bet in one case, you're triggering the app execution alias, and in the other, you're running the actual binary (from WindowsApps, which _should not be run directly_). You_ should be able to do a `where wt` in Command Prompt, but idk if you can do the same thing effectively from the Run Dialog, without somehow invoking CMD itself.
claunia commented 2026-01-31 06:26:40 +00:00
Author
Owner
Copy Link

@goodbey857 commented on GitHub (Dec 22, 2023):

I had the same question, but now I solved it! The reason is that I moved the directory "%username%/AppData/LocalLow" to "D:/AppData/LocalLow" using a tool named "freemove" to save space on the C disk. This tool creates a symbolic link on "%username%/AppData/LocalLow" pointing to "D:/AppData/LocalLow." When I deleted the symbolic link, everything was repaired.

@goodbey857 commented on GitHub (Dec 22, 2023): I had the same question, but now I solved it! The reason is that I moved the directory "%username%/AppData/LocalLow" to "D:/AppData/LocalLow" using a tool named "freemove" to save space on the C disk. This tool creates a symbolic link on "%username%/AppData/LocalLow" pointing to "D:/AppData/LocalLow." When I deleted the symbolic link, everything was repaired.
claunia commented 2026-01-31 06:26:40 +00:00
Author
Owner
Copy Link

@xxnuo commented on GitHub (Jan 7, 2024):

I had the same question, but now I solved it! The reason is that I moved the directory "%username%/AppData/LocalLow" to "D:/AppData/LocalLow" using a tool named "freemove" to save space on the C disk. This tool creates a symbolic link on "%username%/AppData/LocalLow" pointing to "D:/AppData/LocalLow." When I deleted the symbolic link, everything was repaired.

I wish I had seen your reply this morning. I encountered the same situation. Here is what happened:

I installed a fresh copy of Windows 10 22H2 19045.3803 (I also tried LTSC 2021). I wanted to move the %APPDATA% directory to another disk where I store my personal data, so I created a symbolic link in safe mode:

MOVE C:\User\USERNAME\AppData\Roaming D:\Roaming
MKLINK /D C:\User\USERNAME\AppData\Roaming D:\Roaming

After rebooting, all the normal Win32 exe applications, pre-installed UWP applications, and Portable format Windows Terminal(wt) downloaded from the Release section worked fine.

When I used winget (I also tried msstore, with the same result) to install wt and nanazip, after the installation, launching wt from the Start menu showed an "Invalid parameter" error, and the same happened with nanazip. I noticed that they are both Win32 UWP Desktop Bridge applications.

So I started looking for the cause and restored the symbolic link directory:

RMDIR C:\User\USERNAME\AppData\Roaming
ROBOCOPY D:\Roaming C:\User\USERNAME\AppData\Roaming /MIR

After rebooting, everything was back to normal.

Therefore, I suspect that this issue may be related to a bug in the Desktop Bridge file API because other types of applications can open normally. I don't know where to report this issue, so I opened this issue hoping that Microsoft developers will take notice of this bug.

If someone encounters the same problem, I hope they can also take note of it and not spend as much time troubleshooting as I did. At first, I even thought it was a problem with the LTSC system, so I even reinstalled the system.

@xxnuo commented on GitHub (Jan 7, 2024): > I had the same question, but now I solved it! The reason is that I moved the directory "%username%/AppData/LocalLow" to "D:/AppData/LocalLow" using a tool named "freemove" to save space on the C disk. This tool creates a symbolic link on "%username%/AppData/LocalLow" pointing to "D:/AppData/LocalLow." When I deleted the symbolic link, everything was repaired. I wish I had seen your reply this morning. I encountered the same situation. Here is what happened: I installed a fresh copy of Windows 10 22H2 19045.3803 (I also tried LTSC 2021). I wanted to move the %APPDATA% directory to another disk where I store my personal data, so I created a symbolic link in safe mode: > > MOVE C:\User\USERNAME\AppData\Roaming D:\Roaming > MKLINK /D C:\User\USERNAME\AppData\Roaming D:\Roaming > After rebooting, all the normal Win32 exe applications, pre-installed UWP applications, and Portable format Windows Terminal(wt) downloaded from the Release section worked fine. When I used winget (I also tried msstore, with the same result) to install wt and nanazip, after the installation, launching wt from the Start menu showed an "Invalid parameter" error, and the same happened with nanazip. I noticed that they are both Win32 UWP Desktop Bridge applications. So I started looking for the cause and restored the symbolic link directory: > > RMDIR C:\User\USERNAME\AppData\Roaming > ROBOCOPY D:\Roaming C:\User\USERNAME\AppData\Roaming /MIR > After rebooting, everything was back to normal. Therefore, I suspect that this issue may be related to a bug in the Desktop Bridge file API because other types of applications can open normally. I don't know where to report this issue, so I opened this issue hoping that Microsoft developers will take notice of this bug. If someone encounters the same problem, I hope they can also take note of it and not spend as much time troubleshooting as I did. At first, I even thought it was a problem with the LTSC system, so I even reinstalled the system.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Culprit-Centennial Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#18864
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?