The process osd.exe ist blocking my Robot

[wael_kaabi (Sa7bouch)]

Hello everyone ,

I run my UiPath processes from Virtual machine!.
In some cases UiPath has problems when the process “osd.exe” (On-Screen Display Application) is running (which is running by default on my VM).
My workaround at the moment is to kill this process before starting the robot.

Does anyone know about this issue? What is the reason for the problems occuring in UiPath? and how can I solve it ?

Thanks in advance!
Wael

[marian.platonov]

It appears that UiPath is encountering an issue with sending a hotkey to the ‘SysListView32’ element due to the current foreground window being blocked by a process called ‘osd.exe.’

This error is of type UiPath.Core.ElementOperationException, which occurs when the target UI element cannot be accessed or interacted with during the process execution.

To resolve this issue, consider the following steps:

1. Ensure that the ‘osd.exe’ process is not essential for the target application and can be safely terminated or disabled. If it’s not necessary, you can close or end the process manually from the Task Manager or by using a kill process activity in your UiPath workflow.
2. Verify that your selectors are accurate and correctly reference the ‘SysListView32’ element to ensure proper targeting.
3. Add retry mechanisms in your workflow to manage such cases. If the target application is temporarily not accessible, the workflow can retry a few times before throwing an error.
4. If the ‘osd.exe’ process is essential, see if there is an alternative way to interact with the desired UI element or use a different approach in your automation.

By addressing the issue with the ‘osd.exe’ process and ensuring accurate targeting of the ‘SysListView32’ element, you should be able to resolve the UiPath.Core.ElementOperationException error.