/
/

How to Enable or Disable Typing Insights in Windows 11

by Angelo Salandanan, IT Technical Writer
How to Enable or Disable Typing Insights in Windows 11 blog banner image

Instant Summary

This NinjaOne blog post offers a comprehensive basic CMD commands list and deep dive into Windows commands with over 70 essential cmd commands for both beginners and advanced users. It explains practical command prompt commands for file management, directory navigation, network troubleshooting, disk operations, and automation with real examples to improve productivity. Whether you’re learning foundational cmd commands or mastering advanced Windows CLI tools, this guide helps you use the Command Prompt more effectively.

Typing Insights in Windows 11 allows you to view data related to your typing behavior, which can be leveraged to improve your workflow. However, if privacy or performance is a concern or you simply want a cleaner experience, you can enable or disable this feature with the methods outlined in this guide.

Methods for changing Typing Insights preferences

Use the table to choose and quickly navigate to your preferred activation steps.

📌 Prerequisites:

  • Some methods may require system and network access.
  • Active enterprise settings or policies may restrict changes.

Choose a Method

💻

Best for Individual Users 

💻💻💻

Best for Enterprises

Method 1: Windows Settings
Method 2: Windows Registry
Method 3: PowerShell script
Method 4: Group Policy

💡 Tip: Check out the Things to look out for section to optimize your action plan and manage risks.

Method 1: Configure Typing Insights via Settings

This method is best for self-service or Remote Desktop Protocol activation.

📌 Use cases: For general configuration and RDP

  1. Open Settings from Search 🔎 or press Win + I.
  2. Navigate to Time & Language → Typing → Typing Insights.
  3. Toggle the on and off switch to manage your preferences.

Open Settings and Navigate to Time & Language, Typing, Typing Insights.

The changes made via Windows Settings will not require administrative privileges and will only apply per user.

Method 2: Configure Typing Insights via Registry

Advanced users can use the Windows Registry to configure personal or managed devices.

📌 Use cases: For systems without GPO access; setting policies not supported via GPO

  1. Press Win + R, type regedit, and tap OK to open the Registry Editor.
  2. Navigate to or copy and paste the following path to the Registry address bar. If the path is incomplete, create the required key.
    • HKEY_CURRENT_USER\Software\Microsoft\Input\Settings
  3. Modify or create the InsightsEnabled DWORD (32-bit) value.
  4. Open it and set its Value data according to your preferences.
    • = Enable Typing Insights
    • 0 = Disable Typing Insights
  5. Close the Registry Editor.

⚠️ Warning: Editing the registry can cause system issues. Create a registry backup before proceeding.

Method 3: Configure Typing Insights via a PowerShell script

PowerShell scripts are incredibly convenient for task automation and software deployment.

📌 Use case: For automation and RMM scripting.

  1. Use Search 🔎 to open Terminal → PowerShell → Run as administrator.
  2. Run the following command:
    • To enable Typing Insights:
      Set-ItemProperty -Path “HKCU:\Software\Microsoft\Input\Settings” -Name “InsightsEnabled” -Value 1 -Type DWord
    • To disable it:
      Set-ItemProperty -Path “HKCU:\Software\Microsoft\Input\Settings” -Name “InsightsEnabled” -Value 0 -Type DWord
  3. Identify the PackageFullName of the speech pack language you intend to uninstall.
  4. Restart the device to apply the changes.

💡 Note: This script may run or fail without displaying any confirmation or prompt. To confirm if changes have been applied successfully, check the corresponding Registry keys or system settings.

Method 4: Configure Typing Insights via Local Policy

The Local Group Policy Editor is exclusive to Windows 11 Pro, Enterprise, or Education editions. If a conflict is detected between two policies, the local policy will be overruled by Group Policy in Active Directory.

📌 Use cases: For enterprise and system-wide deployments

📌 Prerequisites: Administrative Templates for Windows 11 must be installed.

  1. Press Win + R, type gpedit.msc, and tap OK to open Local Group Policy Editor.
  2. Navigate to Computer Configuration → Administrative Templates → Windows
  3. Components → Text Input.
  4. Double-click the Improve inking and typing recognition policy.
  5. Set to Enabled or Disabled based on your preference.

You can run the gpupdate /force command to apply the changes immediately. Otherwise, the new settings will be applied on the next interval.

💡 Tip: Watch this GPUpdate video demonstration for a visual reference.

⚠️ Things to look out for when configuring Typing Insights

Missing something? Consider these scenarios and tips for handling errors, preventing system issues, and reinforcing policies.

Risks Potential Consequences Reversals
GPO conflicts with local settings GPO overrides user changes The GPO setting must be changed to re-enable.
Disabling Typing Insights mid-session Changes may not take effect until the next sign-in. Save your work and restart the computer to confirm the changes.

If Typing Insights remains active after updating your preferences, ensure that no conflicting policies override the setting. You can also go to the Registry and confirm that the InsightsEnabled value reflects the desired configuration.

Best practices for managing Typing Insights

Preventing the collection of typing statistics by disabling Typing Insights is a good way to manage user data and privacy. Along with this, you can consider switching off Personal inking and typing dictionary to prevent cloud-based text learning, which you can find via Settings → Privacy & security → Inking & typing personalization.

For deployment strategies, Windows Settings is a straightforward method for managing preferences. Otherwise, Windows Registry and PowerShell both provide more flexibility for advanced users and IT managers. GPO, meanwhile, offers the best path for enforcing policies across the IT network and for managing endpoints en masse.

Related topics:

FAQs

No. Text input suggestions and corrections still function unless turned off separately. Navigate to Time & Language → Typing and toggle Autocorrect misspelt words on or off to manage your preferences.

Typing Insights in Windows 11 devices is enabled by default upon initial setup.

You can edit the Registry or use a Group Policy to deploy the new settings for all users on a device.

You might also like

Ready to simplify the hardest parts of IT?

NinjaOne Terms & Conditions

By clicking the “I Accept” button below, you indicate your acceptance of the following legal terms as well as our Terms of Use:

  • Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms.
  • Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party.
  • Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library belonging to or under the control of any other software provider.
  • Warranty Disclaimer: The script is provided “as is” and “as available”, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations.
  • Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks.
  • Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script.
  • EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).