the export-counter cmdlet writes the sampling timestamp column in the US format (MM/dd/yyyy) to a csv file - as viewed in Notepad - regardless of which culture is currently in influence. This creates many issues with importing/using the data. (other cmdlets such as get-counter and get-date utilize the current culture correctly and subsequently return the correct date format).
Is this a bug or by design? If by design, where is this... exceptional feature documented and what's the rationale behind such design? Note in the reproduction steps that the get-counter statement returns the correct date format (