Given that the documented behaviour is that ".. the sort key produces the same order as when the source string is used in CompareString or CompareStringEx"[1], this seems like a reportable bug, unless perhaps your test program is hiding an error with that default case you have.