starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

windows打开参数错误 #17349

New Issue
Closed
opened 2026-01-31 05:39:58 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:39:58 +00:00
Owner
Copy Link

Originally created by @sunjikui on GitHub (Apr 27, 2022).

Windows Terminal version

No response

Windows build number

10.0.19043.1526

Other Software

1651043554(1)

Steps to reproduce

安装好打开就是参数错误，之前可以用，突然不知道怎么就坏了

Expected Behavior

No response

Actual Behavior

1651043554(1)

Originally created by @sunjikui on GitHub (Apr 27, 2022). ### Windows Terminal version _No response_ ### Windows build number 10.0.19043.1526 ### Other Software ![1651043554(1)](https://user-images.githubusercontent.com/33799970/165462101-3415794a-c6ec-422e-b167-c74743d8eb5c.jpg) ### Steps to reproduce 安装好打开就是参数错误，之前可以用，突然不知道怎么就坏了 ### Expected Behavior _No response_ ### Actual Behavior ![1651043554(1)](https://user-images.githubusercontent.com/33799970/165462305-814f48e2-762f-4773-a6c4-4d750a9b4d99.jpg)
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 05:39:58 +00:00
claunia commented 2026-01-31 05:40:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2022):

Hmm. Someone else got the same error over in #7611, but then just closed the issue themself without sharing how they fixed it.

Here are some similar issues

#4095 seems to imply that it might have to do with having bad permissions on the WindowsApps folder. Have you changed those at all/? Try running the following command, from PowerShell:

get-acl \Program` Files\WindowsApps | fl

(from #9959)

@zadjii-msft commented on GitHub (Apr 27, 2022): Hmm. Someone else got the same error over in #7611, but then just closed the issue themself without sharing how they fixed it. Here are some [similar issues](https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22The+parameter+is+incorrect%22+is%3Aclosed) #4095 seems to imply that it might have to do with having bad permissions on the `WindowsApps` folder. Have you changed those at all/? Try running the following command, from PowerShell: ```pwsh get-acl \Program` Files\WindowsApps | fl ``` (from #9959)
claunia commented 2026-01-31 05:40:00 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 1, 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 (May 1, 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 05:40:00 +00:00
Author
Owner
Copy Link

@westfly commented on GitHub (May 14, 2022):

相同的错误，尝试了9959 中的方法，一样的错误
卸载重装也不行，安装prev版本也是相同的错误

PS C:\Program Files> Get-Acl .\WindowsApps\ |fl


Path   : Microsoft.PowerShell.Core\FileSystem::C:\Program Files\WindowsApps\
Owner  : LAPTOP-####for###private\####
Group  : NT SERVICE\TrustedInstaller
Access : NT SERVICE\TrustedInstaller Allow  FullControl
         NT SERVICE\TrustedInstaller Allow  268435456
         NT AUTHORITY\SYSTEM Allow  FullControl
         NT AUTHORITY\SYSTEM Allow  268435456
         BUILTIN\Administrators Allow  FullControl
         BUILTIN\Administrators Allow  268435456
         BUILTIN\Users Allow  ReadAndExecute, Synchronize
         BUILTIN\Users Allow  -1610612736
         LAPTOP-OB6NES61\mintegral Allow  FullControl
         CREATOR OWNER Allow  268435456
         APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow  ReadAndExecute, Synchronize
         APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow  -1610612736
         APPLICATION PACKAGE AUTHORITY\所有受限制的应用程序包 Allow  ReadAndExecute, Synchronize
         APPLICATION PACKAGE AUTHORITY\所有受限制的应用程序包 Allow  -1610612736
Audit  :
Sddl   : O:S-1-5-21-2594991028-2133156761-2730387977-1001G:S-1-5-80-956008885-3418522649-1831038044-1853292631-22714784
         64D:AI(A;ID;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CIIOID;GA;;;S-1-5-80-956008
         885-3418522649-1831038044-1853292631-2271478464)(A;ID;FA;;;SY)(A;OICIIOID;GA;;;SY)(A;ID;FA;;;BA)(A;OICIIOID;GA
         ;;;BA)(A;ID;0x1200a9;;;BU)(A;OICIIOID;GXGR;;;BU)(A;ID;FA;;;S-1-5-21-2594991028-2133156761-2730387977-1001)(A;O
         ICIIOID;GA;;;CO)(A;ID;0x1200a9;;;AC)(A;OICIIOID;GXGR;;;AC)(A;ID;0x1200a9;;;S-1-15-2-2)(A;OICIIOID;GXGR;;;S-1-1
         5-2-2)

手工注册

PS C:\> Add-AppPackage -Register 'C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\AppxManifest.xml'
Add-AppPackage : 部署失败，原因是 HRESULT: 0x80073CF9, 无法安装。请联系你的软件供应商。 (异常来自 HRESULT:0x80073CF9)
正在拒绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于程序包根目录中。
注意: 有关其他信息，请在事件日志中查找 [ActivityId] ca02a98e-656c-0000-0391-16ca6c65d801，或使用命令行 Get-AppPackageLo
g -ActivityID ca02a98e-656c-0000-0391-16ca6c65d801
所在位置 行:1 字符: 1
+ Add-AppPackage -Register 'C:\Program Files\WindowsApps\Microsoft.Wind ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Program File...ppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand
PS C:\> Get-AppPackageLog -ActivityID ca02a98e-656c-0000-0391-16ca6c65d801

Time                      ID           Message
----                      --           -------
2022/5/14 23:20:59        603          已使用主参数 AppxManifest.xml 以及选项 DevelopmentModeOption 和 0 开始对程序包执
                                       行部署 Register 操作。要获取有关诊断应用部署问题的帮助，请参阅 http://go.microso
                                       ft.com/fwlink/?LinkId=235160。
2022/5/14 23:20:59        216          应用部件清单(manifest)验证警告: 声明的命名空间 http://schemas.microsoft.com/deve
                                       loper/appx/2015/build 不适用，在清单处理期间将忽略它。
2022/5/14 23:20:59        709          正在拒绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于
                                       程序包根目录中。
2022/5/14 23:20:59        404          程序包  的 AppX 部署操作失败，错误为 0x80070057。此失败的具体错误文本是: 正在拒
                                       绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于程序包
                                       根目录中。
@westfly commented on GitHub (May 14, 2022): > 相同的错误，尝试了[9959](https://github.com/microsoft/terminal/issues/9959) 中的方法，一样的错误 卸载重装也不行，安装prev版本也是相同的错误 ``` PS C:\Program Files> Get-Acl .\WindowsApps\ |fl Path : Microsoft.PowerShell.Core\FileSystem::C:\Program Files\WindowsApps\ Owner : LAPTOP-####for###private\#### Group : NT SERVICE\TrustedInstaller Access : NT SERVICE\TrustedInstaller Allow FullControl NT SERVICE\TrustedInstaller Allow 268435456 NT AUTHORITY\SYSTEM Allow FullControl NT AUTHORITY\SYSTEM Allow 268435456 BUILTIN\Administrators Allow FullControl BUILTIN\Administrators Allow 268435456 BUILTIN\Users Allow ReadAndExecute, Synchronize BUILTIN\Users Allow -1610612736 LAPTOP-OB6NES61\mintegral Allow FullControl CREATOR OWNER Allow 268435456 APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow ReadAndExecute, Synchronize APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow -1610612736 APPLICATION PACKAGE AUTHORITY\所有受限制的应用程序包 Allow ReadAndExecute, Synchronize APPLICATION PACKAGE AUTHORITY\所有受限制的应用程序包 Allow -1610612736 Audit : Sddl : O:S-1-5-21-2594991028-2133156761-2730387977-1001G:S-1-5-80-956008885-3418522649-1831038044-1853292631-22714784 64D:AI(A;ID;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CIIOID;GA;;;S-1-5-80-956008 885-3418522649-1831038044-1853292631-2271478464)(A;ID;FA;;;SY)(A;OICIIOID;GA;;;SY)(A;ID;FA;;;BA)(A;OICIIOID;GA ;;;BA)(A;ID;0x1200a9;;;BU)(A;OICIIOID;GXGR;;;BU)(A;ID;FA;;;S-1-5-21-2594991028-2133156761-2730387977-1001)(A;O ICIIOID;GA;;;CO)(A;ID;0x1200a9;;;AC)(A;OICIIOID;GXGR;;;AC)(A;ID;0x1200a9;;;S-1-15-2-2)(A;OICIIOID;GXGR;;;S-1-1 5-2-2) ``` 手工注册 ``` PS C:\> Add-AppPackage -Register 'C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\AppxManifest.xml' Add-AppPackage : 部署失败，原因是 HRESULT: 0x80073CF9, 无法安装。请联系你的软件供应商。 (异常来自 HRESULT:0x80073CF9) 正在拒绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于程序包根目录中。 注意: 有关其他信息，请在事件日志中查找 [ActivityId] ca02a98e-656c-0000-0391-16ca6c65d801，或使用命令行 Get-AppPackageLo g -ActivityID ca02a98e-656c-0000-0391-16ca6c65d801 所在位置 行:1 字符: 1 + Add-AppPackage -Register 'C:\Program Files\WindowsApps\Microsoft.Wind ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : WriteError: (C:\Program File...ppxManifest.xml:String) [Add-AppxPackage], IOException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand PS C:\> Get-AppPackageLog -ActivityID ca02a98e-656c-0000-0391-16ca6c65d801 Time ID Message ---- -- ------- 2022/5/14 23:20:59 603 已使用主参数 AppxManifest.xml 以及选项 DevelopmentModeOption 和 0 开始对程序包执 行部署 Register 操作。要获取有关诊断应用部署问题的帮助，请参阅 http://go.microso ft.com/fwlink/?LinkId=235160。 2022/5/14 23:20:59 216 应用部件清单(manifest)验证警告: 声明的命名空间 http://schemas.microsoft.com/deve loper/appx/2015/build 不适用，在清单处理期间将忽略它。 2022/5/14 23:20:59 709 正在拒绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于 程序包根目录中。 2022/5/14 23:20:59 404 程序包 的 AppX 部署操作失败，错误为 0x80070057。此失败的具体错误文本是: 正在拒 绝从 AppxBundleManifest.xml 进行注册的请求，因为部件清单(manifest)没有位于程序包 根目录中。 ```
claunia commented 2026-01-31 05:40:00 +00:00
Author
Owner
Copy Link

@goodbey857 commented on GitHub (Nov 12, 2022):

我找到的一个解决的办法是 在 设置》账户》其他用户》添加账户 。 再用新的账户登陆电脑，就能打开Windows Terminal 了。
此外我的 “小组件” 在旧帐户中打不开，但在新账户中也能打开。

我搜索到的一个说法是 “可能是旧帐户的用户配置出了问题”。折腾了好久，也没能找到修复旧帐户的用户配置的方法。

@goodbey857 commented on GitHub (Nov 12, 2022): 我找到的一个解决的办法是 在 设置》账户》其他用户》添加账户 。 再用新的账户登陆电脑，就能打开Windows Terminal 了。 此外我的 “小组件” 在旧帐户中打不开，但在新账户中也能打开。 我搜索到的一个说法是 “可能是旧帐户的用户配置出了问题”。折腾了好久，也没能找到修复旧帐户的用户配置的方法。
claunia commented 2026-01-31 05:40:01 +00:00
Author
Owner
Copy Link

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

我找到的一个解决的办法是 在 设置》账户》其他用户》添加账户 。 再用新的账户登陆电脑，就能打开Windows Terminal 了。 此外我的 “小组件” 在旧帐户中打不开，但在新账户中也能打开。

我搜索到的一个说法是 “可能是旧帐户的用户配置出了问题”。折腾了好久，也没能找到修复旧帐户的用户配置的方法。

终于解决了，原因是我为了节省C盘空间，把"%username%/AppData/LocalLow"目录 移动到 了"D:/AppData/LocalLow"，然后创建了一个软链接，从“%username%/AppData/LocalLow" 指向 "D:/AppData/LocalLow"。
当我把"%username%/AppData/LocalLow"这个软连接删了，Windows Terminal 就能正常打开了。小组件也正常了。

@goodbey857 commented on GitHub (Dec 22, 2023): > 我找到的一个解决的办法是 在 设置》账户》其他用户》添加账户 。 再用新的账户登陆电脑，就能打开Windows Terminal 了。 此外我的 “小组件” 在旧帐户中打不开，但在新账户中也能打开。 > > 我搜索到的一个说法是 “可能是旧帐户的用户配置出了问题”。折腾了好久，也没能找到修复旧帐户的用户配置的方法。 终于解决了，原因是我为了节省C盘空间，把"%username%/AppData/LocalLow"目录 移动到 了"D:/AppData/LocalLow"，然后创建了一个**软链接**，从“%username%/AppData/LocalLow" 指向 "D:/AppData/LocalLow"。 当我把"%username%/AppData/LocalLow"这个**软连接**删了，Windows Terminal 就能正常打开了。小组件也正常了。
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 Issue-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage
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#17349
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?