Skip to content

ConvertTo-Csv/Export-Csv -UseCulture:$false uses the wrong delimiter in ouput #26513

Open

Description

@surfingoldelephant

Prerequisites

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:$false

Export-Csv:

$file = (New-TemporaryFile).FullName
[pscustomobject] @{ H1 = 'V1'; H2 = 'V2' } | Export-Csv -LiteralPath $file -UseCulture:$false

Expected behavior

ConvertTo-Csv:

"H1","H2"
"V1","V2"

Export-Csv:

"H1","H2"
"V1","V2"
  • -UseCulture:$false behaves 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:$false neither behaves as if the switch was or wasn't specified.
  • ConvertTo-Csv output includes no item delimiter.
  • Export-Csv output 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.0

Activity

  1. moved this from Queue to In-Progress-Issues in Cmdlets Working Groupon Feb 18, 2026
  2. SteveL-MSFT commented on Feb 18, 2026

    @SteveL-MSFT
    Member

    The @PowerShell/wg-powershell-cmdlets agrees this is a bug that should be fixed.

  3. added
    Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
    WG-ReviewedA Working Group has reviewed this and made a recommendation
    and removed
    Needs-TriageThe issue is new and needs to be triaged by a work group.
    on Feb 18, 2026
  4. moved this from In-Progress-Issues to Reviewed in Cmdlets Working Groupon Feb 18, 2026
  5. added 2 commits that reference this issue on Mar 22, 2026
    0564012
    bd5da2a
  6. changed the title [-]`ConvertTo-Csv`/`Export-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/-] [+]`ConvertTo-Csv`/`Import-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/+] on Aug 11, 2026
  7. changed the title [-]`ConvertTo-Csv`/`Import-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/-] [+]`ConvertTo-Csv`/`Export-Csv -UseCulture:$false` uses the wrong delimiter in ouput[/+] on Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-BugIssue has been identified as a bug in the productUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdletsgeneral cmdlet issuesWG-ReviewedA Working Group has reviewed this and made a recommendation

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions