I have a really strange problem with my sister's MacBook Pro (Mid 2012, running El Capitan): it is incorrectly identifying the physical layout of the built-in keyboard. It isn't just a matter of mapping the buttons to characters incorrectly; the diagram shown in "Keyboard Viewer" actually shows more physical buttons than exist on the keyboard.

Note: see the update at the end for the current status.

The physical keyboard appears to be the correct US English version, and it is called "U.S." in the "Input Sources" preferences pane — but here's a screenshot of what Keyboard Viewer thinks it physically looks like:

screenshot: no keys pressed

The problems become more obvious with Shift pressed:

screenshot: shift pressed

Thanks to Wikipedia-ing (and a helpful clue from the yen symbol), I think this is showing the Japanese Industrial Standard layout, but I don't actually read any East Asian alphabets, so I'm less than 100% confident.

My goal is to get the layout recognized as standard US QWERTY, either (preferably) by actually getting OS X to believe it is one, or by re-mapping the keys it believes it has. I've read Create and use your own input source, but so far without success. I think my issue may be that the characters it wants to map from are the Japanese(?) ones rather than the ASCII ones.

Interestingly, I tried booting from a Ubuntu USB, and it recognized the keyboard with no problems. On the other hand, the layout was still incorrect when I booted from the OS X recovery partition.

Any advice on how to correct this would be very greatly appreciated!

Update 1:

Inspired by Tom Gewecke's answer below, I tried re-setting the SMC, which has changed things. Probably the fastest way to describe it is with two new screenshots (taken with the "U.S." input source):

  • With no keys pressed: Screenshot of Keyboard Viewer after resetting SMC
  • With Shift pressed: enter image description here

As you can see, it's not Japanese anymore, but it also still doesn't match the layout of the physical keyboard. In Keyboard Viewer:

  • The diagram shows a key with § and ± to the left of the 1/! key. but the actual keyboard has a key marked `/~. When I press this key, Keyboard Viewer shows it as a press to the `/~ key between the z and left shift keys (there is no physical key between z and shift.
  • The diagram shows a vertical return/enter key and an extra \/| key at the right-hand side of the home row, between '/" and enter. The actual keyboard has a horizontal enter on the home row and has the \/| key as the last key on the QWERTY row, to the right of ]/}. Again, Keyboard Viewer shows a press of the physical \/| as a press of its misplaced key.

So, for practical purposes, this is a huge improvement, since the physical keys now all do what their keycaps say they do. On the other hand, something is clearly still wrong, since Keyboard viewer still has keys in the wrong place, keys that are the wrong shape, and one key in it's diagram (the §/± key) that isn't mapped to any to any physical key on the keyboard.

Update 2:

I've tried resetting the SMC a number of times; the resulting layout is always either JIS or ISO, but never ANSI, and I've yet to find any pattern that would allow me to predict which the result will be. More concerningly, even when I get an ISO layout by resetting the SMC, it will revert to a JIS layout at some arbitrary point while using the system.

Update 3:

After a long delay, I recently gained access to this machine again. Following up on dan's comment, the keyboard is indeed showing the USB "product id" 0x0264, which appears to be the JIS variant for the MacbookPro10,1 (this model). Here's a screenshot:

Screenshot of system information

  • You still have a keyboard type problem. It has switched from JIS to ISO, but it needs to go to ANSI. Try another SMC reset. Commented Jun 25, 2016 at 23:16
  • Thanks for the update. Have you tried the Karabiner Option mentioned in my blog article? Commented Aug 15, 2016 at 10:01
  • Was the keyboard of this MacBook Pro ever replaced?•• return ••Was this MacBook Pro ever opened?
    – dan
    Commented Aug 15, 2016 at 14:48
  • 1
    From your thorough description of problem, it looks like your keyboard firmware is sending random garbage as its model identification string on the USB bus. Please confirm this hypothesis with:  > About This Mac > System Report... > Hardware > USB > Hub > Apple Internal Keyboard / Trackpad, and include a screen capture.
    – dan
    Commented Aug 15, 2016 at 14:53
  • The keyboard was definitely replaced, and this problem started basically immediately afterwords — I should have mentioned that, but must have lost track of it among the other details. I'm currently away from the MacBook in question, but I will get its model identification string as soon as I can. Commented Aug 16, 2016 at 23:30

1 Answer 1


You machine is mistaking the Keyboard Type. See if this helps:


If nothing else works, try this Karabiner fix:

Change Mac Keyboard Identifier after keyboard replacement

  • 2
    Could you please add the relevant portions of that link into the answer in case said link dies and for ease of reading?
    – JMY1000
    Commented Jun 23, 2016 at 1:16
  • No dice. Deleting /Library/Preferences/com.apple.keyboardtype.plist does nothing — the file isn't even created again when I reboot. Replacing it with the /Library/Preferences/com.apple.keyboardtype.plist file from a Macbook Pro that works correctly also does nothing. (Interestingly, defaults read com.apple.keyboardtype reports that the domain does not exist.) Keyboard Setup Assistant exits with the message No unknown keyboard connected - terminating at the command line … it doesn't even open a GUI window. Commented Jun 25, 2016 at 15:18
  • Actually, the blogspot post talked about resetting the PMU, which doesn't exist on Intel-based Macs, but I've tried resetting the SMC, which has done something. I'm going to edit the main post above to explain, because it's too complicated for a comment. Commented Jun 25, 2016 at 15:26
  • @LiberalArtist I have fixed the blogspot post to refer to SMC. Sometimes in the end only the Karabiner fix seems to work for this problem. Commented Jun 26, 2016 at 10:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .