FileVault stuck on "Encryption Paused"

So I ran the hardware tests and it came back saying that there were no problems.

I may do a re-install, but right now I'm waiting to backup what I've done so far (i.e. apps installed, data copied over) to a Time Capsule. It's taking forever. 24hrs to do 60GB!!. I don't have a spare external drive to back up to right now. Anyway, I'll wait. It's not my primary machine.

All said though, I do hope that Apple will come up with a fix for this pretty sharpish. It's a bit shoddy really.

Just spent over £2.5k on a new Retina Macbook Pro with fastest CPU and 1TB HD.

I used the default ON settings for FileVault during setup and it hang for around 45 minutes before proceeding to the next step.

Once everything was up and running I noticed the encryption paused message despite having the power line connected.

Tried everything mentioned in this thread and have now resorted to reinstalling OS X.

After having using windows PC's and other systems since 1980 (ZX80) I decided to finally jump ship and join Apple with this laptop.

I have to say that so far this is a very dismal start. I've now lost all faith I had in this company. They ship a brand new top of the range laptop with software that does not work, and by reading these forums they've known about it for a while.

That's similar to me - this MBP was just over £2k and we do expect not to have this sort of issue. To be fair, it's the first time I've seen this sort of thing (this is my fifth Mac). Having said that, I've never turned FileVault on - I'm not sure what possessed me to do it, other than OS X recommended that I do (I don't remember this when upgrading my other two Macs which don't have it turned on). It does make sense to use FileVault on a laptop though. Let's hope it gets fixed soon. Right now I'm not seeing performance issues. When it did kick off again, it was completing the Optimisation before going back to the paused state, so I think it had completed what it needed to do initially. Whether subsequent changes to the volume are impacted, I know not.

On a related note, someone posted a link to file bugs with Apple in an earlier post. However, you need to be a member of the developer programme, which I am not. Anyone got a link for the rest of us plebs to file a report (for it to be ignored, because Apple know best and I'm clearly using my MacBook Pro wrong!)?

Brand new MBA 11". During initial setup, the thing froze on this "Encryption Paused" thing. Yes, the mac was charged up, yes the power cable was in it, yes the green light was on. No nothing progressed. The computer was empty, but iCloud had bough over some settings and calendar entries (no files).

The initial consultation with the online Apple support facility, suggested leaving it to run for 24 hours. It was no further ahead by the next evening. The next online support guy was stumped, and given this was a brand new mac setup, acquiesced and let us go back to the store it was bought from some three days before.

In that store, we got a new machine, as the original 11" locked up in front of the GeniusBar guy and that was that - we got a replacement machine. It's set up now (with FileVault on), but we had other MigrationAssistant teething troubles.

Brand new Retina MBP 13" here and had the same issues as above. Initially turned on filevault last week when I first set it up and it has never completed despite a lot of the above fixes.

Finally bit the bullet, did a time machine back up, full erase and reinstalled Yosemite from scratch this time turning off FileVault during the installation and then restored from my time machine backup and it looks like it's still off.

Update:

Chatted with a support specialist the afternoon of the day I restored everything to its original state and setup without FileVault. The specialist confirmed they are aware of the issue and complimented me on my resolution to the problem. Every new machine should have a red flag slapped on the box with a WARNING of this issue. Very unprofessional.

Brand New, was stuck on "Connect power adapter to resume encryption."

MBAIR 11.6/1.7/8/256FLASH-USA

* Disk Util

* Erase Journaled

* Reinstall Yosemite takes forever, leave overnight

* When prompted during setup unchecked File Vault

* Immediately once logged in went to system preferences and turned on File Vault, it rebooted, on reboot I opened system preferences and just watched...

* Encryption Finished. 🙂

I did the Time Machine Backup > Erase > Reinstall > Restore process. I chose to load the backup data *during* the installation, and when everything was done, FileVault was off. I confirmed this via Terminal.

Note that it never asked me to enable or disable FileVault after I told the installer to restore from Time Machine.

I just can't ******* believe it. I bought this new MacBook Air yesterday and guess why I'm switching to Mac from Windows? To avoid ******* **** like that.

I'm really disappointed by Apple. I already tried everything from this discussion but nothing worked. It's still bugged.

I will call the Apple Support now and if they don't have a quick and simple solution, I will find a really simple solution for me: I will just put the ******* thing back in the box and send it back.

Thanks god I have the opportunity to send this piece of **** back, I can't believe that this can happen to a new device from APPLE. This is ridiculous.

Just a 'me too', no solution here. I configured two brand new MacBooks Air this week (out of the box). Both MacBooks have this issue now. I'v tried every solution described here, or elsewhere, apart from a clean reinstall. I've reported a bug at www.apple.com/feedback (no developer account required). The MacBooks do not seem to be affected otherwise. I think I'll wait for 10.10.2

Is my understanding of the situation correct when I say that the PRAM + SMC reset, then disk util and repair solution, as well as the "fdesetup disable" solution are the only two solutions other than backing up and wiping?

My MBP is relatively new so I've only got a hundred or so GB of files to backup, but would prefer not having to wipe if I don't have to

Try the clean reinstall and not checking it during setup, and then checking it afterwards and just letting File Vault run, no other programs. That worked for me on my brand new MacBook Air after I tried all other solutions in the thread. I think the bug is that for Yosemite if you turn on File Vault during the setup process it has issues. By waiting until the setup is complete File Vault seems to finally be able to complete the first encryption.

Did you perform the clean install and not check it during the setup process?

That seems to be the only solution that works reliably. Others reported success with other solution in this thread. I tried all of them, the only one that worked was a clean install, not checking it during setup, then checking it and letting File Vault only run and complete its setup.

I´m stuck, too, brand new 13" retina MBP. I´ve tried the PRAM reset/CMD+R/repair thing various times without success, same goes for the fdsetup fix. At the Moment it´s okay (performance-wise) but I´d rather not leave it in this state of unfinished business until Apple coughs up a fix. My only option now seems to be a wipe and restore I guess. Or is there a certain order for the repair permissions thing? I went through it 5 times, with varying orders. So I reset the PRAM (waiting for three sounds) then immediately press CMD-R and go into disk util. There I unlock the partition via the file menu, then repair permissions, then repar the partiotion, then repair the whole parent disk. Should I check permissions and the volume before repairing? Does the order in which I repair permissions/volume make any difference?

Also, I´ve noticed that if I remove the power adapter, the battery status menu bar item lists a "restore from Filevault" process as a large energy consumer (or whatever the exact term is, you´ll get me I hope).

I´d rather not do a clean wipe and restore, but the battery seems to be drained quite a bit by the stuck encryption. So, what do I do? Decisions, decisions. 😕

I had a battery demand message also. One day after a routine computer shut down and start up, the message was no longer there. I doubt there's cause and effect here...just letting you know the message can disappear. Since I don't have perceptible performance problems or an extra drain on the battery, I'm waiting for an Apple fix to the FileVault issue. I'm reluctant to take more aggressive measures for fear of triggering unintended consequences.