Page 1 of 1

Ranorex 5.3 and Windows 10

Posted: Thu Feb 16, 2017 8:17 am
by Bernd Rausch
Hello,
are there any known problems with Ranorex 5.3 and Windows 10 (Update 1607)? Ranorex Version 5.3.5 was released at December 2015, so I assume it works with Win10 in general. But we have all kind of problems with a WPF application, where tests are green on a Win7 machine and randomly freeze or fail on Win10 (Ranorex freezes, not the tested application). This question isn't about a specific problem in one of the tests, it's more general about Ranorex 5.3.5 and Win10:
  • Was this combination tested?
  • Does anybody else has problems with this?
  • Is this simply something that will not work and we need to either upgrade Ranorex or change to another product?
Any comments on this topic are appreciated.

Thanks,
Bernd

Re: Ranorex 5.3 and Windows 10

Posted: Fri Feb 17, 2017 11:04 am
by odklizec
Hi Bernd,

Generally speaking, Ranorex 5.3.x is way too old and it's based of SharpDevelop 3.2, which is even older and most probably not fully compatible with Win 10. I would strongly recommend upgrading Ranorex to latest 6.2.1. This is probably the only way how to check/eliminate possible 5.x incompatibility with Win10. Additionally, there were done many WPF-related tweaks between 5.3.5 and 6.2.1.

Re: Ranorex 5.3 and Windows 10

Posted: Fri Feb 17, 2017 3:20 pm
by krstcs
Windows 10 Update 1607 (Anniversary Update) is not fully supported until Ranorex 6.0.2 (which is itself no longer supported by Ranorex).

As Pavel said, you must upgrade to a supported version of Ranorex in order to get support, including new features, updates, and bug fixes. Only versions 6.1.1 and 6.2.1 are supported currently.

Re: Ranorex 5.3 and Windows 10

Posted: Mon Feb 20, 2017 7:18 am
by Bernd Rausch
odklizec wrote: Generally speaking, Ranorex 5.3.x is way too old and it's based of SharpDevelop 3.2, which is even older and most probably not fully compatible with Win 10. I would strongly recommend upgrading Ranorex to latest 6.2.1. This is probably the only way how to check/eliminate possible 5.x incompatibility with Win10. Additionally, there were done many WPF-related tweaks between 5.3.5 and 6.2.1.
Thanks a lot for the reply, that helps for further internal communications.

Have a nice day,
Bernd