Windows Eye Tracking Registry Settings Location

This article explains the exact Windows Registry locations used to store active configurations for system-wide eye tracking and Eye Control accessibility tools. In Windows 10 and Windows 11, user preferences, dwell times, calibration states, and interface behaviors are primarily stored under dedicated user-specific keys within the Windows Registry Editor (Regedit).

Primary User Configuration Path

The active configuration for the current user’s Eye Control accessibility tools is located at:

HKEY_CURRENT_USER\Software\Microsoft\EyeControl

This key contains the core settings for the Eye Control launchpad, dwell time configurations, text-to-speech settings, and on-screen keyboard interaction modes. Key values stored here include:

• DwellTime: Controls the duration (in milliseconds) a user must fixate on an element before a click is registered.
• Smoothing: Defines the algorithmic smoothing applied to gaze data to reduce jitter.
• LaunchPadPosition: Stores the screen coordinates where the Eye Control toolbar appears.

Gaze Interaction and Input Settings

For Windows Gaze Input APIs and global pointer interaction settings, configuration values are stored under:

HKEY_CURRENT_USER\Software\Microsoft\Input\Gaze

This location manages whether gaze-based cursor feedback is visible on-screen and how gaze coordinates interact with standard Windows UI elements.

System-Wide and Hardware Configurations

For device-level defaults and hardware integration policies across all accounts, configuration data resides under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EyeControl

Additionally, individual eye tracker drivers (such as Tobii or other supported eye tracking hardware) register system-level services and calibration data under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ (prefixed by the specific hardware vendor’s service name).

To modify these values, open regedit.exe, navigate to the relevant key path, and edit the corresponding DWORD or String values while the eye tracking hardware is idle to ensure changes take effect upon the next session restart.