{"version":"2.1.257","anchor":"powershell-command-safety-checks-extended-for-write-commands","canonical_anchor":"powershell-command-safety-checks-extended-for-write-commands","heading":"PowerShell command-safety checks extended for write commands with implicit reads","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/powershell-command-safety-checks-extended-for-write-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### PowerShell command-safety checks extended for write commands with implicit reads\n\nPowerShell checks now also validate the source path of copies and moves, and ask before a forced New-Item.\n\nThe PowerShell\/`pwsh` command permission checker now also validates the read side of write operations, such as checking whether the source path of a copy or move is itself blocked. It also now requires an 'ask' approval for `New-Item` invoked with a force-like flag, via a new helper that gates these additional checks.\n\n- Area: Windows\n- Names: `New-Item`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}