Windows command safety now recognises many more PowerShell cmdlets, flagging download-capable ones as dangerous.
What's wrong with this entry?
Command safety analysis on Windows now recognises more PowerShell cmdlets, including location and output ones (set-location, push-location, pop-location, write-output, write-host), pipeline and formatting ones such as where-object and format-table, and a download-capable set flagged as dangerous (invoke-webrequest, iwr, new-object, start-bitstransfer). The shell binaries pwsh and powershell are named as a set.
start-bitstransfer
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