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

PSCore fails to load profile if startingDirectory points to other drive #3004

New Issue
Closed
opened 2026-01-30 23:10:40 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 23:10:40 +00:00
Owner
Copy Link

Originally created by @davidkwoods on GitHub (Jul 30, 2019).

Environment

Windows build number: 10.0.18362.239
Windows Terminal version (if applicable): 0.2.1831.0

Any other software?
No

Steps to reproduce

Set startingDirectory for the PSCore profile to a directory not on the C: drive. In my example, the D: drive.

Expected behavior

PSCore should still load its profile from C:\Users\<user>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

Actual behavior

PSCore attempts to load its profile from \Users\<user>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 and fails because it tries to find it on the D: drive, which doesn't contain that file.

The same steps do not repro for classic PowerShell. It loads its profile correctly when set to start on a different drive.

Originally created by @davidkwoods on GitHub (Jul 30, 2019). # Environment ```none Windows build number: 10.0.18362.239 Windows Terminal version (if applicable): 0.2.1831.0 Any other software? No ``` # Steps to reproduce Set startingDirectory for the PSCore profile to a directory not on the C: drive. In my example, the D: drive. # Expected behavior PSCore should still load its profile from `C:\Users\<user>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1` # Actual behavior PSCore attempts to load its profile from `\Users\<user>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1` and fails because it tries to find it on the D: drive, which doesn't contain that file. The same steps do not repro for classic PowerShell. It loads its profile correctly when set to start on a different drive.
claunia commented 2026-01-30 23:10:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 30, 2019):

This is highly irregular. What version of PSCore?
This should also reproduce if you run pwsh from a standard console host by starting it from CMD. Windows Terminal doesn’t change how an application starts up, after all.

C:\>D:
D:\>pwsh
@DHowett-MSFT commented on GitHub (Jul 30, 2019): This is highly irregular. What version of PSCore? This should also reproduce if you run `pwsh` from a standard console host by starting it from CMD. Windows Terminal doesn’t change how an application starts up, after all. ``` C:\>D: D:\>pwsh ```
claunia commented 2026-01-30 23:10:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2019):

@Björn Did you delete your comment for some reason? If you can confirm this is happening in other terminals, not just the Windows Terminal, then we should definitely just close this issue in favor of tracking an issue on the powershell repo

From: Björn Petersen notifications@github.com
Sent: Sunday, August 4, 2019 3:07 AM
To: microsoft/terminal terminal@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Subject: Re: [microsoft/terminal] PSCore fails to load profile if startingDirectory points to other drive (#2154)

I'm having the same problem with PSCore, but it's not related to the new terminal for me. It also happens in the old terminal and integrated in IDEs like IntelliJ.

@zadjii-msft commented on GitHub (Aug 5, 2019): @Björn Did you delete your comment for some reason? If you can confirm this is happening in other terminals, not _just_ the Windows Terminal, then we should definitely just close this issue in favor of tracking an issue on the powershell repo From: Björn Petersen <notifications@github.com> Sent: Sunday, August 4, 2019 3:07 AM To: microsoft/terminal <terminal@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [microsoft/terminal] PSCore fails to load profile if startingDirectory points to other drive (#2154) I'm having the same problem with PSCore, but it's not related to the new terminal for me. It also happens in the old terminal and integrated in IDEs like IntelliJ.
claunia commented 2026-01-30 23:10:42 +00:00
Author
Owner
Copy Link

@BjoernPetersen commented on GitHub (Aug 5, 2019):

I re-read the issue and realized my problem is not related.

@BjoernPetersen commented on GitHub (Aug 5, 2019): I re-read the issue and realized my problem is not related.
claunia commented 2026-01-30 23:10:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 10, 2019):

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 (Aug 10, 2019): 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 Area-TerminalConnection Issue-Bug Needs-Author-Feedback No-Recent-Activity Product-Terminal
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#3004
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?