Hi,
I'm afraid, this kind of issue is not something that could be solved here. Definitely not without seeing, at very least, a Ranorex snapshot of the problematic element(s) and a complete xpath that typically takes too long to find. Also, are you using most recent Ranorex 9.3.1?
If you cannot share the snapshot/xpath, try to contact Ranorex support and request a remote session, so they can analyze the problem on your machine. Seriously, there is nothing anyone here can do or suggest without seeing your environment, test suite and app under test.
BTW, I see you've asked almost identical questions in the past...
https://www.ranorex.com/forum/viewtopic ... 585#p59585
https://www.ranorex.com/forum/viewtopic ... 683#p57683
In both cases, you were using an obsolete Ranorex version and you failed to post, at very least, Ranorex snapshot of the app under test. I think your best hope is to update Ranorex and then, if problem still exists, contact Ranorex support.