Newshot
Account

Microsoft tightens PowerShell security checks in November Windows 11 update, non-compliant scripts will fail

Source: IT之家 Published: Business & Funding 中文 Win11PowerShell 4 more articles on this event →
AI summary

In the cumulative update released for Windows 11 on this month's Patch Tuesday, Microsoft tightened security checks, which may cause some older PowerShell scripts to stop working properly. After installing the November cumulative update, Windows 11 introduces stricter text encoding checks for PowerShell script signing and validation, especially for files containing invalid UTF-8 encoding; previous versions might accept such non-compliant scripts by replacing invalid characters, but the new rules explicitly reject these encodings, so old scripts may be identified as "unsigned" even if they were signed, and re-signing may also produce errors. Microsoft's recommended fix is to save affected scripts as valid UTF-8 with a byte order mark (BOM), check the contents, and re-sign them; for users who need to process many files, Microsoft also provides a repair tool that scans for potential encoding issues and attempts to fix files while preserving existing signatures, without overwriting the originals. The change is not limited to Windows 11: Microsoft's guidance also covers Windows 10 Enterprise LTSC 2021 and some server versions, including Windows Server 2025.

Translation(model translation, not the source's own text)

Microsoft's November Windows 11 update tightens PowerShell security checks, non-compliant scripts will fail

IT Home, November 12: The tech media outlet NeoWin published a blog post today (November 12) reporting that in the cumulative update released for Windows 11 on this month's Patch Tuesday, Microsoft tightened security checks, which may cause some older PowerShell scripts to stop working properly.

The report points out that after installing the November cumulative update, Windows 11 introduces stricter text encoding checks for the signing and verification of PowerShell scripts, especially files containing incorrect UTF-8 encoding. Previous versions of Windows 11 could accept these non-compliant PowerShell scripts when decoding them by replacing invalid characters.

The new rules explicitly reject such encoding, so even old scripts that have already been signed may be identified as "unsigned," and attempts to re-sign them may likewise produce errors.

Microsoft's recommended fix is to save the affected scripts as valid UTF-8 encoding with a byte order mark (BOM), check the contents, and then re-sign them. For users who need to process files in bulk, Microsoft also provides a repair tool that can scan for potential encoding problems and attempt to repair files while preserving existing signatures, without overwriting the original files.

This change is not limited to Windows 11; Microsoft's guidance also covers Windows 10 Enterprise LTSC 2021 and some server versions, including Windows Server 2025.

  • Encoding guidelines for signed PowerShell scripts
  • Sample PowerShell script for fixing script signature encoding issues

Advertising statement: External redirect links contained in this article (including but not limited to hyperlinks, QR codes, passwords, and other forms) are used to convey more information and save selection time; the results are for reference only. All articles on IT Home that contain external links include this statement.

Related articles

  • Some Windows 11 users report errors installing Microsoft's November cumulative update, with the fault pointing to the sandbox feature
  • Up 1860.32% year over year: Microsoft fixed 1,235 vulnerabilities in November, setting a record for the number of fixes in the same month across previous years
  • May affect performance in some games: Microsoft's November Windows 11 cumulative update expands automatic enabling of "Memory integrity"
  • Microsoft releases November cumulative update for Windows 11: updates the autoplay dialog and fixes the "Code 10" error for some USB audio devices
  • Microsoft upgrades Windows 11 backup/restore: "Restore summary" makes migrating to a new PC more transparent
  • Microsoft accelerates the modernization of Windows 11, and dialogs such as "Services" will bid farewell to their outdated interfaces

The translation is machine-generated and individual terms may be off. Nothing is rewritten or cut; the original is authoritative.

Published by IT之家
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗