+23
Completed

Run native 64 Bit client on 64 Bit OS

Drashna Jaelre 4 years ago updated by anonymous 3 years ago 15

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.

Available in Version:

Answer

Answer
Completed

Hi All,

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

Really hope something is done with this soon! 2 Things that keep biting me are the inability to run WUAUCLT.EXE or KLIST.EXE from the ScreenConnect command line. There are also many other utilities which are not available in SysWOW64 directory...

I've posted a workaround that will allow you to access the true C:\Windows\System32 directory from the ScreenConnect command window in the original form thread:


http://forum.screenconnect.com/yaf_postsm35454_Client-Version-5-6-runs-in-32-bit-mode-on-64-bit-machines.aspx#post35454


Summary: Prefix your commands with %windir%\sysnative\

Pending Review

So Review It Already! How can it take 3 months to decide IF you are going to fix this x86/x64 thing that got broken in version 5.6? The isn't a Feature Request - It's a Bug Fix.

Under Review
Pending Review
Under Review

I know it doesn't address the point of your original post, but if you haven't seen it already you may find this interesting: Feature Request Status Madness

Answer
Completed

Hi All,

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

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.

Roadmapped

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

-1
Completed