Filenames disguised to mimic existing executables are now much harder to sneak past.
What's wrong with this entry?
The check for filenames that could collide with an existing .exe or .lnk file now defeats several disguises: characters from the U+F000-U+F0FF private-use block are mapped back to ASCII before comparing, trailing dots and spaces are stripped, and names are compared in both cases rather than lowercased once.
- The private-use unmapping step is new in this build.
.exe.lnk
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