FileVault frozen decryption

I've been at this for at least 12 hours now, i'm losing my mind!!! Basically, I was having a small problem with my late 2011 macbook pro so I backed it up, got the problem sorted, Erased my disk and reinstalled yosemite. Since i've reinstalled , I've just been getting the little pinwheel option every few minutes, when i try to do simple tasks like type, copy and paste, everything is running VERY slow, Listening to music and watching videos is next to impossible. So after researching I found a few other people with the same problem and they said it was caused by FileVault (I must have clicked to enable it when i restored) so I followed instructions and began decrypting it. Problem is, It's been frozen in the exact same spot (about 5/6th's of the way) for about 8 hours now, it doesn't even give me a time it just says 'Estimated time remaining'.. I have tried everything, restarted multiple times, typed loads of stuff into the terminal, even reinstalled yosemite AGAIN but still nothing.. I need to do some work for college but it's too slow to run Final Cut pro. Please someone help!

If you can't turn off encryption in Disk Utility, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

Similar Messages

FileVault not decrypting?

For some reason, I decided to encrypt my MBP, just because I could, with Lion. No problem..did that. BUT, when I went to turn FileVault off, it went to do a restart and got hung up. Then, when I did get it going again I went to see if FV was really 'turning off'. But, it still said it was on. So when I tried to turn it off, I got this message saying "there was a problem enabling filevault, Problems were encountered with the disk “Internal HD”. Please turn off FileVault, verify and (if necessary) repair the disk with Disk Utility, and try enabling FileVault again." There is an option that says 'turn off filevault", which, when I press, it prompts me for my password, then I notice something weird: At the bottom of the window it says: "some users are not able to unlock the disk" (with a button to 'enable users')..which is weird because I am logged in as the admin account! When I click on 'enable users' all I see is my admin account with a check mark beside it (to me this means everything's ok?). When I click 'done' I return to the screen and I am given this error: Unable to modify a Full Disk Encryption context.
Basically I just want to completely turn off FileVault. But it looks like it's still trying to 'enable' itself every time I go into System Preferences and into Security.
Help?

First of all thank you for the help. In all my trying to figure it out I didn't try just double clicking on the sparse bundle.
Because this was my only user on the computer I had to enable the root user to be able to login. Once that was enable I was able to mount the sparsebundle and copy my data out. I didn't get all of it as something did truly get corrupted during the decryption but I did get 99% I think.
Now with my data coped to another location I can attempt some repairs and see if I am able to get that last percentage point. Thank again.
Brandon

FileVault Stuck Decrypting (Among Other Issues)

Recently I made the mistake of trying out FileVault to encrypt the files on my MacBook Pro. Unfortunately I came to realize that this is a very tedious process that can take days to complete and slow down the performance of my machine. After trying multiple methods to either speed up the encryption process (which initially changed back and forth from "estimating time remaining" to "106 days remaining") or begin decryption through recovery mode and disk utility, I'm now stuck with a FileVault decryption status that's stuck, and a near useless computer.
im currently attempting to backup using Time Machine onto an external drive in order to do a full restore (since as far as I know that's the only true solution to the problem). Only issue is that it backs up depressingly slow (about 1 MB every 10 minutes, with a total of 224 GB to back up).
If there's anyone out there that could perhaps give me insight on how to repair this issue more smoothly, that'd be great.

A
There are several ways to back up a Mac that is not fully functional. You need an external hard drive or other storage device to hold the data.
1. Start up from the Recovery partition, from Internet Recovery, or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
If you use FileVault 2, then you must first unlock the startup volume. Select its icon ("Macintosh HD," unless you gave it a different name.) It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. Enter your login password when prompted.
2. If Method 1 fails because of disk errors, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
3. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
4. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
B
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

FileVault Frozen

I upgrade to Yosemite last weekend and chose to encrypt my hard drive during the process. The OS upgrade was successful, but it has been five days of not being able to use my MBP outside of "safemode." FileVault has been encrypting my data for five days and every time I try to do something I get the wheel of death. FileVault is showing that the drive is being encrypted but it hasn't made any progress pass the 10% status bar since it started. I have left my computer on, encrypting, for the last five days and it has made no progress. The system is still trying to estimate the time remaining to finish but it hasn't come back with an estimate. I have rebooted, unplugged, and everything else that people have listed in their posts but noting seems to be working. Does anyone have any ideas to help me?

Same issues here. Here is my terminal report:
Start time: 09:51:03 11/09/14
Model Identifier: MacBookPro8,1
System Version: OS X 10.10 (14A389)
Kernel Version: Darwin 14.0.0
Time since boot: 17 minutes
SATA
   ST9500325ASG
FileVault: Decryption in progress: Percent completed = 7971
Diagnostic reports
   2014-10-29 com.apple.WebKit.WebContent hang x2
   2014-10-29 coresymbolicationd crash
   2014-10-29 iMovie hang
   2014-10-30 coresymbolicationd crash x3
   2014-11-05 ProPresenter hang
   2014-11-06 com.apple.WebKit.Plugin.64 crash
Log
   Nov 9 09:13:54 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:14:29 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:14:45 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:15:01 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:15:15 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:15:50 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:16:22 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:16:50 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:17:07 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:17:22 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:17:37 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:17:52 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:18:06 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:18:30 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:18:43 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:19:02 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:19:15 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:19:36 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:19:51 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:20:15 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:20:27 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:20:47 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:21:01 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
   Nov 9 09:22:24 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397676642304.
   Nov 9 09:22:52 CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (UUID), pv UUID, near LV byte offset = 397677387264.
kexts
   tc.tctechnologies.driver.PaeFireStudio (4.0.0 14255)
Daemons
   tc.tctechnologies.daemon.PaeFireStudio
   com.teamviewer.service
   scManagerD
   org.macosforge.xquartz.privileged_startx
Agents
   com.google.GoogleContactSyncAgent
   com.adobe.ARM.UUID
   com.symantec.quickmenu.application
   com.google.keystone.system.agent
   com.apple.photostream-agent
   org.macosforge.xquartz.startx
   com.teamviewer.desktop
   scClient
   com.apple.CSConfigDotMacCert-EMAIL-SharedServices
   com.spotify.webhelper
   com.teamviewer.teamviewer
Startup items
   /Library/StartupItems/NortonMissedTasks/NortonMissedTasks
   /Library/StartupItems/NortonMissedTasks/StartupParameters.plist
   /Library/StartupItems/SMC/SMC
   /Library/StartupItems/SMC/smcdaemon
   /Library/StartupItems/SMC/smclient
   /Library/StartupItems/SMC/StartupParameters.plist
   /Library/StartupItems/SMC/syguard
   /Library/StartupItems/SymAutoProtect/SAVAPComm.kext/Contents/Info.plist
   /Library/StartupItems/SymAutoProtect/SAVAPComm.kext/Contents/MacOS/SAVAPComm
   /Library/StartupItems/SymAutoProtect/StartupParameters.plist
   /Library/StartupItems/SymAutoProtect/SymAutoProtect
   /Library/StartupItems/SymProtector/StartupParameters.plist
   /Library/StartupItems/SymProtector/SymProtector
Bundles
   /System/Library/Extensions/JMicronATA.kext
   - com.jmicron.JMicronATA
   /System/Library/Extensions/PaeFireStudio.kext
   - tc.tctechnologies.driver.PaeFireStudio
   /Library/Audio/MIDI Drivers/PaeFireStudioMIDIDriver.plugin
   - tc.tctechnologies.PaeFireStudio.midiplugin
   /Library/Internet Plug-Ins/AdobePDFViewer.plugin
   - com.adobe.acrobat.pdfviewer
   /Library/Internet Plug-Ins/AdobePDFViewerNPAPI.plugin
   - com.adobe.acrobat.pdfviewerNPAPI
   /Library/Internet Plug-Ins/Flash Player.plugin
   - N/A
   /Library/Internet Plug-Ins/googletalkbrowserplugin.plugin
   - com.google.googletalkbrowserplugin
   /Library/Internet Plug-Ins/JavaAppletPlugin.plugin
   - com.apple.java.JavaAppletPlugin
   /Library/Internet Plug-Ins/o1dbrowserplugin.plugin
   - com.google.o1dbrowserplugin
   /Library/Internet Plug-Ins/Silverlight.plugin
   - com.microsoft.SilverlightPlugin
   /Library/PreferencePanes/Flash Player.prefPane
   - com.adobe.flashplayerpreferences
   /Library/PreferencePanes/SymantecQuickMenu.prefPane
   - com.symantec.quickmenu.prefpane
   /Library/PreferencePanes/SymAutoProtect.prefPane
   - SymAutoProtect
   /Library/Services/ScanService.service
   - com.symantec.ScanService
   Library/Address Book Plug-Ins/SkypeABDialer.bundle
   - com.skype.skypeabdialer
   Library/Address Book Plug-Ins/SkypeABSMS.bundle
   - com.skype.skypeabsms
dylibs
   /usr/lib/libsymsea.1.0.0.dylib
Apps
   /Applications/Dropbox.app
Contents of /Library/LaunchAgents/Safe.Connect.client.plist (checksum 3405402045)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>ExitTimeOut</key>
    <integer>5</integer>
    <key>HopefullyExitsFirst</key>
    <true/>
    <key>KeepAlive</key>
    <false/>
    <key>Label</key>
    <string>scClient</string>
    <key>RunAtLoad</key>
    <true/>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/SafeConnect.app/Contents/MacOS/scClient</string>
    </array>
    <key>WorkingDirectory</key>
    <string>/Applications/SafeConnect.app/Contents/MacOS/</string>
   </dict>
   </plist>
Contents of /Library/LaunchAgents/com.symantec.quickmenu.application.plist (checksum 1217750391)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>KeepAlive</key>
    <true/>
    <key>Label</key>
    <string>com.symantec.quickmenu.application</string>
    <key>ProgramArguments</key>
    <array>
    <string>/Library/Application Support/Symantec/SymQuickMenu/SymQuickMenu.app/Contents/MacOS/SymQuickMenu</str ing>
    </array>
    <key>RunAtLoad</key>
    <true/>
   </dict>
   </plist>
Contents of /Library/LaunchAgents/com.teamviewer.teamviewer.plist (checksum 4172461460)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Debug</key>
    <true/>
    <key>Disabled</key>
    <false/>
    <key>Label</key>
    <string>com.teamviewer.teamviewer</string>
    <key>LimitLoadToSessionType</key>
    <string>Aqua</string>
    <key>OnDemand</key>
    <false/>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/TeamViewer 8/TeamViewer.app/Contents/MacOS/TeamViewer</string>
    <string>--agent</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>WorkingDirectory</key>
    <string>/Applications/TeamViewer 8/TeamViewer.app/Contents/MacOS</string>
   </dict>
   </plist>
Contents of /Library/LaunchAgents/com.teamviewer.teamviewer_desktop.plist (checksum 461628494)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Debug</key>
    <true/>
    <key>Disabled</key>
    <false/>
    <key>Label</key>
    <string>com.teamviewer.desktop</string>
    <key>LimitLoadToSessionType</key>
    <array>
    <string>LoginWindow</string>
    <string>Aqua</string>
    </array>
    <key>OnDemand</key>
    <false/>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/TeamViewer 8/TeamViewer.app/Contents/Resources/TeamViewer_Desktop</string>
    <string>--agent</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>WorkingDirectory</key>
   ...and 3 more line(s)
Contents of /Library/LaunchAgents/org.macosforge.xquartz.startx.plist (checksum 3873345487)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>org.macosforge.xquartz.startx</string>
    <key>ProgramArguments</key>
    <array>
    <string>/opt/X11/lib/X11/xinit/launchd_startx</string>
    <string>/opt/X11/bin/startx</string>
    <string>--</string>
    <string>/opt/X11/bin/Xquartz</string>
    </array>
    <key>Sockets</key>
    <dict>
    <key>org.macosforge.xquartz:0</key>
    <dict>
    <key>SecureSocketWithKey</key>
    <string>DISPLAY</string>
    </dict>
    </dict>
    <key>ServiceIPC</key>
    <true/>
    <key>EnableTransactions</key>
    <true/>
   ...and 2 more line(s)
Contents of /Library/LaunchDaemons/Safe.Connect.plist (checksum 1904970653)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>AbandonProcessGroup</key>
    <true/>
    <key>ExitTimeOut</key>
    <integer>5</integer>
    <key>HopefullyExitsFirst</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
    <key>Label</key>
    <string>scManagerD</string>
    <key>OnDemand</key>
    <false/>
    <key>Program</key>
    <string>/Applications/SafeConnect.app/Contents/MacOS/scManagerD</string>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/SafeConnect.app/Contents/MacOS/scManagerD</string>
    <string>daemon</string>
    </array>
    <key>ThrottleInterval</key>
    <integer>2</integer>
   ...and 4 more line(s)
Contents of /Library/LaunchDaemons/com.teamviewer.teamviewer_service.plist (checksum 3400244753)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Debug</key>
    <true/>
    <key>Disabled</key>
    <false/>
    <key>Label</key>
    <string>com.teamviewer.service</string>
    <key>OnDemand</key>
    <false/>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/TeamViewer 8/TeamViewer.app/Contents/Resources/TeamViewer_Service</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>WorkingDirectory</key>
    <string>/Applications/TeamViewer 8/TeamViewer.app/Contents/Resources</string>
   </dict>
   </plist>
Contents of /Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist (checksum 523110921)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>org.macosforge.xquartz.privileged_startx</string>
    <key>ProgramArguments</key>
    <array>
    <string>/opt/X11/lib/X11/xinit/privileged_startx</string>
    <string>-d</string>
    <string>/opt/X11/lib/X11/xinit/privileged_startx.d</string>
    </array>
    <key>MachServices</key>
    <dict>
    <key>org.macosforge.xquartz.privileged_startx</key>
    <true/>
    </dict>
    <key>TimeOut</key>
    <integer>120</integer>
    <key>EnableTransactions</key>
    <true/>
   </dict>
   </plist>
Contents of /Library/LaunchDaemons/tc.tctechnologies.PaeFireStudio.plist (checksum 2354694686)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>tc.tctechnologies.daemon.PaeFireStudio</string>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <false/>
    <key>ProgramArguments</key>
    <array>
    <string>/Library/Application Support/PaeFireStudio/PaeFireStudioDaemon</string>
    <string>--onDemand</string>
    </array>
    <key>Sockets</key>
    <dict>
    <key>MasterSocket</key>
    <dict>
    <key>SockFamily</key>
    <string>Unix</string>
    <key>SockPathMode</key>
    <integer>438</integer>
    <key>SockPathName</key>
    <string>/var/run/tc.tctechnologies.daemon.PaeFireStudio</string>
   ...and 6 more line(s)
Contents of Library/LaunchAgents/com.adobe.ARM.UUID.plist (checksum 394026997)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>com.adobe.ARM.UUID</string>
    <key>ProgramArguments</key>
    <array>
    <string>/Applications/Adobe Reader.app/Contents/MacOS/Updater/Adobe Reader Updater Helper.app/Contents/MacOS/Adobe Reader Updater Helper</string>
    <string>semi-auto</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>StartInterval</key>
    <integer>12600</integer>
   </dict>
   </plist>
Contents of Library/LaunchAgents/com.apple.CSConfigDotMacCert-EMAIL-SharedServices.Agent.pl ist (checksum 3907645158)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>KeepAlive</key>
    <false/>
    <key>Label</key>
    <string>com.apple.CSConfigDotMacCert-EMAIL-SharedServices</string>
    <key>LimitLoadToSessionType</key>
    <string>Aqua</string>
    <key>LowPriorityIO</key>
    <true/>
    <key>Nice</key>
    <integer>10</integer>
    <key>ProgramArguments</key>
    <array>
    <string>/System/Library/Frameworks/CoreServices.framework/Frameworks/OSServices .framework/Versions/A/Support/CSConfigDotMacCert</string>
    <string>-l</string>
    <string>/Users/USER/Library/Logs/CSConfigDotMacCert.log</string>
    <string>-u</string>
    <string>EMAIL</string>
    <string>-t</string>
    <string>SharedServices</string>
    <string>-s</string>
    </array>
   ...and 4 more line(s)
Contents of Library/LaunchAgents/com.google.GoogleContactSyncAgent.plist (checksum 2135155192)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>com.google.GoogleContactSyncAgent</string>
    <key>LimitLoadToSessionType</key>
    <string>Aqua</string>
    <key>ProgramArguments</key>
    <array>
    <string>/System/Library/PrivateFrameworks/GoogleContactSync.framework/Versions/ A/Resources/gconsync</string>
    <string>--sync</string>
    <string>com.google.ContactSync</string>
    <string>--periodic</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>StartInterval</key>
    <integer>3600</integer>
   </dict>
   </plist>
Contents of Library/LaunchAgents/com.spotify.webhelper.plist (checksum 4140853610)
   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
   <plist version="1.0">
   <dict>
    <key>Label</key>
    <string>com.spotify.webhelper</string>
    <key>KeepAlive</key>
    <dict>
     <key>NetworkState</key>
     <true/>
    </dict>
    <key>RunAtLoad</key>
    <true/>
    <key>Program</key>
    <string>/Users/USER/Library/Application Support/Spotify/SpotifyWebHelper</string>
    <key>SpotifyPath</key>
    <string>/Applications/Spotify.app</string></dict>
   </plist>
Root crontab
   #SqzS VERSION = 1.0.0
   #SYMANTEC SCHEDULER CRON ENTRIES. THESE ENTRIES ARE AUTOMATICALLY GENERATED
   #PLEASE DO NOT EDIT.
   # Enc=1 Name=DefaultLiveUpdateSchedule EvType1=1 EvType2=1 Sched=3
   57 12 * * * "/Library/Application Support/Symantec/Scheduler/SymSecondaryLaunch.app/Contents/schedLauncher" -u 1 "/Applications/Symantec Solutions/LiveUpdate.app/Contents/MacOS/LiveUpdate" "    " "oapp" "aevt" "exAG" "-update LUal"
   #SqzS END SYMANTEC CRON ENTRIES
Global login items
   /Library/Application Support/Symantec/AntiVirus/SAVDiskMountNotify.app
   /Library/Application Support/Symantec/AntiVirus/ScanNotification.app
   /Library/Application Support/Symantec/Scheduler/SymSecondaryLaunch.app
Listeners
   launchd: afpovertcp
   launchd: afpovertcp
   kdc: kerberos
User login items
   encore_reg
   - missing value
   AdobeResourceSynchronizer
   - missing value
Restricted files: 569
Elapsed time (s): 950
Any better news here?

Filevault encryption: no security questions, no recovery code; how to revert?

Running the latest Yosemite (10.10.2) on an iMac (upgraded from Mavericks) ...
I decided I wanted to encrypt the boot drive on our iMac, so I clicked to turn on Filevault. Here's what happened:
I was NOT offered a recovery key. (As this point, I didn't know when the key is normally offered.)
I DID get a window that asked if I wanted Apple to save my key, and I clicked on the radio button to do so. Then I clicked on CONTINUE.
I did NOT get any security questions to answer, just a RESTART button. I thought, maybe the security questions come after the restart.
I clicked on RESTART and the iMac restarted and encrypted the drive (17 hours).
Concerned that I didn't have a recovery key, I read up on the forums. Sounded like if I simply used my user password, I could turn off Filevault to decrypt the drive, and I'd be back to where I started. I did so, and watched as it decrypted the drive (6 hours). Filevault indicates that is is "now off."
I thought I'd try again, so I clicked to turn on Filevault. This time, I did NOT get a recovery key (same as before) and I did NOT get the window asking if I wanted Apple to save my key — only an immediate RESTART button. I canceled.
I restarted the iMac, noting that the startup graphics were different — the iMac now starts immediately with an all-white screen, something that one forum participant said is evidence that your boot drive IS encrypted regardless of what Filevault says.
This concerned me because it now seemed like the drive might be encrypted and I had no recovery key and hadn't been asked any security questions.
I thought if I turned on Filevault I could generate a fresh recovery key that would supplant anything Apple was storing for me — and give me a chance to answer security questions.
I turned on Filevault and was, for the third time, NOT offered a recovery key but this time I DID get the window that asked if I wanted Apple to save my key. Apparently the restart at least added this screen. I cancelled.
So while Filevault says it is off, the immediate white start-up screen suggests the drive may be encrypted. Regardless, Filevault is not offering a recovery key or security questions.
I have sketchy ideas about how to rectify things:
I could start up from an external backup (unencrypted) of the boot drive, erase the boot drive, and clone the backup to the boot drive. Will that create a bootable (non-encrypted) startup drive? I don't think so ...
I could start up from the external backup (unencrypted) of the boot drive, erase the boot drive, then do a clean install of Yosemite on the boot drive. Would that clear any existing encryption? I don't know ...
Or I read about using Terminal to un-encrypt a drive?
Any advice would be much appreciated.
Thanks,
Bradley

Click here for information. If you can't get the answers emailed to you for some reason, contact the iTunes Store staff via the link in that article.
(80111)

Why do I always need to sign in twice?

When I begin the sign in the URL begisn with daw
and my login name is entered [email protected] - and my password appears (as black circles);
when I press enter, the URL begins with appleid
I am then shown a 2nd window that sez I must confirm my login (text appears in red) and the login name is the same as before but without the @mac.com;
all I do is press return and I'm now into the discussions forums.
So why do I have to do this double sign-in every single time?
Annoyance, only, I can always login, but I'm terrified if I ever do anything to screw it up, I'll be hard pressed to make it right agagin.
Thanks for any explanation.

Hello All,
Maybe you have had this issue with other OS X upgrades, but I'm being prompted to log in twice to my MacBook Pro OS X Yosemite (2014 model).
I've upgraded to Yosemite, from Mavericks, without any issues, until I noticed that after turning my computer on and logging in the first time, I see a progress bar load.....then the screen goes black, I hear the restart sound, then the same login screen appears for a second time.
I then enter my credentials a second time, see the progress bar load (a little faster this time), them my desktop appears like normal.
I've read some other, older, posts for older OS X builds but none of them addressed the issue completely.
I've turned OFF filevault, to decrypt my HD, restarted and things seemed okay (1 log in request only). So I turned filevault back on, and the first time I logged in, it worked fine (1 log in request only). However, now, after powering off the computer, I'm back to where I started....2 log in requests before my desktop loads properly.
I don't have the time out setting on "to request password after 60min". I don't have auto login enabled nor parental controls
Filevault is on and my drive is encrypted. No special software loads, just the factory basics...
Any insights or suggestions?

Why do I now HAVE to use i-Cloud to now sync my calander? This is beyond stupid

Why do I now HAVE to use i-Cloud to sync my calander to my i-pad and/or i-phone?
<Edited By Host>

Hello All,
Maybe you have had this issue with other OS X upgrades, but I'm being prompted to log in twice to my MacBook Pro OS X Yosemite (2014 model).
I've upgraded to Yosemite, from Mavericks, without any issues, until I noticed that after turning my computer on and logging in the first time, I see a progress bar load.....then the screen goes black, I hear the restart sound, then the same login screen appears for a second time.
I then enter my credentials a second time, see the progress bar load (a little faster this time), them my desktop appears like normal.
I've read some other, older, posts for older OS X builds but none of them addressed the issue completely.
I've turned OFF filevault, to decrypt my HD, restarted and things seemed okay (1 log in request only). So I turned filevault back on, and the first time I logged in, it worked fine (1 log in request only). However, now, after powering off the computer, I'm back to where I started....2 log in requests before my desktop loads properly.
I don't have the time out setting on "to request password after 60min". I don't have auto login enabled nor parental controls
Filevault is on and my drive is encrypted. No special software loads, just the factory basics...
Any insights or suggestions?

Canceled copy will not close.

I tried to copy a file from my BOOTCAMP partition to my mac for easier access(i have Tuxera NTFS so this is possible) but i changed my mind rather promptly. I hit the cancel button and no its just sitting there saying "Stopping" with a barber pole. Because its doing this, It wont let me do log outs or shut downs. I would just do a hard shut down but im also in the middle of FileVault 2 decrypting my drive and most defiantly dont want to mess that up. any suggestions?

Try - I am not sure whether this will work - going to the Apple Menu, and force restarting finder. I don't know however whether this will stop the FileVault 2 Decrypting process though

Slow login with Domain Mobile Account in 10.9.1

I've tried searching, although I may have missed something. I saw that this was possibly resolved in 10.7, but I'm having the issue with 10.9.1...so...but, if this has been solved and I did miss it when searching, please be gentle. =)
Got a new MBP for work and it's joined to the domain and set up with a mobile account. When I log in from home, I select my account so that FileVault can decrypt the drive, and after the inital spinning wheel, it sits for about 60 seconds before telling me:
"There was a problem connecting to the server "[server name]".
The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again."
Thoughts? Questions that I can try to answer?
Thanks in advance.

here's a picture of the message I get on login, if it helps.

I am not able to use my Mac while FileVault is encrypting. Is it frozen on a gray screen with the apple logo. Is it actually encrypting?

I have an early 2008 MacBook and running iOS Lion. I just turned on FileVault and restarted my computer as instructed. It told me before hand that I would still be able to use my Mac while the files were being encrypted. However, when I logged in on the secure gray login screen, I was only directed to a plain gray screen with the apple logo in the center. There are no time turners or anything moving. Is my Mac encrypting or is it frozen in some sort of way? If it is encrypting, how long does it usually take? and if it is frozen, how do I unfreeze it?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

To Shrink a filevault 2 partition using Disk Utility, decrypt it first

Just a tip for others: while trying to enlarge a bootcamp partition, I discovered that Disk Utility under Mountain Lion 10.8 will give you a strange (and misleading) error if you try to shrink a partition that's encrypted with filevault 2.
The solution is to turn off encryption, let the drive fully decrypt.
Then reboot (if you don't reboot, Disk Utility seems confused and shows a duplicate ghost version of your drive).
Then use DU to resize the partition.

Click the partioned disk > Hit Erase Tab >
Under "Format" Select "MAC OS Extended Journaled, Encrypted
Click "Erase"
Set Password ..
Done

Is it true that FileVault can be decrypted without a key?

Hello,
I just turned on my FileVault 2 like 3-4 hours back and was just web-searching how secure it was.
I happen to come accross a Youtube video and a website that says it can be decrypted without any key.
The software: http://www.lostpassword.com/news/pnl61.htm
Could anyone please tell me if this is true?
Thanks,
Graham Miranda
<Link Edited By Host>

I would not turn on FileVault unless my Macs were in a "hostile" environment. I also do not trust 90% of YouTube's content. You can test this yourself - no need for a second computer: clone your hard drive to an external drive so you have a bootable copy. Then follow the steps shown. If it works, fine. If not, wipe your drive and clone back your system.

Decrypting FileVault Failed and User Account Not Allowing Login

So here is the scenario and my problem. I decided to do a clean install of Leopard on my PowerMac G5 and in doing so used Carbon Copy Cloner to copy all the content of my Macintosh HD drive to another internal DataDrive so that I could get my data later and be able to boot into that old installation of the OS for any reason. After the clone was complete I did a clean install of Leopard onto my Macintosh HD volume.
With the new installation running and updates run I decided to go and get my old data. Turns out I had FileVault protection on in the old installation and could not access my data through the new install. This was the very reason I kept the old installation. I rebooted into the old installation and went to remove FileVault protection. The computer logged out and started decrypting my user folder.
Two hours into the decryption it failed and prompted me to continue and be returned to my login and state before I started the decryption. Now I can't login to that user because when I attempt to it will say that FileVault needs to be repaired and give you the option to repair. The repair takes a while and then give you the error stating the repair didn't work.
So I need help figuring out how to get access to my data in that user folder or get that user folder to work so that I can get my info copied to my new installation. Any ideas would be very much appreciated as I feel like I have lost too much for comfort.
Thanks, Brandon

First of all thank you for the help. In all my trying to figure it out I didn't try just double clicking on the sparse bundle.
Because this was my only user on the computer I had to enable the root user to be able to login. Once that was enable I was able to mount the sparsebundle and copy my data out. I didn't get all of it as something did truly get corrupted during the decryption but I did get 99% I think.
Now with my data coped to another location I can attempt some repairs and see if I am able to get that last percentage point. Thank again.
Brandon

FileVault decryption paused, unable to revert

My 2014 MacBook Pro with OS X 10.10.2 became unusable after a crash where the system became unresponsive and I was forced into a hard reboot. As I was using FileVault, the login screen was appearing soon after rebooting, but would freeze at around 40% after putting in my password, after which the spinning wheel would start. The problem even occurred in Safe Mode.
In looking for a solution, it was recommended that I decrypt the drive using the Disk Utility. However, I received an error when attempting to decrypt. I switched to the Terminal to try manually performing the decrypt operation using diskutil. Unfortunately, when trying 'diskutil cs revert UUID', I received the error "Unable to modify a FileVault context". I then tried both encryptVolume and decryptVolume, but they gave me conflicting messages at the disk was decrypted and encrypted already respectively.
Here is a summary of what I see when I run 'diskutil cs list':
Logical Volume Family UUID
Encryption Status: Unlocked
Encryption Type: AES-XTS
Conversion Status: Converting
Conversion Direction: Backward
|
+-> Logical Volume UUID
Conversion Progress: Paused
Revertible: Yes (unlock and decryption required)

You'll have to erase the volume and then restore the data from a backup.
If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

FileVault 2 - Login issue: Only administrator can decrypt HD?

Hi, I just activated FileVault 2 (Lion) on my MBP (late 2007). Now, when I start the machine, the only user who can log in is the Admin account, not my "normal" user account. This is odd, because during the FileVault setup, I explicitly allowed this user to decrypt my data. Hence, the only way to access my user account is to login as Admin, log off again and then log in as user. The Aplle FileVault manual states that one could easily add users after encryption in Preferences, but I can see no such option on my machine.
Any idea what's wrong here?
Many thanks in advance!
Best, Matthias

Kaufi wrote:
Some idea, anyone?
Have you searches through the articles on the Right of this page under 'More Like This' for a solution? Personally I have never used, and will never use File Vault. But many do, so your solution is more than likely here.
Good Luck
Pete

FileVault frozen decryption

Similar Messages

Maybe you are looking for