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 Terminal error 0x800700c1 when launching `powershell.exe' #9982

New Issue
Closed
opened 2026-01-31 02:09:14 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 02:09:14 +00:00
Owner
Copy Link

Originally created by @dwram on GitHub (Aug 3, 2020).

Environment

Platform ServicePack Version VersionString

Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal version (if applicable): The latest as of this posting. No clue how to be certain.I believe v1.0.1401.0

Any other software?

Steps to reproduce

  1. Downloaded 64bit NodeJs with npm (with all required dependancies including chocolatey packages, which forcefully installed python 3.8 despite already having python) from https://nodejs.org/ in Powershell (Terminal)
  2. npm install -g javascripting ran this command in Powershell (Terminal ).
  3. Tried to run Javascripting. Was failing due to some Powershell scripting security error.
  4. Ran commands on https://www.opentechguides.com/how-to/article/powershell/105/powershel-security-error.html via Terminal (Powershell). Commands used were powershell.exe -executionpolicy -bypass Unblock-File -Path C:\Downloads\script1.ps1
  5. Restarted terminal
  6. Powershell is default shell: [error 0x800700c1 when launching `powershell.exe']
  7. Have tried playing around with adding new PATH (system and user) to my folder containing Python3.exe to no avail!

A description of how to trigger this bug.

  1. Open up Windows Terminal (Powershell)

Expected behavior

  1. Working Windows Terminal (Powershell)

A working powershell. Whereas I can actually use it in Windows Terminal.

Actual behavior

"[error 0x800700c1 when launching `powershell.exe']"

extra: Path information

image

Originally created by @dwram on GitHub (Aug 3, 2020). # Environment Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 Windows Terminal version (if applicable): The latest as of this posting. No clue how to be certain.I believe v1.0.1401.0 Any other software? # Steps to reproduce 1. Downloaded 64bit NodeJs with npm (with all required dependancies including chocolatey packages, which forcefully installed python 3.8 despite already having python) from **https://nodejs.org/** in Powershell (Terminal) 2. `npm install -g javascripting` ran this command in Powershell (Terminal ). 3. Tried to run **Javascripting**. Was failing due to some Powershell scripting security error. 4. Ran commands on https://www.opentechguides.com/how-to/article/powershell/105/powershel-security-error.html via Terminal (Powershell). Commands used were `powershell.exe -executionpolicy -bypass` `Unblock-File -Path C:\Downloads\script1.ps1` 5. Restarted terminal 6. Powershell is default shell: [error 0x800700c1 when launching `powershell.exe'] 7. Have tried playing around with adding new PATH (system and user) to my folder containing Python3.exe to no avail! A description of how to trigger this bug. 1. Open up Windows Terminal (Powershell) # Expected behavior 1. Working Windows Terminal (Powershell) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> A working powershell. Whereas I can actually use it in Windows Terminal. # Actual behavior <!-- What's actually happening? --> <img src="https://i.gyazo.com/b8089b85b7ac5754c038b1bf7a1ba4ad.png"> "[error 0x800700c1 when launching `powershell.exe']" extra: Path information ![image](https://user-images.githubusercontent.com/64813795/89199386-5f658e80-d5a6-11ea-9591-76d206d7668d.png)
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:09:14 +00:00
claunia commented 2026-01-31 02:09:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 3, 2020):

As a quick sanity check:
if you add a new custom profile that hardcodes the path to Windows PowerShell... does it work?

{
	"name": "PowerShell Test",
	"commandline": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
}
@zadjii-msft commented on GitHub (Aug 3, 2020): As a quick sanity check: if you add a new custom profile that _hardcodes the path to Windows PowerShell_... does it work? ```json { "name": "PowerShell Test", "commandline": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" } ```
claunia commented 2026-01-31 02:09:15 +00:00
Author
Owner
Copy Link

@dwram commented on GitHub (Aug 3, 2020):

As a quick sanity check:
if you add a new custom profile that hardcodes the path to Windows PowerShell... does it work?

{
	"name": "PowerShell Test",
	"commandline": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
}

image

Yes it seems to work. How do I rectify this so I don't need the "fake" test powershell?

image

(extra screen of my profiles)

@dwram commented on GitHub (Aug 3, 2020): > As a quick sanity check: > if you add a new custom profile that _hardcodes the path to Windows PowerShell_... does it work? > > ```json > { > "name": "PowerShell Test", > "commandline": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" > } > ``` ![image](https://user-images.githubusercontent.com/64813795/89199912-30035180-d5a7-11ea-96db-5a13fa57409c.png) Yes it seems to work. How do I rectify this so I don't need the "fake" test powershell? ![image](https://user-images.githubusercontent.com/64813795/89199964-44dfe500-d5a7-11ea-9949-6014fffe2c1e.png) (extra screen of my profiles)
claunia commented 2026-01-31 02:09:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 3, 2020):

For the quickest/easiest fix, delete the entire line containing commandline: powershell.exe (38) in your settings. Terminal will fall back to the "default" value (which is specified in another file), which we changed with #6684.

Thanks for troubleshooting with us!

@DHowett commented on GitHub (Aug 3, 2020): For the quickest/easiest fix, delete the entire line containing `commandline: powershell.exe` (38) in your settings. Terminal will fall back to the "default" value (which is specified in another file), which we changed with #6684. Thanks for troubleshooting with us!
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-Question Needs-Tag-Fix Resolution-Answered
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#9982
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?