Apple Keyboard Windows

[Sofía Goldthwait]

Ihave the Magic Keyboard working with my Windows 10 system. Download the latest Windows Drivers from the Apple Support site (Downloads: Windows drivers) and you should be able to install the keyboard driver from the zip file.

In my case, when I would go in Bluetooth & other devices on Windows 10 and click on Add Bluetooth or other devices, I would eventually see my Magic Keyboard with Touch ID appearing, but when I would select it, I would get an error message saying: "Try connecting your device again". What solved the issue for me, was to update my Bluetooth drivers using the ones provided by Intel here: -wireless-bluetooth-for-windows-10-and-windows-11.html.

My apple wireless keyboard has stopped pairing with Windows 10. Now when I try to pair through settings, I'm asked to enter a passcode for the keyboard rather than being supplied a passcode to pair the device. I'm unable to type anything using the keyboard. Entering four zeros using the laptop keyboard does not work. I've tried un-installing bluetooth drivers and reinstalling. This doesn't help. Any advice?

With the new Apple Wireless Keyboards and Touch Pads you need first to connect device to the PC via USB-to-USC-C cable. After that when you go to the Bluetooth section on Windows 10 you will see that keyboard and will be able to pair it.

Version 1.x had a bug whereby anybody using a Mac with a non-US keyboard was tortured by the software failure to map keys correctly to the Windows session. The most infamous examples of this where that the Mac " (speech marks) key would generate an @ (at symbol) in Windows and vice versa although a number of other incorrect key mappings also apply.

Microsoft then bought a 3rd party RDC client and this became the next Microsoft official client and I cannot remember if this was released as version 5.x or 7.x. Regardless as this was new/different code it REINTRODUCED THE SAME BUG!!!

When I last was personally victimised by Microsoft with this issue many years ago I also reported this but I found that the Parallels Remote Desktop Client for Mac did not have this bug. The reason being it was not written by American programmers who are wilfully ignorant regarding international keyboard layouts.

Unfortunately I now once more have to use an RDC client and I am finding that the Parallels client whilst still available is not connecting to the Microsoft RDC server whereas the Microsoft client does successfully connect even if it then inflicts cruel and unusual punishment in the form of this now ancient keyboard mapping error.

I have however been able to prove that the RDC client for Mac available here - www.jumpdesktop.com DOES connect to the same Microsoft RDC server and DOES NOT have this keyboard mapping bug. However the JumpDesktop client is a chargeable product.

Microsoft over the decades has in a number of cases committed grave offences against Mac-kind but in more recent times has been comparatively friendly to the Mac using community. Why therefore is this bug which affects potentially BILLIONS of people around the world i.e. anyone who does not have a Mac with an American keyboard still not been fixed?

5. On the Mac type in to the Wordpad document abcdefghijklmnopqrstuvwxyz these all map correctly. Now on the Mac type the @ (at) symbol, in Window you will instead see the " (speech marks) symbol, now on the Mac type the " (speech marks) symbol, in Windows an @ (at) symbol will appear. As mentioned other keys like the \ (back slash) are also incorrectly mapped.

When using the Macintosh "Microsoft Remote Desktop" (French ?) I have a keyboard problem with Powershell : my keyboard does not send anything to the powershell session if the keyboard mode is "Unicode" in the "Keyboard Mode" "Connections" menu.

I have problems with keyboard input in certain apps using rdp. In windows it works from iPad. When I start Zbrush and power shell keyboard input is impossible. Nothing happens. Is this the same cause?

We've been suffering this problem for years. We've mostly got around the problem by asking the users to set the keyboard mode to Unicode, which allows enough of the UK Mac keyboard to be mapped as the average user needs, including the '@' sign and speech marks.

However, as developers we use Scancode, which allows us to do things in calculations that Unicode doesn't. We've uploaded a custom UK keyboard to each RemoteApp server, which again does an OK, but not perfect job.

Now we have a problem for users authenticating by OAUTH 2 for Microsoft 365 within our apps. Typing into a web browser within FileMaker using Unicode results in a 'Before typing, press Tab or click in a field' message, which is a standard FileMaker error when trying to enter data without having the cursor in a field. However, there are no fields in this case, just the native Microsoft Edge engine based web viewer.

Swap the setting to Scancode and all works fine, except the keyboard mappings then rely on the custom keyboard, which has to be selected within a floating language bar and set for each session (if it opens at all, or with the text displaying to change it, which is the most common annoyance).

For years Jump Desktop from PhaseFive Systems has allowed a 'Match Mac Keyboard', or an extensive list of international keyboards, to select from for each connection. It is very obvious that this is not a priority for Microsoft, despite the awful user experience outside of the US.

Same problem here: bluetooth "compatible" external keyboard, Italian layout. Keyboard is working correctly with MacOS. When I type a backslash on the external keyboard, the Microsoft RDP client sends a "

Hi there. Was this ever resolved please? I tried going into the keyboard settings and changing option and command around but it would seem that Synergy overrides this. I made the mistake of buying a keyboard and without realising, they've swapped the command and alt button around. How very annoying of them

I do not want to remap the keys directly on my secondary laptop (Ubuntu) settings because the physical (local) key maps should remain consistent and familiar. I only want the keys to be remapped when I'm controlling Ubuntu from the macOS physical keyboard.

I was unable to find links on Symless.com to any documentation whatsoever. I'm certain this is not an unusual request and I'd rather not trigger an individual support ticket that just gets repeated over and over. Hiding the forums behind a "Help" button that looks more like a "Support Ticket" isn't the right way to do this.

I found this forum from external search engine results, and was immediately blocked from searching anonymously by some message that indicated I need to wait 4 seconds before performing another search, but in reality, I was not permitted to search after any amount of waiting until I signed into the forum with my account.

I was able to find a number of articles (here and elsewhere) that indicate I should be able to double-click on the machines in the Synergy configuration screen. Unfortunately, this does not seem to work for me and might be a bug in the latest Synergy that might have been caused by macOS High Sierra? In any case, double clicking the machines in my server configuration interface does not seem to do anything.I eventually found this post and found the following issues here:

I have a similar issue. I have a Keyboard that allows me to change the keys from the keyboard itself. So i have set windows key to be command from the keyboard. However, Synergy is automatically mapping the key that it thinks should be Windows to command is reversing the setting I have set on the keyboard.

Any suggestions for disabling automatic key-switching?

For Reference the KeyBoard is WASD brand 10keyless

I'm going to post this on other related threads to help others as well. Note that if you change your setup later, you're going to have to undo this change (let Synergy edit the file), make the setup changes, and reapply it.

* And now for a selfish plug - if you find that this solution saves you time, throw me a follow on Twitch or Instagram (cautionary_snail) - it's free, and follows make me happy since I work hard on my photos, and will be trying to build a Twitch channel soon. If you work for a company that's awesome (hello to any animation companies, 3d printing companies, etc.) and can send a discount or silly postcard my way, that's especially awesome. I'd worship you if you can get me early access to The Outer Worlds so I could get a jumpstart on streaming it!

I found the solution by going through their Synergy Github repository and experimenting with what was documented as supported for Synergy 1. Perhaps your solution, if it was a feature in Synergy 1, might be found in one of the documentation bits there. I have found via trial and error that not 100% of the featues in Synergy 1 that are controlled by the synergy.conf file do work in Synergy 2, so it may be a little hit or miss.

For example, Aliases were a no-go for me, and I have yet to figure out a way to map the Fn key on the Mac keyboard so as to access some of the other Fn+F4/Fn+F5 keystrokes. If I could just figure out if the Fn key sends any form of Unicode, I might have a chance of figuring it out, but that's mysteriously missing from the bulk of documentation I've looked at thus far.

While it's not great that we have to suppress certain features (like future autoconfiguration) to get this to work, at least it's a start.

What I still don't quite get is why this has not yet been included in a new build of the actual Synergy 2.0 software since the functionality is present and activating it merely requires adding the strings to that configuration text file. It makes me sad that such a great product is not getting the development support to regain these clearly pre-exisitng features via the UI. Is Symless no longer investing in this product?

I currently use a MacBook Pro, and to be honest I quite like, however I do have Windows 10 installed on it via Bootcamp. Even though this was so easy to setup and all the drivers worked and the keyboard layout also worked. As you may have noticed that there are some differences between the apple keyboard layout and normal keyboard layout.

3a8082e126