Repository navigation
Open
Open
Copy link
Labels
Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issuesWG-ReviewedA Working Group has reviewed this and made a recommendationA Working Group has reviewed this and made a recommendation
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Summary
This is a sub-issue of #25242.
ConvertTo-Csv and Export-Csv do not respect an explicit $false value for the -UseCulture switch parameter.
-UseCulture:$false doesn't behave as if the switch wasn't specified. It also doesn't behave as if it was specified. Instead, it results in either no delimiter (ConvertTo-Csv) or a space as the delimiter (Export-Csv).
Steps to reproduce
ConvertTo-Csv:
[pscustomobject] @{ H1 = 'V1'; H2 = 'V2' } | ConvertTo-Csv -UseCulture:$falseExport-Csv:
$file = (New-TemporaryFile).FullName
[pscustomobject] @{ H1 = 'V1'; H2 = 'V2' } | Export-Csv -LiteralPath $file -UseCulture:$falseExpected behavior
ConvertTo-Csv:
"H1","H2"
"V1","V2"
Export-Csv:
"H1","H2"
"V1","V2"
-UseCulture:$falsebehaves as if the switch wasn't specified.- The default
,item delimiter is used by both commands.
Actual behavior
ConvertTo-Csv:
"H1""H2"
"V1""V2"
Export-Csv:
"H1" "H2"
"V1" "V2"
-UseCulture:$falseneither behaves as if the switch was or wasn't specified.ConvertTo-Csvoutput includes no item delimiter.Export-Csvoutput includes a space as the item delimiter.
Environment data
Name Value
---- -----
PSVersion 7.6.0-preview.5
PSEdition Core
GitCommitId 7.6.0-preview.5
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0, 5.0, 5.1…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Reacted by Michael Klement
Metadata
Metadata
Assignees
Labels
Issue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issuesWG-ReviewedA Working Group has reviewed this and made a recommendationA Working Group has reviewed this and made a recommendation
Type
Projects
- StatusShow more project fieldsReviewed
Activity
SteveL-MSFT commentedon Feb 18, 2026
The @PowerShell/wg-powershell-cmdlets agrees this is a bug that should be fixed.
Fix ConvertTo-Csv/Export-Csv -UseCulture:$false uses wrong delimiter
Fix ConvertTo-Csv/Export-Csv -UseCulture:$false uses wrong delimiter (F…
Respect explicit false for CSV UseCulture (PowerShell#26513)
[-]`ConvertTo-Csv`/`Export-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/-][+]`ConvertTo-Csv`/`Import-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/+][-]`ConvertTo-Csv`/`Import-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/-][+]`ConvertTo-Csv`/`Export-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/+]