Microsoft’s November 10 Windows 11 security update makes Windows PowerShell signature validation stricter about script encoding. Files containing invalid UTF-8 bytes that previously passed may now fail with a signature error. Official guidance describes reviewing the contents, saving valid UTF-8 with a BOM and signing the file again. The response is to check deployed scripts’ origins and encoding rather than disable signature verification. The change does not mean every PowerShell script stops working.
Back to Tech
Windows security update tightens script-encoding checks
If a signed script is rejected, check valid UTF-8 encoding and the required re-signing process.