Windows 10 22H2 · 1.0

Enter “0” to disable Logon Script Delay. [removed: ] This policy setting allows you to configure how long the Group Policy client waits after logon before running scripts. [removed: ] By default, the Group Policy client waits five minutes before running logon scripts. This helps create a responsive desktop environment by preventing disk contention. [removed: ] If you enable this policy setting, Group Policy will wait for the specified amount of time before running logon scripts. [removed: ] If you disable this policy setting, Group Policy will run scripts immediately after logon. [removed: ] If you do not configure this policy setting, Group Policy will wait five minutes before running logon scripts.

This security feature provides a means to override individual process MitigationOptions settings. This can be used to enforce a number of security policies specific to applications. The application name is specified as the Value name, including extension. The Value is specified as a bit field with a series of flags in particular positions. Bits can be set to either 0 (setting is forced off), 1 (setting is forced on), or ? (setting retains its existing value prior to GPO evaluation). The recognized bit locations are: PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE (0x00000001) Enables data execution prevention (DEP) for the child process PROCESS_CREATION_MITIGATION_POLICY_DEP_ATL_THUNK_ENABLE (0x00000002) Enables DEP-ATL thunk emulation for the child process. DEP-ATL thunk emulation causes the system to intercept NX faults that originate from the Active Template Library (ATL) thunk layer.[removed: ] PROCESS_CREATION_MITIGATION_POLICY_SEHOP_ENABLE (0x00000004) Enables structured exception handler overwrite protection (SEHOP) for the child process. SEHOP blocks exploits that use the structured exception handler (SEH) overwrite technique. PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON (0x00000100) The force Address Space Layout Randomization (ASLR) policy forcibly rebases images that are not dynamic base compatible by acting as though an image base collision happened at load time. If relocations are required, images that do not have a base relocation section will not be loaded. PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_ON (0x00010000) PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF (0x00020000) The bottom-up randomization policy, which includes stack randomization options, causes a random location to be used as the lowest user address. For instance, to enable PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE and PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON, disable PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF, and to leave all other options at their default values, specify a value of: ???????????????0???????1???????1 Setting flags not specified here to any value other than ? results in undefined behavior.[removed: ][added: ]

This policy setting allows an administrator to define the Direct Access connection to be considered a fast network connection for the purposes of applying and updating Group Policy.[removed: ][added: ]When Group Policy detects the bandwidth speed of a Direct Access connection, the detection can sometimes fail to provide any bandwidth speed information. If Group Policy detects a bandwidth speed, Group Policy will follow the normal rules for evaluating if the Direct Access connection is a fast or slow network connection. If no bandwidth speed is detected, Group Policy will default to a slow network connection. This policy setting allows the administrator the option to override the default to slow network connection and instead default to using a fast network connection in the case that no network bandwidth speed is determined.[removed: ][added: ]Note: When Group Policy detects a slow network connection, Group Policy will only process those client side extensions configured for processing across a slow link (slow network connection).[removed: ][added: ]If you enable this policy, when Group Policy cannot determine the bandwidth speed across Direct Access, Group Policy will evaluate the network connection as a fast link and process all client side extensions.[removed: ][added: ]If you disable this setting or do not configure it, Group Policy will evaluate the network connection as a slow link and process only those client side extensions configured to process over a slow link.[removed: ][added: ]

This policy directs Group Policy processing to skip processing any client side extension that requires synchronous processing (that is, whether computers wait for the network to be fully initialized during computer startup and user logon) when a slow network connection is detected.[removed: ][added: ]If you enable this policy setting, when a slow network connection is detected, Group Policy processing will always run in an asynchronous manner. Client computers will not wait for the network to be fully initialized at startup and logon. Existing users will be logged on using cached credentials,[removed: ][added: ]which will result in shorter logon times. Group Policy will be applied in the background after the network becomes available.[removed: ][added: ]Note that because this is a background refresh, extensions requiring synchronous processing such as Software Installation, Folder Redirection and Drive Maps preference extension will not be applied.[removed: ][added: ]Note: There are two conditions that will cause Group Policy to be processed synchronously even if this policy setting is enabled: 1 - At the first computer startup after the client computer has joined the domain. 2 - If the policy setting "Always wait for the network at computer startup and logon" is enabled.[removed: ][added: ]If you disable or do not configure this policy setting, detecting a slow network connection will not affect whether Group Policy processing will be synchronous or asynchronous.

This policy setting specifies how long Group Policy should wait for network availability notifications during startup policy processing. If the startup policy processing is synchronous, the computer is blocked until the network is available or the default wait time is reached. If the startup policy processing is asynchronous, the computer is not blocked and policy processing will occur in the background. In either case, configuring this policy setting overrides any system-computed wait times. If you enable this policy setting, Group Policy will use this administratively configured maximum wait time and override any default or system-computed wait time. If you disable or do not configure this policy setting, Group Policy will use the default wait time of 30 seconds on computers running Windows Vista operating system.[removed: ][added: ]

This policy setting allows you to turn off the ability to use a custom dictionary. If you enable this policy setting, you cannot add, edit, and delete words in the custom dictionary either with GUI tools or APIs. A word registered in the custom dictionary before enabling this policy setting [removed: is not][added: can continue to be] used for conversion. If you disable or do not configure this policy setting, the custom dictionary can be used by default. For Japanese Microsoft IME, [Clear auto-tuning information] works, even if this policy setting is enabled, and it clears self-tuned words from the custom dictionary. This policy setting is applied to Japanese Microsoft [removed: IME and Simplified Chinese Microsoft Pinyin.][added: IME. Note: Changes to this setting will not take effect until the user logs off.]

This policy setting allows you to turn off history-based predictive input. If you enable this policy setting, history-based predictive input is turned off.[removed: ][added: ]If you disable or do not configure this policy setting, history-based predictive input is on by default. This policy setting applies to Japanese Microsoft IME only. Note: Changes to this setting will not take effect until the user logs off.

This policy setting allows you to turn off Internet search integration. [removed: If you enable this policy setting, you cannot add a new search integration configuration file. A search integration configuration file that was installed before enabling ][added: Search integration includes both using Search Provider (Japanese Microsoft IME) and performing bing search from predictive input for Japanese Microsoft IME. If you enable ]this policy [removed: setting is not used.][added: setting, you cannot use search integration.] If you disable or do not configure this policy setting, the search integration function can be used by default. This policy setting applies to Japanese Microsoft [removed: IME, Simplified Chinese Microsoft Pinyin, and Traditional Chinese New Phonetic.][added: IME. Note: Changes to this setting will not take effect until the user logs off.]

This policy setting allows you to turn off Open Extended Dictionary. If you enable this policy setting, Open Extended Dictionary is turned off. You cannot add a new Open Extended Dictionary. For Japanese Microsoft IME, an Open Extended Dictionary that is added before enabling this policy setting is not used for conversion. [removed: For Simplified Chinese Microsoft Pinyin, an Open Extended Dictionary that is added before enabling this policy setting is still used for conversion. ]If you disable or do not configure this policy setting, Open Extended Dictionary can be added and used by default. This policy setting is applied to Japanese Microsoft [removed: IME and Simplified Chinese Microsoft Pinyin.][added: IME.]

This policy setting allows you to turn off saving the auto-tuning result to file. If you enable this policy setting, the auto-tuning data is not saved to file.[removed: ][added: ]If you disable or do not configure this policy setting, auto-tuning data is saved to file by default. This policy setting applies to Japanese Microsoft IME only.

This policy setting controls the cloud candidates feature, which uses an online service to provide input suggestions that don't exist in a PC's local dictionary. If you enable this policy setting, the functionality associated with this feature is turned on, the user's keyboard input is sent to Microsoft to generate the suggestions, and the user won't be able to turn it off.[removed: ][added: ]If you disable this policy setting, the functionality associated with this feature is turned off, and the user won't be able to turn it on.[removed: ][added: ]If you don't configure this policy setting, it will be turned off by default, and the user can turn on and turn off the cloud candidates feature. This Policy setting applies to Microsoft CHS Pinyin IME and JPN IME.

This policy setting allows you to turn on logging of misconversion for the misconversion report. If you enable this policy setting, misconversion logging is turned on. If you disable or do not configure this policy setting, misconversion logging is turned off.[removed: ][added: ]This policy setting applies to Japanese Microsoft IME and [removed: Simplified][added: Traditional] Chinese [removed: Microsoft Pinyin.][added: IME.]