Ranorex Studio and all its tools (Spy, Recorder, Test Suite Runner) are available in 32- and 64-bit versions.
Both versions of the tools are available from the start menu, but if you want to start the 64-bit Ranorex Studio manually, use RanorexStudioBinx64RanorexStudio.exe.
Ranorex Studio automatically tests 32/64-bit-based applications on 64-bit operating systems. It is possible, but recommended only for advanced users, to turn off the bit bridge feature within the Ranorex Settings dialog. If you disable the bit bridge feature (not recommended!) or your Ranorex Studio version does not support the bit bridge (versions before 2.3), follow the guidelines in this chapter to make 32/64-bit automation interoperable.
On 64-bit versions of Windows, processes may run using 64-bit or 32-bit (also called ‘x86’) architecture. Applications started as 32-bit processes are marked with ‘*32’ or ‘(32-bit)’ in the Windows Task Manager; all others use the 64-bit architecture.
In general, you should use the Ranorex Studio version that matches the bit architecture of the automated application. For example, if you automate a 32-bit application, use Ranorex Studio (32-bit) or the respective 32-bit tools, otherwise, use the 64-bit versions of Ranorex Studio and its tools.
When compiling your Ranorex executables, specify the right target architecture in your project settings. In Ranorex Studio this setting is on the Compiling tab in the project properties. .NET applications are by default started as 64-bit processes on 64-bit operating systems unless the target CPU is explicitly set to the 32-bit (x86) architecture.
Consequently, set the Target CPU property to Any processor for automating 64-bit applications and to 32-bit Intel-compatible processor for 32-bit applications.