Keyboard and mouse inop at filevault screen

Hi,

I do have the same issue. Macbook Pro Retina 13 early 2015 256SSD 8g RAM.

I was in 10.10.5 when this issue first happens more or less one month ago.

10.10.5:

Filevault ON -> impossibile to insert disk unlock password and/or user login. External keyboard works fine and can unlock disk and login (very slow!)

Filevault ON + Reset NVRAM at every boot -> everything ok, fast boot, fast unlock everything ok.

Filevault OFF -> all ok

Create another user, nothing changed.

Complete format using sierra installation drive and full disk erase and format using directly encryption.

10.12

Filevault ON -> impossibile to insert disk unlock password and/or user login. External keyboard does not work same way.

Filevault ON + Reset NVRAM at every boot -> everything ok, fast boot, fast unlock everything ok.

10.12.2

Same behaviour of 10.12

sudo nvram -c and then reboot is like boot without NVRAM reset -> not useful

Have somebody fixed this issue?

I can replicate this very fast on my mac.

I have exactly the same issue and hardware. This problem persisted after upgrading to 10.11

Extremely annoying to try to move the mouse cursor down to "restart" when it only works for tiny snippets of time at random intervals. Tried connecting an external keyboard or TB display and had the same issue.

Often I would be left with the "if you're having trouble entering your password, press and hold the power button and reboot to access safe mode" (or something like that). After choosing the obvious recovery option "my keyboard does not work when entering password" the recovery tool unhelpfully suggests that my keyboard is not compatible with FileVault and instructs me to disable FileVault. Oddly enough this solution actually works.

So it seems this is a serious bug in FileVault - the initial boot "unlocker" code seems to have trouble on "MacBook Pro (Retina, 13-inch, Early 2015)".

Same here on my 13" Retina MacBook Pro Early 2015, 8GB, i5 even after several clean installs to 10.11.1 (and at least it is a relief that I am not alone)

Are there any news about this case or an appropriate workaround?

First I thought this came up since I was on the public beta programme. But after two clean installs with the original build 15B42 this happened all the time. Funny enough, also when I erase the SSD completely and want to access the recovery option via Internet (the screen with the Globe). Also there the mouse and keyboard stucks. So I restarted my mac several times and one of this times the mouse didn't stuck. What I did not do was to reset NVRAM/PRAM. So this is the only workaround? Or is it best to leave FileVault off? Seems like a bad compromise...

Thanks for this post here.

Yes; the only workaround I am aware of at this stage is to ⌘⌥ P+R (reset the parameter ram). I pretty much have to do this on every reboot.

I don't want to leave FileVault disabled as I am traveling for work every week and require most of my documents to remain encrypted at rest.

Ah, OK. Thanks. Full disk encryption should be a must not an option at least on portable computers. So I will turn it on and will reset the NVRAM.

But you never were on any Betas before, right? Since I am still wondering, why I ran into this... again, now I am on a clean install of 10.11.1 with this problem.

Update: on a hunch I deleted my Bluetooth pairing with Magic Trackpad. (I hardly ever use it and had almost forgotten it). The NVRAM clear workaround led me to this hunch. Bluetooth pairing is kept there for pre-boot use.

This seems to have solved the problem for me. Many clean reboots since clearing out the Bluetooth pairing.

suggest deleting and Bluetooth HID pairings to see if that fixes it.

I have this issue on 10.11.6 with early 2016 Macbook 12"

I have the same issue with 13" Retina Macbook Pro early 2015, i7, running 10.11.6

I have the same problem with a late 2015 13 inch MacBook Pro with retina. Disabling the FileVault seems to remove the problem.

When FileVault is enabled, I have noticed the keyboard works every few seconds on login so if i patiently enter my password, repeating each keystroke repeatedly until they register, i can get through. Alternatively, I have logged in by using a USB external keyboard.

I have upgraded to OS X El Capitan, but this hasn't fixed the problem.

If anyone has ideas on how to fix this, I'm very keen to try.

Just turned on FileVault on my Mac Mini Server, and the keyboard stopped working. My trackpad and numeric keypad are still connecting, just the keyboard won't work. Now I'm dead in the water and have to buy a USB keyboard to enter my password and disable FireVault. Very frustrating!

I have exactly the same problem with my 2015 MBP and built in keyboard and trackpad. im running Sierra with all the latest updates. I've tried several options. Some like a fresh install worked for a while. However it comes back eventually. Seems apple has chose to ignore the complaints from its valued customers on this issue for several versions of Apple OS. I have sent an email to Tim Cook pointing to this thread and also sent a transcript of my conversation with Apple Care. If nothing comes out of it, I'm ditching Apple products. Period. Lenovo has much better solutions and price is much more competitive.

DDidn't seem to work for me 😟

Apple should admit that this is a defect in Macbook pro 13 inch early 2015 (and maybe others).

I had this issue about 6 months after I bought my machine. The first time I took it to apple store was under warranty and they just replaced the cable that goes to the trackpad and DISABLED Filevault.

After the warranty expired, I enabled the Filevault And the same problem was back but this time was worse because I changed my password to a longer one. I was told that my machine has some liquid inside !!!!!! and I was charged $813 with tax !!!!!

In this, repair they replaced many parts including the logic board, battery nad many others.

After I received the machine from the repair center, I enabled FileVault and it was working fine until now (about a month after the repair), THE SAME bloody issue is back.

My sister has the same model and I asked her to enable FileVault and immediately after she enabled it, the same problem happened to hers.

What is the point of putting a feature the should not be used ?!!!!!

I think Apple already knows about it because the message that we get on the "reset my password" window suggests that FileVault should be turned off if the keyboard is not responding.