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

[error 0x800700c1 when launching `C:\Program Files\PowerShell\7\pwsh.exe'] #14066

New Issue
Closed
opened 2026-01-31 03:59:53 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:59:53 +00:00
Owner
Copy Link

Originally created by @Manbearpiet on GitHub (May 31, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Preview Version: 1.9.1445.0

Other Software

No response

Steps to reproduce

Startup terminal as usual (with C:\Program Files\PowerShell\7\pwsh.exe as default)
Also happens when new tabs are opened with pwsh

Expected Behavior

It starts C:\Program Files\PowerShell\7\pwsh.exe

Actual Behavior

It throws [error 0x800700c1 when launching `C:\Program Files\PowerShell\7\pwsh.exe']

Originally created by @Manbearpiet on GitHub (May 31, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Preview Version: 1.9.1445.0 ### Other Software _No response_ ### Steps to reproduce Startup terminal as usual (with C:\Program Files\PowerShell\7\pwsh.exe as default) Also happens when new tabs are opened with pwsh ### Expected Behavior It starts C:\Program Files\PowerShell\7\pwsh.exe ### Actual Behavior It throws [error 0x800700c1 when launching `C:\Program Files\PowerShell\7\pwsh.exe']
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:59:53 +00:00
claunia commented 2026-01-31 03:59:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 31, 2021):

Out of curiosity, which architecture of pwsh 7 did you install, and what architecture is your machine?

We've seen this before a few times (#7160, #7195), but not when someone's hardcoding the path.

Troubling that there are two similar reports (see also #10270) on the latest update.

@zadjii-msft commented on GitHub (May 31, 2021): Out of curiosity, which architecture of pwsh 7 did you install, and what architecture is your machine? We've seen this before a few times (#7160, #7195), but not when someone's hardcoding the path. Troubling that there are two similar reports (see also #10270) on the latest update.
claunia commented 2026-01-31 03:59:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 31, 2021):

Also,

Is there a C:\Program file? According to https://github.com/microsoft/terminal/issues/7195#issuecomment-720627551, that could cause error 0x800700c1. If so, you could perhaps delete the file?

@zadjii-msft commented on GitHub (May 31, 2021): Also, > Is there a `C:\Program` file? According to <https://github.com/microsoft/terminal/issues/7195#issuecomment-720627551>, that could cause error 0x800700c1. If so, you could perhaps delete the file?
claunia commented 2026-01-31 03:59:54 +00:00
Author
Owner
Copy Link

@Manbearpiet commented on GitHub (May 31, 2021):

Out of curiosity, which architecture of pwsh 7 did you install, and what architecture is your machine?

We've seen this before a few times (#7160, #7195), but not when someone's hardcoding the path.

Troubling that there are two similar reports (see also #10270) on the latest update.

Using the exe
$PSVersionTable

Name Value

PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

Launching the path mentioned in the Terminal settings with run-command works fine.
image

When pasted:
image

settings.json:
Contains the following:

    "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",





            {
                "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "hidden": false,
                "name": "PowerShell",
                "source": "Windows.Terminal.PowershellCore"
            },
@Manbearpiet commented on GitHub (May 31, 2021): > > > Out of curiosity, which architecture of pwsh 7 did you install, and what architecture is your machine? > > We've seen this before a few times (#7160, #7195), but not when someone's hardcoding the path. > > Troubling that there are two similar reports (see also #10270) on the latest update. Using the exe $PSVersionTable Name Value ---- ----- PSVersion 7.1.3 PSEdition Core GitCommitId 7.1.3 OS Microsoft Windows 10.0.19042 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0 Launching the path mentioned in the Terminal settings with run-command works fine. ![image](https://user-images.githubusercontent.com/43993129/120186433-cb8b4000-c213-11eb-851d-63d206743fcd.png) When pasted: ![image](https://user-images.githubusercontent.com/43993129/120186589-fe353880-c213-11eb-8162-a1e1e0779f53.png) settings.json: Contains the following: ``` "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell", "source": "Windows.Terminal.PowershellCore" }, ```
claunia commented 2026-01-31 03:59:54 +00:00
Author
Owner
Copy Link

@Manbearpiet commented on GitHub (May 31, 2021):

Also,

Is there a C:\Program file? According to #7195 (comment), that could cause error 0x800700c1. If so, you could perhaps delete the file?

This was the fix!!

The file blocking launch is a log file created with Citrix receiver updates:

C:\Program-file (opened with notepad)

[11F4:38F4][2021-05-28T13:24:51]i001: Burn v3.10.4.4718, Windows v10.0 (Build 19042: Service Pack 0), path: C:\Windows\Temp\{someguid}\.cr\vc_redist.x64.exe
[11F4:38F4][2021-05-28T13:24:51]i009: Command Line: '-burn.clean.room=C:\Windows\SysWOW64\config\systemprofile\Citrix\UpdaterBinaries\Ctx-someguid\Extract\vc_redist.x64.exe -burn.filehandle.attached=596 -burn.filehandle.self=736 /q /norestart /ACTION=Install /l C:\Program Files (x86)\Citrix\Logs\CTXReceiverInstallLogs-20210528-132448\CtxInstall-vc_redist-20210528-132449.log'

Removing the C:\Program-file fixed it

image

@Manbearpiet commented on GitHub (May 31, 2021): > > > Also, > > > Is there a `C:\Program` file? According to [#7195 (comment)](https://github.com/microsoft/terminal/issues/7195#issuecomment-720627551), that could cause error 0x800700c1. If so, you could perhaps delete the file? This was the fix!! The file blocking launch is a log file created with Citrix receiver updates: `C:\Program`-file (opened with notepad) ``` [11F4:38F4][2021-05-28T13:24:51]i001: Burn v3.10.4.4718, Windows v10.0 (Build 19042: Service Pack 0), path: C:\Windows\Temp\{someguid}\.cr\vc_redist.x64.exe [11F4:38F4][2021-05-28T13:24:51]i009: Command Line: '-burn.clean.room=C:\Windows\SysWOW64\config\systemprofile\Citrix\UpdaterBinaries\Ctx-someguid\Extract\vc_redist.x64.exe -burn.filehandle.attached=596 -burn.filehandle.self=736 /q /norestart /ACTION=Install /l C:\Program Files (x86)\Citrix\Logs\CTXReceiverInstallLogs-20210528-132448\CtxInstall-vc_redist-20210528-132449.log' ``` Removing the `C:\Program`-file fixed it ![image](https://user-images.githubusercontent.com/43993129/120187220-d5617300-c214-11eb-9bbd-e57f6e6094db.png)
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 Needs-Attention 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#14066
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?