This article describes the known issues that occur when you use the spelling checker in the Microsoft .NET 4.6.1 in Windows 8.1 or a newer version of Windows.
Note The following information does not apply to Windows Vista SP2, Windows 7, or Windows 8.
Symptoms
To support the spelling checker in additional languages, the spelling checker in Windows Presentation Foundation (WPF) in Windows 8.1 and newer versions is now updated. However, you may experience the following known issues when you use the spelling checker in the .NET Framework 4.6.1:
-
When a Feature On Demand (FoD) language package is installed in Windows, the corresponding language is supported for the spelling check. However, not all languages that have an FoD language package are supported for the spelling check. Only the languages that the corresponding FoD language package has installed in Windows are supported.
Note When you add a specific language keyboard, Windows 10 automatically downloads and installs the corresponding FoD package from Windows Update. This process may require connectivity to the Internet, and may take several hours to finish. For more information, see the instructions for Windows 8.1. -
The spelling checker isn't supported for Partial Trust conditions.
-
Custom dictionaries no longer function as per-control dictionaries starting with the .NET Framework 4.6.1. These dictionaries exhibit the following behavior:
-
Dictionaries that are registered by any TextBox or RichTextBox control affect all other instances of those controls within the application.
-
Dictionaries that are registered by any TextBox or RichTextBox control affect controls in other processes that have the spelling checking enabled.
-
-
The system will impose a limit on the cumulative size of custom dictionaries that can be registered in a user session. When this limit is reached, the underlying spell-checking system (which is part of Windows) silently ignores additional requests for registration of custom dictionaries.
