Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Windows 11: 22H2 · 3.0 to 26H2 · 1.0

191 new settings, 113 changed, 1 removed since 22H2 · 3.0. 4 retained releases apart.

Changes that matter

305 settings · compared with 22H2 · 3.0
  • User · Control Panel\Regional and Language Options
    Registry key: Software\Policies\Microsoft\Control Panel\Desktop · Value name: Not specified
    • A choice in “Restrict users to the following language” is renamed [was: Traditional Chinese (Hong Kong) (zh-HK)][now: Traditional Chinese (Hong Kong SAR) (zh-HK)]
      Registry key: Software\Policies\Microsoft\Control Panel\Desktop · Value name: PreferredUILanguages
  • Computer · Windows Components\App Privacy
    Registry key: Software\Policies\Microsoft\Windows\AppPrivacy · Value name: Not specified
  • Computer and user · Windows Components\Internet Explorer\Internet Control Panel\Advanced Page
    Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: Not specified
    • A choice in “Secure Protocol combinations” is renamed [was: Only use SSL 2.0 (8)][now: [Obsolete] Only use SSL 2.0 (8)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0 and SSL 3.0 (40)][now: [Obsolete] Use SSL 2.0 and SSL 3.0 (40)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0 and TLS 1.0 (136)][now: [Obsolete] Use SSL 2.0 and TLS 1.0 (136)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, and TLS 1.0 (168)][now: [Obsolete] Use SSL 2.0, SSL 3.0, and TLS 1.0 (168)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0 and TLS 1.1 (520)][now: [Obsolete] Use SSL 2.0 and TLS 1.1 (520)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, and TLS 1.1 (552)][now: [Obsolete] Use SSL 2.0, SSL 3.0, and TLS 1.1 (552)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, TLS 1.0, and TLS 1.1 (648)][now: [Obsolete] Use SSL 2.0, TLS 1.0, and TLS 1.1 (648)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1 (680)][now: [Obsolete] Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1 (680)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0 and TLS 1.2 (2056)][now: [Obsolete] Use SSL 2.0 and TLS 1.2 (2056)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, and TLS 1.2 (2088)][now: [Obsolete] Use SSL 2.0, SSL 3.0, and TLS 1.2 (2088)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, TLS 1.0, and TLS 1.2 (2184)][now: [Obsolete] Use SSL 2.0, TLS 1.0, and TLS 1.2 (2184)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.2 (2216)][now: [Obsolete] Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.2 (2216)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, TLS 1.1, and TLS 1.2 (2568)][now: [Obsolete] Use SSL 2.0, TLS 1.1, and TLS 1.2 (2568)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, TLS 1.1, and TLS 1.2 (2600)][now: [Obsolete] Use SSL 2.0, SSL 3.0, TLS 1.1, and TLS 1.2 (2600)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, TLS 1.0, TLS 1.1, and TLS 1.2 (2696)][now: [Obsolete] Use SSL 2.0, TLS 1.0, TLS 1.1, and TLS 1.2 (2696)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
    • A choice in “Secure Protocol combinations” is renamed [was: Use SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2 (2728)][now: [Obsolete] Use SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2 (2728)]
      Registry key: Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings · Value name: SecureProtocols
  • Computer and user · Windows Components\Internet Explorer
    Registry key: Software\Policies\Microsoft\Internet Explorer\Main · Value name: AllowLegacyURLFields
  • Computer and user · Windows Components\Internet Explorer
    Registry key: Software\Policies\Microsoft\Internet Explorer\Main · Value name: JScriptReplacement
    • Renamed Replace JScript by loading JScript9Legacy in place of [removed: JScript via MSHTML/WebOC.][added: JScript.]
    • Description This policy setting specifies whether JScript or JScript9Legacy is [removed: loaded for MSHTML/WebOC/MSXML/Cscript based invocations.][added: loaded.] If you enable this policy [removed: setting,][added: setting or not configured,] JScript9Legacy will be loaded in situations where JScript is instantiated. If you disable this policy, then JScript will be utilized.[removed: If this policy is left unconfigured, then MSHTML will use JScript9Legacy and MSXML/Cscript will use JScript.]
      Whole description, marked

      This policy setting specifies whether JScript or JScript9Legacy is [removed: loaded for MSHTML/WebOC/MSXML/Cscript based invocations.][added: loaded.] If you enable this policy [removed: setting,][added: setting or not configured,] JScript9Legacy will be loaded in situations where JScript is instantiated. If you disable this policy, then JScript will be utilized.[removed: If this policy is left unconfigured, then MSHTML will use JScript9Legacy and MSXML/Cscript will use JScript.]

  • Computer · System\Kerberos
    Registry key: Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters · Value name: CloudKerberosTicketRetrievalEnabled
    • Supported on At least Windows Server [removed: 2019 Version 2004,][added: 2019,] Windows 10 Version 2004
  • Computer · System\Kerberos
    Registry key: Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters · Value name: DelegatedMSAEnabled
  • Computer · System\LAPS
    Registry key: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\LAPS · Value name: AutomaticAccountManagementEnabled
  • Computer · System\LAPS
    Registry key: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\LAPS · Value name: [was: PwdExpirationProtectionEnabled][now: PasswordExpirationProtectionEnabled]
    • The policy's own registry value [was: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\LAPS\PwdExpirationProtectionEnabled][now: SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\LAPS\PasswordExpirationProtectionEnabled]
    • Option “PwdExpirationProtectionEnabled” removed [removed: ]
    • New option “PasswordExpirationProtectionEnabled” [added: ]
  • Computer · Windows Components\App Privacy
    Registry key: Software\Policies\Microsoft\Windows\AppPrivacy · Value name: Not specified
  • Computer · Windows Components\App Privacy
    Registry key: Software\Policies\Microsoft\Windows\AppPrivacy · Value name: Not specified
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: AuditClientDoesNotSupportEncryption
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: AuditInsecureGuestLogon
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: EnableAuthRateLimiter
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\Bowser · Value name: EnableMailslots
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: EnableSMBQUIC
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: Not specified
  • Computer · Network\Lanman Server
    Registry key: Software\Policies\Microsoft\Windows\LanmanServer · Value name: Not specified
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: Not specified
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: AuditInsecureGuestLogon
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: AuditServerDoesNotSupportEncryption
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: AuditServerDoesNotSupportSigning
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: BlockNTLM
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: EnableAlternativePorts
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\NetworkProvider · Value name: EnableMailslots
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: Not specified
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: Not specified
  • Computer · Network\Lanman Workstation
    Registry key: Software\Policies\Microsoft\Windows\LanmanWorkstation · Value name: RequireEncryption
  • Computer · System\Local Security Authority
    Registry key: [was: System\CurrentControlSet\Control\Lsa][now: Software\Policies\Microsoft\Windows\System] · Value name: Not specified
    • Description … current setting in the registry, LSA will run as protected process for [added: all ]clean installed, HVCI capable, client [removed: SKUs that are domain or cloud domain joined devices.][added: SKUs.] This configuration is not UEFI locked. This can be overridden if the …
      Whole description, marked

      This policy controls the configuration under which LSASS is run. If you do not configure this policy and there is no current setting in the registry, LSA will run as protected process for [added: all ]clean installed, HVCI capable, client [removed: SKUs that are domain or cloud domain joined devices.][added: SKUs.] This configuration is not UEFI locked. This can be overridden if the policy is configured. If you configure and set this policy setting to "Disabled", LSA will not run as a protected process. If you configure and set this policy setting to "EnabledWithUEFILock," LSA will run as a protected process and this configuration is UEFI locked. If you configure and set this policy setting to "EnabledWithoutUEFILock", LSA will run as a protected process and this configuration is not UEFI locked.

    • The policy's own registry value [was: System\CurrentControlSet\Control\Lsa][now: Software\Policies\Microsoft\Windows\System]
    • Option “Configure LSA to run as a protected process” writes [was: System\CurrentControlSet\Control\Lsa\RunAsPPL][now: Software\Policies\Microsoft\Windows\System\RunAsPPL]
      Registry key: [was: System\CurrentControlSet\Control\Lsa][now: Software\Policies\Microsoft\Windows\System] · Value name: RunAsPPL
  • Computer · System\Net Logon\DC Locator DNS Records
    Registry key: Software\Policies\Microsoft\Netlogon\Parameters · Value name: BlockNetbiosDiscovery
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 15:50 UTC · 273 of 275 readable · 271 fully read · documentation 469/469 current