Q: FileVault stuck on "Encryption Paused"

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.

semsijo wrote:

 

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.

Things like that happens from time to time and only thing what you can do is to try resolve it. If you do not have enough patient to do that then save yourself more stress (and what is more important save the AppleCare person from listening to your usless talk because it is not his/her fault) and send back to Apple your MacBook Air.

You can release your anger here: http://www.apple.com/feedback/

There is few steps that can take to resolve this problem, many times already mentioned here on Apple Discussions by other users. If you need a help, we can help you, but again, your usless talk it won't fix the problem for you!

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 too have just noticed this issue with my new MBP however let my battery get to 100% and still no change but what i did notice is when i unplug the magsafe and click on the battery icon it now says used Apps using significant energy - "Converting to FileVault". In Filevault in preferences it still says to plug it in.

Is it still doing something? I think i'll leave the machine on and disable all the power saving to find out.

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. 

I have the same problem. Brand new MBP 15. I spent a lot of time on the phone with Apple. I was surprised that each time, each new person, was completely unaware of this problem. My case was escalated and everybody was very nice. But there is no estimated fix. I was told that my file system is not actually in danger and there is no chance that I will lose my files. I am not sure that I am confident in this information. I sure wish that Apple would do a better job and take this seriously. The whole point of me shifting to Apple was reliability. This has, quite frankly, shaken my confidence pretty dramatically.

I have "upgraded twice" I will not recommend Yosemite.

I had the same issue.

Reinstalled a clean and fresh Yosemite in recovery mode without activation of Filevault this time.

I'll activate it with next Yosemite update when this bug will be solved.

Before that, and even now, with clean install, i regulary found problems on files permissions when i check with diskutil.

Don't know if it's normal on a brand new macbook pro (ssd), but disk vérification is always good.

I suppose it may be secure to make a Check and correct permissions BEFORE enabling Filevault.

Maybe this is a cause of hanging the process.

Brand new macbook and this is what I get?

Its been three days that I purchased my new Macbook Pro and the File Vault encryption is stuck.It says to connect it to the power adapter to resume encryption.

I do and nothing happens. (even left it plugged in no matter what it said, for one day)

Any useful ideas anyone?

Scafede - Another satisfied customer! Same deal - changed power outlets while setting up a new Air. Went into the well-documented "encryption paused" mode 3 minutes from being finished. Ran through the process and about 30 seconds after booting up, it resumed and finished in about 30 minutes.

I purchased a brand new Macbook Pro and had the same issues with FileVault. I have now reinstalled the OS X and managed to get the system back to where I could start initial setup from beginning.

Could someone please tell me if the Disk Utility section is correct? Should I have the "disk 1" and "OS X Base System" listed under the "Macintosh HD"? Do I have something duplicated?

Here is a picture: