Issue
- Allow screen-reading software (like NVDA, JAWS, Narrator) to access GUI of ESET security products
- Self-defense blocks access to egui.exe
- Create a new HIPS rule to allow access to egui.exe
Solution
Choose one of the solutions available:
- Install with XML settings—ESET is not installed yet
- Import an XML file—ESET is already installed
- Create a new HIPS rule—ESET is already installed
Install with XML settings—ESET is not installed yet
- Download your ESET security product to an installation folder.
- Download the configuration file.
- Extract .zip archive to the installation folder and rename screen_readers_config.xml to cfg.xml.
- Make sure cfg.xml is placed in the same folder as the installation file.
- Install.
- After installation, verify that the HIPS rule named "Allow screen readers to access Egui" has been created in Setup > Advanced setup > Detection engine > HIPS > Rules.
Figure 1-1
Import an XML file—ESET is already installed
Use only if you did not import XML settings during installation.
- Download the configuration file and extract the .zip archive.
- Import ESET configuration settings using the downloaded file screen_readers_config.xml.
Create a new HIPS rule—ESET is already installed
Use only if you do not prefer import XML settings during or after installation.
- Create a following HIPS rule based on this guide:
- Name of the rule: "Allow screen readers to access EGUI"
- Enabled: yes
- Action: Allow
- Operations affecting: Applications
- Logging severity: None
- Source applications: All applications
(you can limit "Source applications" to your screen-reading software only) - Application operations: All application operations
- Specific applications: %InstallDir%egui.exe
- Enforce the policy to client workstations (ESET endpoint products only).