Newshot Microsoft tightens PowerShell security checks in November Windows 11 update, non-compliant scripts will fail
In its November 2026 Patch Tuesday cumulative update for Windows 11, Microsoft tightened PowerShell security checks, so some older PowerShell scripts that do not meet the new requirements will fail to run. Microsoft also confirmed that the security update released on November 10, 2026 introduced an activation and license management issue, with some devices potentially returning error 0x80041008 in enterprise KMS configurations. Separately, Microsoft announced plans to progressively strengthen NTLM authentication, requiring Windows clients to provide NTLM message signing on all connections and to reject unsigned connections starting in May 2027. Windows Latest reported on November 13 that Microsoft intentionally delays loading some Windows 11 startup apps to prevent multiple programs from c
How this story unfolded
Key points10 items Model summary · ordered by when the evidence was published
- Point 01 11/12, 13:10
Microsoft will require Windows clients to provide NTLM message signing on all connections
Based on 1 - Point 02 11/12, 13:10
Microsoft plans to reject unsigned NTLM connections from May 2027
Based on 1 - Point 03 11/12, 13:10
The NTLM changes are intended to reduce relay attack risk
Based on 1 - Point 04 11/12, 14:24
Windows 11's November Patch Tuesday cumulative update tightened PowerShell security checks
Based on 1 - Point 05 11/12, 14:24
Some older PowerShell scripts that fail the new checks will stop working
Based on 1 - Point 06 11/13, 08:31
Microsoft confirmed the November 10, 2026 security update introduced an activation and license management issue
Based on 1 - Point 07 11/13, 08:31
Affected enterprise devices may return error 0x80041008 in KMS configurations
Based on 1 - Point 08 11/13, 13:02
Microsoft intentionally delays some Windows 11 startup apps to avoid resource competition
Based on 1 - Point 09 11/13, 13:02
Two registry edits cut the startup wait from 150 seconds to 30 seconds
Based on 1 - Point 10 11/13, 14:26
Microsoft confirmed November updates can prevent some Word documents from printing on Windows 11 and Windows 10
Based on 1
ReportsBy publish time · newer further down
- November 12, 2026 · Thu
- Start
Windows NTLM security change: Microsoft plans to reject unsigned connections from May 2027 to reduce relay attack risk
AI overview Microsoft announced that it will gradually strengthen NTLM authentication security via Windows updates, requiring Windows clients to provide NTLM message signing on all connections
IT之家 Original ↗ - +1h
Microsoft tightens PowerShell security checks in November Windows 11 update, non-compliant scripts will fail
AI overview 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 p
IT之家 Original ↗ - November 13, 2026 · Fri
- +19h
Microsoft Acknowledges Activation Commands Failing After November Windows 11 Update, Enterprise KMS Configuration May Return Error 0x80041008
AI overview Microsoft has confirmed that the Windows security update released on November 10, 2026 introduced a new activation and license management issue, with some devices possibly encounte
IT之家 Original ↗ - +24h
Microsoft intentionally delays Windows 11 startup app loading to prevent multiple apps from competing for system resources; editing two registry entries cuts the wait from 150 seconds to 30 seconds
AI overview According to Windows Latest on November 13, Microsoft deliberately delayed the loading of some startup apps in Windows 11 to avoid multiple programs consuming too many system resou
IT之家 Original ↗ - +1d 1h
Microsoft confirms some Word documents cannot be printed after installing November updates on Windows 11/Windows 10
AI overview Microsoft has acknowledged a bug in the November update for Windows 11 that can prevent some Word documents from printing. The issue is triggered when an image in a document has a
IT之家 Original ↗ - Still developing · later reports will keep extending this axis
Some legacy PowerShell scripts may fail, some enterprise KMS activations may return error 0x80041008, and unsigned NTLM connections will be rejected starting in May 2027.