Welcome to our community!

Run native 64 Bit client on 64 Bit OS

Drashna Jaelre

9 years ago
updated 4 years ago
Completed

Basically, this thread: http://forum.screenconnect.com/yaf_postsm35204_Client-Version-5-6-runs-in-32-bit-mode-on-64-bit-machines.aspx#post35204

Apparently in 5.6 and up, the client service runs as a 32bit process regardless of the OS bit-ness, due to a change from C#/.NET to C++.

This is a problem for a bunch of reasons. Including misreported info, as well as binary access. The "C:\Windows\System32\" folder displayed and accessed in the "Command" section is in fact "C:\Windows\SysWOW64\" and prevents access to a number of command line tools.

The client really needs to be a 64-bit process on 64-Bit OS's.

Pinned replies

anonymous

8 years ago
Answer
Completed

Hi All,

There was a fix implemented that will enable a temporary redirect to the sys32 directory when needed.

Reply Link

Replies 16

Oldest first
Newest first Oldest first

FAB-ITRescue

8 years ago

Kirsten,

That's great news - for the sake of the record would you kind enough to indicate whether which version contained the fix. I must have missed it in the Output Stream Forum.

Thanks.

Reply Link

anonymous

8 years ago
Roadmapped

Reply Link

FAB-ITRescue

8 years ago

Good job I've got a sense of humour when it comes to interpreting your Request Status Levels . . .

Reply Link

anonymous

8 years ago
Started

Reply Link

-1

anonymous

8 years ago
Completed

Reply Link

Justin Seifert

4 years ago

I know this is years later but there is still no true x64 client available. This prevents us from using this remote access tool in modern WinPE environments unless we perform the very hackish method of adding SYSWOW64 support to the modern PE builds.

Reply Link