On Windows, non-ASCII characters in your project path no longer corrupt the internal pipe name.
What's wrong with this entry?
On Windows, the internal pipe name built from your project path now lowercases only A-Z runs instead of applying a full lowercase to the whole string, so non-ASCII characters in a path are left alone and locale rules cannot corrupt the name.
- Windows only.
\\\\.\\pipe\\
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window