Okta Verify for Windows release notes

Generally Available features

Improved screen reader behavior in Okta Verify

This enhancement improves the way screen readers interact with static text within the Okta Verify app. This change provides a better experience for users who rely on accessibility tools.

Device sessions persist after failed desktop sign-in attempts

Okta Verify no longer ends the device session when a desktop sign-in attempt fails. Previously, any failed attempt, such as an incorrectly entered password, ended the session even if the next attempt succeeded. Users now keep their existing device session.

Fixes

• Okta Verify for Windows timed out on some devices under certain conditions such as a heavy network load. This caused unexpected MFA prompts, trusted app filter failures, or unexpected prompts for other factors. (OKTA-1221697, OKTA-1254966, OKTA-1253459)

• When Okta Verify was installed with the DeviceHealthOptions variable set to Disabled, the device health shield still appeared until the device restarted or the Okta services were restarted. (OKTA-1232407)

• Okta Verify failed to launch if the user account was restricted from reading or enumerating the plugin manifest files. (OKTA-1244223)

• After the device access certificate was rotated, the admin recovery secret couldn't be rotated. (OKTA-1275284)

• When users signed in with a device recovery PIN, they didn't receive the admin recovery message on devices configured for passwordless with a stored password. (OKTA-1276706)

• Okta Verify for Windows sometimes displayed a Registration failed error when an org used a custom domain, even though the device registration had succeeded. (OKTA-1278053)

• This release also includes internal fixes and minor usability improvements.