Ranorex Forum

When we try to run tests using GDI capture on a Windows 10 VM we get the following error message:
"[Warn ][GDI]: Failed to instrument application: Failed to retrieve handle to bootstrapper library."

This causes the tests to fail.

Is there a way to solve this issue?

Ranorex 7.1.0
Windows 10

Hello coertmetz,

Welcome to the Ranorex forum!

I'm afraid we are not aware of such an issue in the latest version of Ranorex. I would suggest contacting [email protected] directly in order we can analyze this issue in detail.

We look forward to hearing from you.

Best Regards,
Johannes

We discovered that MSBuild could not find the .net framework. We were able to fix this which made the warning disappear. However, GDI raw text support is still not working, even though it has been enabled for the GUI element we want to track.

Hello coertmetz,

Did GDI raw text recognition for this UI element work in previous versions of Ranorex? It would be great if you could get in touch with us by email. Probably we need to schedule a short remote session in order to analyze the issue.

We look forward to hearing from you.

Best Regards,
Johannes

Any more information on this issue? I emailed support about the same thing but they haven't been able to figure it out.

I had this issue a little while ago.

It seemed like a windows update caused it, but I am not quite sure. I do know it happened just after the VM "automatically updated" to the Creators Update and it was flaky from that point on until I had the time to try and fix it.

To fix it I did the following:
1. Uninstall Ranorex
2. Turn off the 3.5 .NET Framework components in the control panel
3. Restart the VM
4. Turn the 3.5 framework back on
5. Reinstall Ranorex

I don't know if this is the only solution, but it worked for me.

jbeeson wrote:Any more information on this issue? I emailed support about the same thing but they haven't been able to figure it out.

Hello Jbeeson,

Regarding your support case, it appears we have not received a response with the requested debug/log files from your colleague's machine. Please provide these files at your earliest convenience to assist with debugging this issue. Thank you in advance!

Cheers,
Ned

We had the same problem and the solution from BSullivan worked like a charm for us.
In our case the .Net 3.5 Framework was completely turned off in favor of the 4.7 one, so the only difference was that we didn't have to turn the 3.5 Framework off.