-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Terminal does not start -> errors in console and GUI (Dialog with "Wrong parameter") #14368
Comments
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 |
Hi there! |
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. |
The Feedback Hub is deactivated on my PC. I have the following findings for both users:
It seems to have to do with the rights settings. The assigned groups (administrators, users) are not enough. |
Do NOT mess with I'm curious if the You_ should be able to do a |
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:
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:
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. |
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:
Admin:
Normal user or Admin: Starting from
→ Dialog: "Falscher Parameter" (= Wrong parameter)
I have done a Windows 10 21H2 inplace upgrade and reinstalled Windows Terminal afterwards. Did not help.
The text was updated successfully, but these errors were encountered: