Synergy

I can confirm this issue.

Server on Windows 7 Ultimate

Client on Windows 8 RTM (released today in MSDN)

Both client and server are running the latest version available (1.4.10beta).

In the client machine:

1) Alt key works. I can use alt key to activate the menu in Firefox without problem.

2) Tab key works. I can use the tab key to switch fields in Firefox.

3) Alt+tab combination doesn't work. But if I use the physical keyboard in client machine, it works without problem.

If you are in a Metro app, Windows key + D (show the desktop) combination doesn't work in client machine (Windows 8) too.

1) Windows key does work. I can use Windows key to activate the 'start' UI without any issue

2) 'd' key does work.

3) Open a Metro app like Windows Store. Windows + D combination doesn't work. I cannot use it to display the desktop.

4) If I use the client machine's physical keyboard, Windows + D combination can show the desktop for me

I can also confirm that I'm having the same issue with a Windows 2k3 host and a Windows 8 Enterprise (RTM) client. Alt+tab isn't working in desktop apps, and Windows + D won't show the desktop Windows + Tab however, WILL switch metro apps. Both client and server are running 1.4.10.

This same problem exists even with very old versions of Synergy. I have been using 1.3.4 for a long time because I've never felt like upgrading, but the same problems exist. It's also worth noting that the problem also happens with a Win8 server as well.

I'm not sure about the architecture of Synergy, but I can add some context from the Windows side (I work on Windows). A number of security changes have been implemented in Windows 8 which prevent programs which are not Metro apps from injecting keys that would remove you from the Metro environment. The way this works is that the keyboard shortcut is ignored if it doesn't come from a physical keyboard or a program that has the appropriate permissions. There are a number of keyboard shortcuts which this affects, one of which is Win+D. Alt+Tab might be another, though I don't recall for sure (most likely is). In order to have the proper permissions, the program must be built with UIAccess (see http://msdn.microsoft.com/en-us/library/ms742884.aspx). I believe that if the Synergy client has this, it should solve the problem.

I can confirm this issue also.

Windows 7 SP1 Synergy v1.4.11 x64 as server Windows 8 Release Preview Build 8400 Synergy v1.4.11 x64 client

Alt+Tab does not work on the client.

Alt+Escape is actually a Windows shortcut to cycle through all the taskbar windows, and this command does work on the client from both the server's keyboard and the client's keyboard. It is a temporary workaround only though, as the typical alt+tab dialog does not show up on the client.

I have this problem as well. Everything works as expected from a directly connected keyboard. But synergy shows the following behavior:

Server

Ubuntu x64 12.04.1 LTS, synergy 1.4.10 from ubuntu repository

Client

Windows 8 Pro 64, synergy 1.4.10 (According to appwiz.cpl)

From Metro UI

• Win+D -> Nothing
  • should switch to desktop mode
• Win+B -> Nothing
  • should switch to desktop mode
• Win -> desktop mode ?
• D -> start search with "d" ?
• Win+F -> Start search ?
• Alt+Tab -> Nothing
  • Should show task switcher

From desktop mode

• Win+D -> Toggle show desktop (as in windows <= 7) ?
• Win -> Switch to Metro UI ?

Confirmed here as well. Version 1.4.10 on both machines, Windows 8 (64) RTM on both systems. Very frustrating. I have 18+ years of muscle memory to hit ATL+TAB.

Mac Mini server (10.6), Macbook client (10.8), and I confirm this behavior exists here as well.

Command+Tab on the server keyboard while operating the client does not function. I have verified the two keys operate other wise, in other shortcuts, and changing focus in a webpage. The client Command+Tab does work regardless of the focus of the server k/m.

Also it worked Friday (09/28/2012). I put a SSD in the client over the weekend, and Monday (10/01/2012), when I reinstalled synergy (1.4.10) on the client, I no longer had Command+Tab on the client.

Failed to mention Server is running 1.4.10 as well.

I can confirm this same issue happening on 1.4.10 (both client and server are running Windows 8). I have tried service and legacy mode, as well as elevated mode. No love. The alt key works, but not the alt-tab combination.

I can also confirm, under both of my use-cases:

1: Windows 7 x64 server, v1.4.10; Windows 8 RTM x64 client, v1.4.10 2: Windows 7 RTM x64 server, v1.4.10; Windows 8 CP x64 client, v1.4.10

I can confirm this on 1.4.10 with the client running on Windows 8 Pro 32bit, retail version. Alt-Tab, Win-Tab don't work. I am commenting to subscribe to this (hopefully) as I don't see any other way to follow a topic who's resolution interests me.

Win-Tab on Windows 8 is popping up the new switcher, but it slides right back to the left margin. Other programs having intermittent keyboard and mouse issues, I believe all desktop apps, not Metro. Confirmed it is Synergy causing the problems. Need to make a little donation...

Confirmed between Mac Mini OS X 10.8.2 and Windows 8 Pro x64.

Support Bug

New Accepted

1.4.11

OS X -> W8

I found a similar behaviour on this setup.

Server: Mac OS X 10.7.5 x86_64, Synergy 1.4.10

Client: Windows 8 Pro x86_32, Synergy 1.4.10

-The combination alt+tab does not work.

-Super+tab works fine.

-Super+D works for normal applications, but when the start menu is open, or in Metro apps, super+D does not work.

Troels

I checked the same bug. (WinXp server 1.4.10 - Win 8 Pro client)

Tried 1.4.10-r1595 and 1.4.11-r1684 with same results

Win7x64 Server running, Win8 client, Win7x32 client. Alt-tab not working on Win8.

Is there an ETA for the 1.4.11 official release? I have used Synergy for years and love it, but this issue is a show stopper for me and has me looking for another solution..

Thank you, Wade

I have a similar problem. I'm using Win8 as my client and Mountain Lion on my Macbook as the Server. Win+Tab works, but Alt+Tab does not. Both Alt and Tab work individually but not together.

I have found an almost workaround for this for those who want to keep their hands on the keyboard; WinKey + NumKey (The number being the index of the app in the task bar going from the left) still works. This not as convenient as Alt + Tab I admit, but can still be helpful once you get used to it.

Possible Fix: I have this problem in Windows Server 2012: which is the same pretty much as 8. ALL the stuff you guys said plus the mouse cursor often just disappeared or I would lose control altogether when I would run server manager or other elevated stuff (which I actually found a workaround for that, adding synergy into security software hash policy and giving the files unrestricted access, plus adding the service to log in on an account with high-level privs.). Anyway, I have 5 machines running synergy on two machines running windows server 2008, one running server 2012, and two running windows XP professional, the monitors are arranged like this, left to right:

[2008]--[2008]--[2012]--[XP(synergy server)]--[XP]

MY WORKAROUND; in order to have ALT+TAB work on the server 2012 machine, I had to make it the synergy server, even though it isn't my main computer, i just plugged my keyboard/mouse into it, and changed the settings on all the machines one by one. Since then, I haven't had ANY problems at all with any of the machines. But it still is a bug... however, since windows 8/2012 handles task scheduling priority way better than XP, my mouse and keyboard have been WAY WAY more responsive since I made this change even though I was stubborn about doing it. So if you have been thinking about doing this too, do it, it might just be the solution you've been looking for, it was for me.

May not be the right place to post this, but PRTSCRN also doesn't work on a Windows 8 client with Win 7 server... (I can confirm the same Alt-Tab problem)

I can confirm that Alt+Tab at least doesn't work here (Windows 8 client, CentOS 6 server). I can, however, use Win+Tab, Win+D, or other keyboard shortcuts successfully.

When I try to Alt+Tab on my Windows 8 client, nothing happens, and a Tab gets typed into the active application on the CentOS server (usually it's a terminal program). Alt+Tab works fine in CentOS.

I can also confirm. alt+tab not functional on windows 8 ultimate. Server: Windows 7 Utlimate. Client: Windows 8 Ultimate. Both are x64. Windows 8 runs elevated.

Seeing the problem using Win 8 Ultimate server and client. Running version 1.4.11 from 13-Feb.

Here's a debug level 2 log of an alt-tab press from the server:

DEBUG1: hook: 0x000000a4 0x20380001
DEBUG1: hook: 0x060000a4 0x20380001
DEBUG1: hook: 0x070000a4 0x20380001
DEBUG1: event: Key char=0, vk=0xa4, nagr=0, lParam=0x20380001
DEBUG1: new mask: 0x2000
DEBUG1: new mask: 0x2004
DEBUG1: onKeyDown id=61417 mask=0x2004 button=0x0038
DEBUG1: send key down to "AndyV" id=61417, mask=0x2004, button=0x0038
DEBUG1: hook: 0x00000009 0x200f0001
DEBUG1: hook: 0x06010909 0x200f0001
DEBUG1: hook: 0x07000909 0x200f0001
DEBUG1: event: Key char=9, vk=0x09, nagr=0, lParam=0x200f0001
DEBUG1: new mask: 0x2004
DEBUG1: new mask: 0x2004
DEBUG1: onKeyDown id=61193 mask=0x2004 button=0x000f
DEBUG1: send key down to "AndyV" id=61193, mask=0x2004, button=0x000f
DEBUG1: hook: 0x000000a4 0x80380001
DEBUG1: hook: 0x060000a4 0x80380001
DEBUG1: hook: 0x070000a4 0x80380001
DEBUG1: event: Key char=0, vk=0xa4, nagr=0, lParam=0x80380001
DEBUG1: new mask: 0x2004
DEBUG1: new mask: 0x2000
DEBUG1: onKeyUp id=61417 mask=0x2000 button=0x0038
DEBUG1: send key up to "AndyV" id=61417, mask=0x2000, button=0x0038
DEBUG1: hook: 0x00000009 0x800f0001
DEBUG1: hook: 0x06010909 0x800f0001
DEBUG1: hook: 0x07000909 0x800f0001
DEBUG1: event: Key char=9, vk=0x09, nagr=0, lParam=0x800f0001
DEBUG1: new mask: 0x2000
DEBUG1: new mask: 0x2000
DEBUG1: onKeyUp id=61193 mask=0x2000 button=0x000f
DEBUG1: send key up to "AndyV" id=61193, mask=0x2000, button=0x000f

And here it is from the client:

DEBUG1: hook: 0x000000a4 0x20380001
DEBUG1: hook: 0x060000a4 0x20380001
DEBUG1: hook: 0x070000a4 0x20380001
DEBUG1: event: Key char=0, vk=0xa4, nagr=0, lParam=0x20380001
DEBUG1: new mask: 0x2000
DEBUG1: new mask: 0x2004
DEBUG1: onKeyDown id=61417 mask=0x2004 button=0x0038
DEBUG1: send key down to "AndyV" id=61417, mask=0x2004, button=0x0038
DEBUG1: hook: 0x00000009 0x200f0001
DEBUG1: hook: 0x06010909 0x200f0001
DEBUG1: hook: 0x07000909 0x200f0001
DEBUG1: event: Key char=9, vk=0x09, nagr=0, lParam=0x200f0001
DEBUG1: new mask: 0x2004
DEBUG1: new mask: 0x2004
DEBUG1: onKeyDown id=61193 mask=0x2004 button=0x000f
DEBUG1: send key down to "AndyV" id=61193, mask=0x2004, button=0x000f
DEBUG1: hook: 0x000000a4 0x80380001
DEBUG1: hook: 0x060000a4 0x80380001
DEBUG1: hook: 0x070000a4 0x80380001
DEBUG1: event: Key char=0, vk=0xa4, nagr=0, lParam=0x80380001
DEBUG1: new mask: 0x2004
DEBUG1: new mask: 0x2000
DEBUG1: onKeyUp id=61417 mask=0x2000 button=0x0038
DEBUG1: send key up to "AndyV" id=61417, mask=0x2000, button=0x0038
DEBUG1: hook: 0x00000009 0x800f0001
DEBUG1: hook: 0x06010909 0x800f0001
DEBUG1: hook: 0x07000909 0x800f0001
DEBUG1: event: Key char=9, vk=0x09, nagr=0, lParam=0x800f0001
DEBUG1: new mask: 0x2000
DEBUG1: new mask: 0x2000
DEBUG1: onKeyUp id=61193 mask=0x2000 button=0x000f
DEBUG1: send key up to "AndyV" id=61193, mask=0x2000, button=0x000f

Both client and server are running on elevated privileges. Client is running UAC off.

This is a really high priority issue for me, so please feel free to contact me directly if I can provide more info.

Hi Steve, we haven't seen an update on this in a while. Can you let us know the status? This issue is killing me..

Thank you, Wade

Or in case it's impossible to fix this issue it would still be useful to know that it is impossible. It would be a real real waste though, I love synergy since I started using it about a week ago.

I too face the same issue. ALT+Tab has been very convenient, is there any workaround atleast?

I installed the latest 1.4.11 today to see if this had changed at all. It's still an issue. I have the server running on my Win XP desktop and client running on my Win 8 laptop. Is there any news on this front?

Today I installed, client and server (both win8 pro x64) the night build 1.4.11r1704, the problem is still present.

I can also confirm:

Server: Windows 7 Ultimate 64bit SP1, Synergy 1.4.10 Client: Windows 8 Pro 64bit, Synergy 1.4.10 UAC off in both cases, using IP for client, Wifi N 5Ghz (VERY fast, little packet loss, <1ms latency)

I am also having this issue.

Both machines are 64 Bit Windows 8 Pro with Synergy 1.4.10.

I can confirm this issue with a CentOS 6 server and Windows 8 Pro 64-bit client. Both are running Synergy version 1.4.10.

Just tested this, Cliff Smolinsky's comment is on the spot. Adding a UAC manifest with uiAccess=true to synergyc.exe, signing it, and changing CMSWindowsRelauncher.cpp to call SetTokenInformation(token, TokenUIAccess, ...) before CreateProcessAsUser makes Alt+Tab work without a hitch in my Windows 8 setup.

But it turns out the former steps weren't necessary at all! The SetTokenInformation call is sufficient to give the resulting process UIAccess permissions, and let it use Alt-Tab freely in W8. Haven't tested with test signing off or with W7, but I don't expect any issues.

http://pastebin.com/fmgM3skx

To be clear, the binary isn't signed and the ONLY change made here is the one in CMSWindowsRelauncher (as well as the previous change I mentioned for the elevation-restart fix, which should be entirely unrelated).

It sounds like you now know what the problem is... Now the code tree needs to updated and the binaries need to be recompiled. I just threw $150 and 15 votes toward making this problem go away. Can you make it go away relatively quickly? IE. Before the next code release in May.

While my contribution isn't a lot in the grand scheme of things, I thought it would be enough to warrant a response here or on the roadmap from a developer... Hmmm, guess not.

Same bug. Since a few months. When is a fix planned?

If people are interested and the Synergy devs are okay with it, I can post the custom build I made so people can test. It's based on the 1750 nightly and includes two patches: this one, along with another one which seems to fix the disconnect-on-UAC-desktop-switch behavior when elevate is checked. Hope this is kosher :p

I am in if Synergy proper is OK with it. Though something tells me they aren't paying much attention to this thread.

I would also love to see this one fixed. Currently i am working around it by using Win+Numbers instead of alt+tab, but it's still very annoying.

Home-cooked builds here, along with applied patches

I just installed the x64 version and it is working quite well. Thanks for sharing! I did have to download with Explorer. For some reason, Firefox corrupted the executable twice.

As a note to the developers and please take this as constructive criticism. You guys have the market cornered on interop between windows and linux as far as I can tell so turning to something else really isn't an option. That is unless you do some funky stuff with VNC. However, you should really try to focus less on the feature enhancements that have never been and more on bugs that affect how users operate from day to day. If you want a user base that donates, you should REALLY consider making sure these types of bugs get fixed in reasonable time frame. Even if the bug is a bit lower on the voting hierarchy. If it took Mr. Tung a day to fix this, it would have been worth your while to fix this and then go back to working on encryption. You might also want to consider paying attention to donations over a certain amount. It would have been really nice to hear back from someone on the team to say thanks and we plan to do x by y. Just my humble two cents. Thanks.

With Henry Tung's patched version Alt+tab is working great in Windows 8, wish the Synergy dev would incorporate the patch into future versions (and not sure why it took this long just to fix it).

Excellent work, Mr. Tung. Works like a charm.

Henry Tung, you are my hero! :)

Henry Tung, you are my hero too!!!!!!!!

Thanks a lot!

Thank you Thank you Thank you!!!!

This has really saved my day.

Henry Tung, thanks for the patched version. Works great.

Any update about other key not working?

Henry Tung, you're a star! Thanks for this.

Thanks, now the Windows key combinations are working on the Windows Client... but if i start a RDP Session on the Client, the key combinations insode the RDP Session didn't work anymore...

with the original 1.4.12 the key combinations are working :/

Ditto: Thanks Henry!! I'm glad I persisted and kept on to the end of the comments to see your fix. :)

This is awesome!!! Thanks a bunch.