6.1.0: Spy complains WPF-limitation under Win 10 Pro (1607)

[BCTest]

Hello,

after the anniversary update of Windows WPF-UI-identification is limited. Before this update the identification worked proper.
.NET 3.5, as mentioned in Message-Help-URL seems to be installed.
What can we do to use WPF-identification in Win 10 Pro (1607) again?

WPF.png

[BCTest]

Hi,

I forgot to mention: this application seems to be build with .NET 2.0 and WPF-Toolkit 3.5 (this is not our application - we only want to test sending and receiving data between our programme and this application).

Th.

[RobinHood42]

Hi,

I'm a little bit confused because the snapshot shows WPF elements. I can see the instrumentation warning, but this is just a warning, right? Maybe the instrumentation warning comes from another application, which is running at the same time?
Please correct me if I'm wrong, but the object recognition seems to work.

Cheers,
Robin

[BCTest]

Hi,

I'm confused, too.
The warning flashes when I hover the mouse over the login form, so I think, the warning is corresponding to this form.
Also a lot of elements can be accessed but some not, like the TextPart in the ComboBox "cbxUsernames". As you can see in the screenshot I added the element "Name" by using Ranorex-Spy. This element was always accessed by Ranorex before I installed the anniversary update on the computer. After the update this Ranorex-Path doesn't work any more.

WPF.png

It looks like a setting in Windows is missing or is false but which one?

Regards,
Thomas

[BCTest]

I don't know what to try next: Reinstalling Ranorex-Studio didn't change this behaviour.

Regards,
Th.

[BCTest]

Hi,

the Support-team solved my problem: I didn't restart the computer during the de- and re-install process. Deinstalling, booting and reinstalling the Studio solved the problem.
Looks like the Windows update alter some settings.

Thanks.