-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
"The parameter is incorrect" on First Run #4095
Comments
@Blizzardo1 Any chance you're using the UTF-8 system code page? The symptoms sound similar to #3039 |
Yikes, that's not what I was hoping for. @Blizzardo1 Could you try repro'ing this with the Feedback hub? That'll give us more detailed diagnostics (hopefully). /feedback |
I had submitted a feedback request yesterday. Hopefully it landed safely :) |
I have hit that today as well. |
same problem here |
And the both of you are also not using UTF-8 ACP? |
System: Windows 10 Enterprise 1903 (Build 18362.592) Just upgraded Windows Terminal from 0.7.3382.0 to 0.8.10261.0 with chocolatey. Problem still exists. Removing and Reinstalling did not fix the problem. Thanks for looking into it. |
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. |
I do not. |
I also have run into this issue. The problem started after I enabled my Administrator account and switched over to use it. I wanted to use Terminal, so I installed it from the Store, thinking it would then entitle me to Launch. It seemed to re-install, and worked fine. When I switch back to the only User account on my PC, I run into the "The parameter is incorrect" error. Note: if I switch to my Administrator account, Terminal opens without any error. I have attempted a number of uninstall/re-install variations between the two accounts, but it seems no matter what I try, my Administrator account can open Terminal, and my User account cannot. |
I have only one account that too is Administrator, still it doesn't work. |
I too have been having this exact issue for months Win AD joined machine Submitted feedback. Link is https://aka.ms/AA8a8hw |
Unfortunately, we haven't really been able to reproduce this. Is it still happening for you folks? |
Still happening for me, but doesn't seem to be limited to only Windows Terminal. I installed Ubuntu 20.04 for WSL and get the same issue. I found one 'solution' which is letting me use Terminal - that being to move the entire install folder out of the WindowsApps folder and into C:\Terminal (any other folder location works, and this fixes Ubuntu as well). I was going to do a "Upgrade in Place" style repair, but couldn't select the choice to leave all of my programs and files in place, so I decided not to go any further. I saw reports from other forums that this solution worked. I'm mostly just ignoring it for now, as I have the work-around, and I plan on re-formatting this PC once I purchase a new one later this summer. |
Dear @DHowett , |
Thanks for the info. I unfortunately don't think there's anything we can do about it, but I'll leave you with two points.
|
I had this same problem after going through updating WSL1 to WSL2. I had to redo that a couple times as I didn't reboot when I should have but eventually got it upgraded. After that though this problem occurred and I can't open my newly downloaded Windows Terminal. I ran "sfc /scannow" which found some corrupt files and fixed them. I could then open Windows Terminal. However, after closing the terminal I get the same problem and "sfc /scannow" doesn't pick up anything. I can run the Ubuntu and Kali apps just fine by clicking on the apps from the start menu. Windows Terminal would be really useful to use right now though. |
I reinstalled my workstation and to my amazement this issue no longer exists. I think my old instance had some anomaly with certain app packages, and Terminal was one of them. Funny, yet strange. Through these harsh times, I thank everyone that tried to help anyone who experienced this issue. May the 8-bit Gods carry the 1 to forever return SUCCESS. |
Fixed the problem moving terminal installation folder. Just change the directory like say %USERPROFILE%\Terminal folder and Voyla. It looks like a security issue in Program Files\WindowsApps directory. Another behavior is the icon that disappears from a shortcut created in desktop or toolbar. There is no need for running sfc /scannow. Sorry for my poor English. Cheers. |
I have this issue as well.
I looked into this & discovered something strange. For some reason my For me the group
I'm going to try completely removing the folder, & let the OS recreate it, hopefully with the proper ownership & permissions. I'll post the results here when I finish |
WATCH OUT! I don't think the OS will recreate that! touching that could be VERY BAD |
I'm already listsed as the owner of it, so the worse that could happen is that the OS does nothing, unlikely, & I copy it back, maybe that alone will fix the permission issues. |
Intereswting thing to note. Deleting the directory was not possible but the reason seems very odd. There were 4 font TTF files in the Windows Terminal folder that were said to be in use by the system. Restarting into safe made was still unable to because the same files were still |
These folders have special ACLs on them that aren't properly displayed by the UI or backed up by I lost an entire day trying to "fix" a broken |
Mine was already permission abnormal. I did notice that on my other system I cannot even open the folder with admin permissions. Putting it back everything except the Store is back, I will do a reset sometime later today or tomorrow & hopefully the Microsoft Store will come back, but as it is it's essentially back to the way it was before so not much has changed. The error it gives me when I try to run the store is about some DLL files not being found, so I'm hopeful that it will load them with a restart since one is in the |
How did you get it fixed? |
I vaguely recall this thread: #13509 (comment) |
I've had many bad experiences with "In-Place Upgrades" so that's a last-ditch for me, but it's at least something if nothing else works. It sounds like, from that thread, that it's saying that having any sort of altered permissions will cause big problems, but mine were already like that... & I could even install other apps fine, but the terminal & other terminal apps like terminus & one other I tried but I can't remember would install but not start. |
So I was able to get everything back to the way it was before I moved the WindowsApps folder by using the PowerShell install method for the Windows Store App. Unfortunately it didn't work with the folder removed though so I had to manually put it back 1st & the folder still has weird permissions. Looking into things it seems like creating a new account may do the same to fix it as an in-place upgrade less destructively. |
Environment
Steps to reproduce
Install from Microsoft Store or download from Releases Tab.
Open Program
Expected behavior
First Run default profile loaded for configuring
Actual behavior
Upon opening program, the following error happens:
[C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.7.3451.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe]
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.7.3451.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
The parameter is incorrect.
This doesn't happen on my laptop which is weird. Other UWP(style) programs do run like the Camera App, Calculator, etc. It's just this particular program that doesn't like my copy of Windows.
The text was updated successfully, but these errors were encountered: