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

The -NoLogo argument to PowerShell does not work #18417

New Issue
Closed
opened 2026-01-31 06:13:19 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:13:19 +00:00
Owner
Copy Link

Originally created by @Tembocs on GitHub (Sep 11, 2022).

Windows Terminal version

1.14.2282.0

Windows build number

10.0.22000.0

Other Software

PowerShell version 7.2.6

Steps to reproduce

Start Windows Terminal
Go to settings then PowerShell (under Profiles)
Go to Command line and add -NoLogo so that it is "C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"
Restart Windows Terminal
The following error message shows up [error 2147942402 (0x80070002) when launching '"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"']

Expected Behavior

I would expect Windows Terminal to start normally with PowerShell profile without the PowerShell banner because that is what -NoLogo argument is for, hiding the banner.

Actual Behavior

The actual behaviour is the error message[error 2147942402 (0x80070002) when launching "C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"']

However if I use JSON settings to set "commandline": "C:/Program Files/PowerShell/7/pwsh.exe -NoLogo" for PowerShell profile this works as expected without any error.

Originally created by @Tembocs on GitHub (Sep 11, 2022). ### Windows Terminal version 1.14.2282.0 ### Windows build number 10.0.22000.0 ### Other Software PowerShell version 7.2.6 ### Steps to reproduce Start Windows Terminal Go to settings then PowerShell (under Profiles) Go to Command line and add `-NoLogo` so that it is `"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"` Restart Windows Terminal The following error message shows up `[error 2147942402 (0x80070002) when launching '"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"']` ### Expected Behavior I would expect Windows Terminal to start normally with PowerShell profile without the PowerShell banner because that is what `-NoLogo` argument is for, hiding the banner. ### Actual Behavior The actual behaviour is the error message`[error 2147942402 (0x80070002) when launching "C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"']` However if I use JSON settings to set `"commandline": "C:/Program Files/PowerShell/7/pwsh.exe -NoLogo"` for PowerShell profile this works as expected without any error.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:13:20 +00:00
claunia commented 2026-01-31 06:13:21 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Sep 11, 2022):

You have to escape slash with one more slash \\ in JSON.

@237dmitry commented on GitHub (Sep 11, 2022): You have to escape slash with one more slash `\\` in JSON.
claunia commented 2026-01-31 06:13:21 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 11, 2022):

"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo"

in the settings UI translates to

"\"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo\""

in the settings.json file and "pwsh.exe -NoLogo" is not an executable that exists on your computer.
This results in 0x80070002 which translates to "The system cannot find the file specified." (ERROR_FILE_NOT_FOUND).

Try writing this in the settings UI instead:

"C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo

If this resolves your problem, please feel free to close this issue. 🙂

@lhecker commented on GitHub (Sep 11, 2022): ``` "C:\Program Files\PowerShell\7\pwsh.exe -NoLogo" ``` in the settings UI translates to ``` "\"C:\Program Files\PowerShell\7\pwsh.exe -NoLogo\"" ``` in the settings.json file and "pwsh.exe -NoLogo" is not an executable that exists on your computer. This results in `0x80070002` which translates to "The system cannot find the file specified." (`ERROR_FILE_NOT_FOUND`). Try writing this in the settings UI instead: ``` "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo ``` If this resolves your problem, please feel free to close this issue. 🙂
claunia commented 2026-01-31 06:13:22 +00:00
Author
Owner
Copy Link

@Tembocs commented on GitHub (Sep 12, 2022):

@lhecker this works, thanks.

@Tembocs commented on GitHub (Sep 12, 2022): @lhecker this works, thanks.
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-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#18417
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?