4 weeks ago
Hello everyone,
Today we're facing a problem. We had a lot of elements mapped with accessibility mode in a desktop application, but after updating some Windows KBs, it stopped working. The option is still available, but it can't find anything with accessibility mode. Is there anything that can fix this, or is it a bug introduced by the new KB?
KB5041773
KB5041961
KB5041576
Answered! Go to Answer.
4 weeks ago
We've seen in the past after pushing O/S updates or patches to Runtime Resources, customers may encounter issues with AA Mode such as the following:
Sometimes this issue can be easily fixed by re-registering the OLEACC.DLL file (usually located here: 'C:\Windows\System32' directory).
However, if re-registering doesn't help to fix the issue, then your next option is to delete some registry keys.
Important: Deleting registry keys should only be done by your IT team and it's always advisable to backup the registry before making any such changes.
The following registry key has to be deleted because after the upgrade, the Accessibility COM object is sometimes unable to pick the right Bit-ness version (i.e. 64- or 32-bit) to work with, hence the AA spy issue:
[HKEY_CLASSES_ROOT\WOW6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
Remember to reboot machine after deleting the key.
4 weeks ago
We've seen in the past after pushing O/S updates or patches to Runtime Resources, customers may encounter issues with AA Mode such as the following:
Sometimes this issue can be easily fixed by re-registering the OLEACC.DLL file (usually located here: 'C:\Windows\System32' directory).
However, if re-registering doesn't help to fix the issue, then your next option is to delete some registry keys.
Important: Deleting registry keys should only be done by your IT team and it's always advisable to backup the registry before making any such changes.
The following registry key has to be deleted because after the upgrade, the Accessibility COM object is sometimes unable to pick the right Bit-ness version (i.e. 64- or 32-bit) to work with, hence the AA spy issue:
[HKEY_CLASSES_ROOT\WOW6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
Remember to reboot machine after deleting the key.
3 weeks ago
Hi, Carlos_Medina,
can you check that you are attached to the right instance of the application?
Regards
Zdenek
3 weeks ago
Thanks, it was solved by deleting the registry keys and restarting the computer.