Is it being run and failing when you are watching it run, or is this only failing as unattended?
If you are watching it and it is failing, then it could be challenging to solve without actually looking at it directly. But, I would say ensure the images are on the screen and you are looking in an element that contains that image (if you leave selector blank, it may take longer to find the image too so make sure TimeoutMS is long enough). I’m not quite sure what the problem would be in this scenario.
However, if this problem is occurring while running unattended where you don’t watch it, there could be a difference in resolution and color depth, which could also fluctuate between different operating systems. In this scenario, I would suggest changing the Robot settings for resolution to match what the environment where you developed the Find Image. You can do this by editing the Robot in Orchestrator. Generally, you would use 1920 w 1080 h 32 depth.