-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get-Item returns invalid FileName when listing alternate data streams #18018
Comments
I've managed to find the reason for this behavior. File Class Method Line Description Probably the following change would fix the issue. That's how its handled elsewhere in
|
@ovdeathiam Won't |
@kilasuit Hah, gotta love off-by-one errors 😄 . Should be -1 there because |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
1 similar comment
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes. |
Prerequisites
Steps to reproduce
Whenever trying to list alternate data stream names and filenames with
Get-Item
the stream name is removed from FileName property value.Set-Content -Path C:\test.txt -Stream t -Value testvalue
Get-Item -Path C:\test.txt -stream t
Both Windows PowerShell and Powershell Core are affected. Tested on Windows 11 as well as Windows Server 2022.
Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: