Knowledge Base

Problem

EthoVision opens and runs correctly for the primary (administrator) Windows user account but fails to open or completes a 'configuring' step when a different Windows user (e.g., a colleague or resident) logs in and attempts to run the software. The secondary user does not have administrator privileges.

Details

When a new Windows user profile opens EthoVision for the first time, Windows performs final per-user setup steps (registry entries, application configuration) that require elevated privileges. Without admin rights, this process fails silently or produces an error, and EthoVision does not complete initialization for that user. The EthoVision license is tied to the computer, not to a specific Windows account, so the license itself is not the cause. Affects EthoVision XT 19 and likely other versions on shared or institutional PCs with restricted accounts.

Solution

1. Confirm that the EthoVision license is computer-locked (tied to the PC), not to a specific Windows account. Any Windows user on the PC can use the license once the software is properly initialized for their profile.
2. For the first launch under a new Windows user account, have an IT administrator either: (a) temporarily grant that user local admin rights, launch EthoVision once to complete per-user setup, then remove the elevated rights; or (b) have an admin log in as that user and launch EthoVision once on their behalf.
3. On domain/Active Directory networks with strict security policies, involve the IT team to pre-configure the required registry keys and application settings for all user profiles that will run EthoVision.
4. After the first successful launch under the new profile, subsequent launches do not require admin rights.
5. Admin rights are required for installation of EthoVision XT 19 but not for routine operation once properly initialized.