When I installed Windows with Boot Camp, I only allocated about 32GB for the C: drive. Unfortunately, it didn’t take long to run out of space even though I don’t use it much. Turning off hibernation freed up space, but not enough to resolve the problem. The next step was to re-size the partition, which is slightly harder than it sounds.

Reduce Size of Mac Partition

Open Disk Utility, and select the top level of the internal SSD/HDD. Then click Partition at the top. Select your Macintosh HD partition, then under Partition Information > Size, reduce the size of the partition. Note that you are limited by how much space is already used (this amount is listed just below the Size text field). Click Apply.

Increase Size of Boot Camp Partition

If resizing Macintosh HD is successful, your next step is to boot into Windows. Open the Start menu, then type Disk Management. Look for your C: drive. Disk Management will only allow you to extend the C: partition if the free space you just created is to the right of it. If it is listed to the left, you must use a free 3rd party utility like MiniTool Partition Wizard Free. Here’s their tutorial on the Move/Resize Partition feature.

Please let me know if this short guide helps you.

Introduced in Mac OS 10.7, Resume re-opens apps and files at login. It’s terrible. Thankfully, I found one simple command line that fixes this:

defaults write -g ApplePersistence -bool no

I love VMware Fusion 8, but only Boot Camp will let me use two sound devices at once. Boot Camp Assistant, though, was unable to partition my disk to make room for Windows (this is a recurring theme starting with Mac OS 10.10). This article provides the perfect solution to Boot Camp Assistant’s Disk could not be partitioned error.

Great thanks to Cody Burleson for writing [these instructions](https://codyburleson.com/blog/shrink-windows-vm-on-vmware-fusion-for-mac). My VM was nearly 55GB; it is now just over 24GB. Make sure, though, that there is no unallocated portion of the C: drive in Windows, as this method will not touch them.

Today I learned (thanks, Mom!) that iPhones with iOS 9 allow the sharing of voicemails to your app of choice.

1. Tap the voicemail.
2. Tap the Share button.
3. Choose where to share it.

So, for example, when Volkswagen says that your diesel vehicle’s emissions are compliant with federal regulations, you have proof they lied (without cluttering your voicemail inbox).

FileVault 2 offers a great service: it encrypts the entire storage of your Mac. However, many people have experienced a problem. It doesn’t finish (for the record, this happened to me on 10.10.5. Some said the issue was resolved with 10.10.3). We see messages like:

Encrypting… Estimating time remaining


Unfortunately, this causes problems when upgrading OS X or trying to create a Boot Camp partition. Since FileVault shows as enabled and the drive shows as encrypted, I decided to decrypt the drive. This is done by:

  1. Booting into Recovery HD (restart the computer and hold Cmd+R until the Apple logo and progress bar appear).
  2. Open Disk Utility.
  3. Select the encrypted drive (it should be grayed out in the sidebar).
  4. Go to File > Unlock Macintosh HD, and enter password
  5. Go to File > Turn Off Encryption, and enter password.
  6. Reboot to OS X.

Ah, good. In a fairly short period of time, I should have my drive back. Except … decryption has the same problem! Interestingly, decryption becomes unpaused during disk verification (Open Disk Utility, select both “Macintosh HD” in the sidebar, and click Verify Disk). This lasts only a few minutes, however. I ended up using Verify Disk a number of times until decryption finished.

Once I installed El Capitan, I tried encryption again and encountered the same issue. So I continually ran First Aid until encryption finished. If you want a Boot Camp partition, however, you’ll probably need to wipe the drive and start fresh.


UPDATE 11/11/2015: Try the solution mentioned on this post.

FileVault 2 offers a great service: it encrypts the entire storage of your Mac. However, many people have experienced a problem. It doesn’t finish (for the record, this happened to me on 10.10.5. Some said the issue was resolved with 10.10.3). We see messages like:

Encrypting… Estimating time remaining


Unfortunately, this causes problems when upgrading OS X or trying to create a Boot Camp partition. Since FileVault shows as enabled and the drive shows as encrypted, I decided to decrypt the drive. This is done by:

  1. Booting into Recovery HD (restart the computer and hold Cmd+R until the Apple logo and progress bar appear).
  2. Open Disk Utility.
  3. Select the encrypted drive (it should be grayed out in the sidebar).
  4. Go to File > Unlock Macintosh HD, and enter password
  5. Go to File > Turn Off Encryption, and enter password.
  6. Reboot to OS X.

Ah, good. In a fairly short period of time, I should have my drive back. Except … decryption has the same problem! Interestingly, decryption becomes unpaused during disk verification (Open Disk Utility, select both “Macintosh HD” in the sidebar, and click Verify Disk). This lasts only a few minutes, however. I ended up using Verify Disk a number of times until decryption finished.

Once I installed El Capitan, I tried encryption again and encountered the same issue. So I continually ran First Aid until encryption finished. If you want a Boot Camp partition, however, you’ll probably need to wipe the drive and start fresh.


UPDATE 11/11/2015: Try the solution mentioned on this post.

My mom has an iPhone 5 on Virgin Mobile. Every time she updates iOS, the iPhone deactivates. In the past, I would call Virgin Mobile technical support for reactivation, but:

  • they aren’t open 24/7.
  • they take a long time.
  • they’ve threatened to charge me before.
  • I hate being on the phone.

After searching the interwebs mostly unfruitfully, I came across the following solution in an Apple Support forum. (Sorry, I couldn’t find it again.)

  1. Backup the iPhone.
  2. Erase all contents and settings.
  3. Restore the iPhone from your backup.

This worked successfully for us. The phone did not activate the first time during setup, but on the second try. I hope other webizens in need find this, and find it useful.