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

error 0x800700e2 when launching `powershell.exe' #16305

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

Originally created by @NareshChinnusamy on GitHub (Dec 29, 2021).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000

Other Software

Software: Powershell
Version: 5.1

Steps to reproduce

  • I opened the windows terminal application from start.
  • Default profiles have been set for the PowerShell application in the windows terminal.
  • Powershell tab is opening with an error showing [error 0x800700e2 when launching `powershell.exe']
  • But the PowerShell is working fine during standalone launch.
  • And I have been able to access PowerShell via visual studio's terminal.

Expected Behavior

I'm expecting a new tab of PowerShell opening in the windows terminal without any issues.

Actual Behavior

The new tab of PowerShell always shows [error 0x800700e2 when launching `powershell.exe'].
I tried different fix approaches like adding PATH of PowerShell to environment variables but nothing is working.

Originally created by @NareshChinnusamy on GitHub (Dec 29, 2021). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.22000 ### Other Software Software: Powershell Version: 5.1 ### Steps to reproduce - I opened the windows terminal application from start. - Default profiles have been set for the PowerShell application in the windows terminal. - Powershell tab is opening with an error showing [error 0x800700e2 when launching `powershell.exe'] - But the PowerShell is working fine during standalone launch. - And I have been able to access PowerShell via visual studio's terminal. ### Expected Behavior I'm expecting a new tab of PowerShell opening in the windows terminal without any issues. ### Actual Behavior The new tab of PowerShell always shows [error 0x800700e2 when launching `powershell.exe']. I tried different fix approaches like adding PATH of PowerShell to environment variables but nothing is working.
claunia commented 2026-01-31 05:03:32 +00:00
Author
Owner
Copy Link

@eryksun commented on GitHub (Dec 29, 2021):

0x8007 in the high word means it's an HRESULT code for a Windows error code. 0x00E2 (226) in the low word is the Windows error code ERROR_VIRUS_DELETED. I doubt the same executable would be repeatedly reported as being infected by a virus instead of the file being moved to a quarantine location. Maybe Terminal is misreporting the exit status.

@eryksun commented on GitHub (Dec 29, 2021): 0x8007 in the high word means it's an `HRESULT` code for a Windows error code. 0x00E2 (226) in the low word is the Windows error code `ERROR_VIRUS_DELETED`. I doubt the same executable would be repeatedly reported as being infected by a virus instead of the file being moved to a quarantine location. Maybe Terminal is misreporting the exit status.
claunia commented 2026-01-31 05:03:32 +00:00
Author
Owner
Copy Link

@NareshChinnusamy commented on GitHub (Dec 29, 2021):

@eryksun Is there any other way to resolve this issue?

@NareshChinnusamy commented on GitHub (Dec 29, 2021): @eryksun Is there any other way to resolve this issue?
claunia commented 2026-01-31 05:03:32 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Dec 29, 2021):

@NareshChinnusamy you might try setting CMD as the default profile, launch windows terminal then start powershell.exe from CMD prompt or another tab and try to narrow down which is the potentially unwanted application

Since your terminal crashes upon launch you might have to directly edit settings.json file.

Also, you could launch CMD profile by running wt.exe --profile "Command Prompt" from win+r

@elsaco commented on GitHub (Dec 29, 2021): @NareshChinnusamy you might try setting `CMD` as the default profile, launch windows terminal then start `powershell.exe` from `CMD` prompt or another tab and try to narrow down which is the `potentially unwanted application` Since your terminal crashes upon launch you might have to directly edit `settings.json` file. Also, you could launch CMD profile by running `wt.exe --profile "Command Prompt"` from `win+r`
claunia commented 2026-01-31 05:03:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2022):

What's your PATH set to in a cmd.exe tab?

Are you using any sore of antivirus software?

@zadjii-msft commented on GitHub (Jan 3, 2022): What's your `PATH` set to in a cmd.exe tab? Are you using any sore of antivirus software?
claunia commented 2026-01-31 05:03:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 7, 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 (Jan 7, 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**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#16305
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?