starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows 11 gets a bizarre "parameter error" and fails to start [Windows11 出现离奇的“参数错误”无法启动] #23419

New Issue
Open
opened 2026-01-31 08:41:41 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:41:41 +00:00
Owner
Copy Link

Originally created by @jsrcode on GitHub (Jul 7, 2025).

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.4351

Other Software

PowerShell 7.5.2

Steps to reproduce

------------------------- English feedback-------------------------
The issue first occurred after installing PowerShell 7.5.2 and subsequently uninstalling PowerShell 7.5.2 was useless
Trying to uninstall and reinstall Windows Terminal had no effect
A search on Bing found https://answers.microsoft.com/zh-hans/windows/forum/all/windows11 Pro type/464c57b0-69c7-4696-ae6f-ea8289bfff0a this solution
Replace WindowsTerminal with the initial configuration file it provides
Then try to install PowerShell 7.5.2 again No error but I don't see the PowerShell 7 configuration file that automatically appears in Windows Terminal as said on the Internet Try to add it manually Edit the json file After saving, the test is normal No error occurred Just in case I tried to restart the computer Restart Windows Terminal did not get any error
Then, a day later, there was a "parameter error" error that had not been modified in the Windows Terminal configuration
Fix within the settings Resume use
Then half a day later it was wrong again, again with no modification
Try to fix within settings useless and reset within settings to resume use
Available for the time being, but frequent errors seriously affect the use hopefully it can be fixed
My personal opinion is that the data directory (C:\Users{username}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState) permission configuration related issues
Considering adding a custom data catalog feature might alleviate this error
I think it's a bug caused by windows' wrong permission control design or a flaw in the Packages directory
-------------------------中文反馈-------------------------
第一次出现该问题是在安装PowerShell 7.5.2之后 随后卸载PowerShell 7.5.2 无用
尝试卸载重新安装Windows Terminal 无效果
在Bing搜索 找到了https://answers.microsoft.com/zh-hans/windows/forum/all/windows11%e4%b8%93%e4%b8%9a%e7%89%88%e6%89%93/464c57b0-69c7-4696-ae6f-ea8289bfff0a 这个解决方案
使用其提供的初始配置文件替换WindowsTerminal后恢复使用
然后重新尝试安装PowerShell 7.5.2 没有出错 但是没有看到网上所说的自动在Windows Terminal内出现PowerShell7配置文件 尝试手动添加 编辑json文件 保存后测试正常 未出现报错 为了以防万一尝试重启计算机 重启Windows Terminal 均未出现错误
然后在一天后又出现了"参数错误"报错 这期间没有修改过Windows Terminal配置
在设置内修复 恢复使用
然后半天后再次出错 同样无修改
尝试设置内修复 无用 在设置内重置 恢复使用
暂时可用 但是频繁出错严重影响使用 希望可以修复
个人观点认为是数据目录(C:\Users{用户名}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState)权限配置相关问题
是否考虑增加自定义数据目录功能 可能可以缓解这个错误
我认为这是windows对于Packages目录错误的权限控制设计或者缺陷导致的bug

Expected Behavior

No response

Actual Behavior

Error message "Parameter error" is reported.

报错"参数错误"

Originally created by @jsrcode on GitHub (Jul 7, 2025). ### Windows Terminal version 1.22.11141.0 ### Windows build number 10.0.26100.4351 ### Other Software PowerShell 7.5.2 ### Steps to reproduce ------------------------- English feedback------------------------- The issue first occurred after installing PowerShell 7.5.2 and subsequently uninstalling PowerShell 7.5.2 was useless Trying to uninstall and reinstall Windows Terminal had no effect A search on Bing found [https://answers.microsoft.com/zh-hans/windows/forum/all/windows11 Pro type/464c57b0-69c7-4696-ae6f-ea8289bfff0a](https://answers.microsoft.com/zh-hans/windows/forum/all/windows11%e4%b8%93%e4%b8%9a%e7%89%88%e6%89%93/464c57b0-69c7-4696-ae6f-ea8289bfff0a) this solution Replace WindowsTerminal with the initial configuration file it provides Then try to install PowerShell 7.5.2 again No error but I don't see the PowerShell 7 configuration file that automatically appears in Windows Terminal as said on the Internet Try to add it manually Edit the json file After saving, the test is normal No error occurred Just in case I tried to restart the computer Restart Windows Terminal did not get any error Then, a day later, there was a "parameter error" error that had not been modified in the Windows Terminal configuration Fix within the settings Resume use Then half a day later it was wrong again, again with no modification Try to fix within settings useless and reset within settings to resume use Available for the time being, but frequent errors seriously affect the use hopefully it can be fixed My personal opinion is that the data directory (C:\Users\{username}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState) permission configuration related issues Considering adding a custom data catalog feature might alleviate this error I think it's a bug caused by windows' wrong permission control design or a flaw in the Packages directory -------------------------中文反馈------------------------- 第一次出现该问题是在安装PowerShell 7.5.2之后 随后卸载PowerShell 7.5.2 无用 尝试卸载重新安装Windows Terminal 无效果 在Bing搜索 找到了https://answers.microsoft.com/zh-hans/windows/forum/all/windows11%e4%b8%93%e4%b8%9a%e7%89%88%e6%89%93/464c57b0-69c7-4696-ae6f-ea8289bfff0a 这个解决方案 使用其提供的初始配置文件替换WindowsTerminal后恢复使用 然后重新尝试安装PowerShell 7.5.2 没有出错 但是没有看到网上所说的自动在Windows Terminal内出现PowerShell7配置文件 尝试手动添加 编辑json文件 保存后测试正常 未出现报错 为了以防万一尝试重启计算机 重启Windows Terminal 均未出现错误 然后在一天后又出现了"参数错误"报错 这期间没有修改过Windows Terminal配置 在设置内修复 恢复使用 然后半天后再次出错 同样无修改 尝试设置内修复 无用 在设置内重置 恢复使用 暂时可用 但是频繁出错严重影响使用 希望可以修复 个人观点认为是数据目录(C:\Users\{用户名}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState)权限配置相关问题 是否考虑增加自定义数据目录功能 可能可以缓解这个错误 我认为这是windows对于Packages目录错误的权限控制设计或者缺陷导致的bug ### Expected Behavior _No response_ ### Actual Behavior Error message "Parameter error" is reported. 报错"参数错误"
claunia added the Issue-BugProduct-TerminalCulprit-Centennial labels 2026-01-31 08:41:41 +00:00
claunia commented 2026-01-31 08:41:42 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 9, 2025):

Hmm... Seems similar to #14368. For what it's worth, you can likely debug this issue yourself by installing "WinDbg" from the Microsoft Store and running Windows Terminal with it.

@lhecker commented on GitHub (Jul 9, 2025): Hmm... Seems similar to #14368. For what it's worth, you can likely debug this issue yourself by installing "WinDbg" from the Microsoft Store and running Windows Terminal with it.
claunia commented 2026-01-31 08:41:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 9, 2025):

Thank you. Can you include a screenshot of the issue/?

@DHowett commented on GitHub (Jul 9, 2025): Thank you. Can you include a screenshot of the issue/?
claunia commented 2026-01-31 08:41:42 +00:00
Author
Owner
Copy Link

@jsrcode commented on GitHub (Jul 10, 2025):

Thank you. Can you include a screenshot of the issue/?

Image
@jsrcode commented on GitHub (Jul 10, 2025): > Thank you. Can you include a screenshot of the issue/? <img width="558" height="190" alt="Image" src="https://github.com/user-attachments/assets/1365998a-0f3e-45a1-9b0c-468042e139c0" />
claunia commented 2026-01-31 08:41:43 +00:00
Author
Owner
Copy Link

@jsrcode commented on GitHub (Jul 10, 2025):

Hmm... Seems similar to #14368. For what it's worth, you can likely debug this issue yourself by installing "WinDbg" from the Microsoft Store and running Windows Terminal with it.

I ran into the error again, the first time last night, I reset the data through the settings and then imported the old configuration file to restore, the second time was this morning, and the problem came up again

我再次遇到了该错误 第一次的在昨天晚上 我通过设置内重置数据然后再导入旧的配置文件恢复 第二次是在今天早上 这个问题再次出现了

@jsrcode commented on GitHub (Jul 10, 2025): > Hmm... Seems similar to [#14368](https://github.com/microsoft/terminal/issues/14368). For what it's worth, you can likely debug this issue yourself by installing "WinDbg" from the Microsoft Store and running Windows Terminal with it. I ran into the error again, the first time last night, I reset the data through the settings and then imported the old configuration file to restore, the second time was this morning, and the problem came up again 我再次遇到了该错误 第一次的在昨天晚上 我通过设置内重置数据然后再导入旧的配置文件恢复 第二次是在今天早上 这个问题再次出现了
claunia commented 2026-01-31 08:41:43 +00:00
Author
Owner
Copy Link

@jsrcode commented on GitHub (Jul 13, 2025):

我认为这个故障是否出现取决于神灵，上帝，佛主，玉帝，他出现故障的原因似乎和权限没有关系 因为 我遇到故障后因为没有时间 没对其进行任何操作 在半个小时以后 我再次打开他的时候 他奇迹般的好了

I think it depends on the gods, the gods, the Buddhas, the Jade Emperor, and the reason for his failure doesn't seem to have anything to do with permissions, because I didn't have time to do anything with it, and after half an hour, when I opened him again, he miraculously recovered

@jsrcode commented on GitHub (Jul 13, 2025): 我认为这个故障是否出现取决于神灵，上帝，佛主，玉帝，他出现故障的原因似乎和权限没有关系 因为 我遇到故障后因为没有时间 没对其进行任何操作 在半个小时以后 我再次打开他的时候 他奇迹般的好了 I think it depends on the gods, the gods, the Buddhas, the Jade Emperor, and the reason for his failure doesn't seem to have anything to do with permissions, because I didn't have time to do anything with it, and after half an hour, when I opened him again, he miraculously recovered
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 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#23419
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?