Can't Verify OSX Mavericks Download

Is your machine stock or has it got any upgrades? Just curious, because on 2 machines I had the same issue, though they were upgraded with 16GB RAM, though using the exact same install file i downloaded (and copied to a usb stick), had failed. The fix: Droping the RAM to 4GB which worked a treat (using the same file to install copied from the USB stick).

Call it co-incidence or not, that was 2 machines in a row. Though the first one, i thought was happy after changing the power settings and then downloading it again which then didnt install and came up with the same error as you. I just didnt see the error until i got home, which pointed me to think it might be a hardware issue.

Either way - you may be right still. You could test it though - stop the network connection (wired/wireless) after the file is downloaded and try the installation. See if it asks you to connect to the internet.

Thank you, Skitts! My RAM was the culprit. It passed memtest in single user mode... but it's still "off" somehow. Downloads 1-21 were bad... All had varying checksums and even different file sizes. Downloads 22 and 23 were identical, yet neither worked. That's when I decided to swap out my RAM with some from a Mac Mini... It's installing now. Thanks again!

For some - commercial I guess - strange reason not all Macs can host the same amount of memory, even if they are from the same period of the year.

For example, my MacBook Pro mid 2010 15" can host up to 8GB even if I had choose the top processor and monitor type. Conversely the 13" from the same season can go up to 16GB.

You should check specification from this site http://www.everymac.com/systems/apple/macbook_pro/index-macbookpro.html, which reports the maximum ram too.

Thank you guys! As it turned out it is RAM for me. My MBP have been crashing for a month or so I thought it is something to do with my OS or other software. This is one of the reason I desperately wanted to update to New OS. Luckily, I had my old RAM sticks, I swapped my old RAM sticks. First, I was able to do Diagnostic test. That is good sign. Previously, I was getting 6002D. Mavericks update went through without any problem...oh! yes no more crashing.

For anyone that is still running into this issue and the RAM fix doesn't work for you - here is an alternative:

Video on YouTube to watch if necessary:

http://www.youtube.com/watch?v=vu9tU0c1Uk0

Use this terminal (to open terminal go to /Applications/utilities) command to show hidden files:

defaults write com.apple.finder AppleShowAllFiles TRUE

killall Finder

Make sure to run the second command to refresh the Finder process.

Right click and show package contents of the Install OS X Mavericks.app, which can be found after App Store download in /Applications

Navgiate to /Contents/Shared Support and mount the OSX Install ESD.dmg

Inside the mounted OSX Install ESD.dmg open up BaseSystem.dmg

Open Disk Utility and restore the BaseSystem.dmg to the external HD or USB Drive you're booting from.

After this is complete go to /System/Installation on your Hard Drive/USB Drive and delete the packages shortcut.

Navigate back into the OSX Install ESD.dmg and find the folder named 'Packages' and copy this to the place where you deleted the shortcut in ' /System/Installation' on your Hard Drive/USB Drive.

Once this is complete eject your drive and reboot and try an install from there.

This is only a suggestion and this is what worked for me. It has also worked many times with previous OSX installs.

So, finally I've got it!

I planed to buy ethernet-usb adaptor today, to download it via ethernet cable, but decided to try one more time. And it worked without a problem!

I don't know what was the reason of this mistake yesterday (maybe extremely big load of the apple services?) - but now everything is ok.

I had the same issue. Downloaded around 10 times using all methods given below. Finally read somewhere online to start my Mac in safe mode and update and it worked with the same file that couldn't be verified in the regular mode!

OK, after at least 20 attempts at downloading Mavericks from the Apple store and getting the same issue as the other people in this thread, I downloaded a Bittorrent copy of Mavericks and used that for the installation. It worked perfectly.

What this proves to me is that there is some sort of corruption occurring to the file during the download process from the Apple store, but how and why this is occurring, I cannot say.

What I would say to you, is that there are Maverick downloads available from Bittorrent that will work perfectly well. I can't post links to such things for obvious reasons.

jeez, apple. Can't we check the data periodically during the download process. Must we wait until we have completly downloaded the 5.3 GB file and then find out is corrupt. It seems the answer is retry or obtain from a bittorrent pirate site. Nice way to roll out a product. I am on a DLS line and it took me 24 hours to download attempt #1. It appears that I need to keep trying....5 or 6 times. I am sure the ISP/NSP's are loving this, multipe users downloading 5GB files repeatedly. Is the Mavericks rollout being handled by the Apple Maps team?

After 6 times I finally installed Mavericks.

On the 5th time. I watched the whole downloading, and I found out at the time it almost finished downloading and it just jump to finish.

So I guess it hadn't been fully downloaded. The problem may be caused by Apple servicer. I think this is why every time when I check MD5 it was different.

On the 6th time, I downloaded still 3.7gb, then I paused downloading. Restarted my MBA. Once it restarted, I resumed downloading and this time it was successfully downloaded. Installed it with no problem.

This method suit my MBA purchase few days ago.

P.S. I also tried checking ram, verifying disk and creating a new admin user, but those methods are not working for me.

Hello everyone,

After numerous tries on day one and two, reading several posts, and taking a day of break from this craziness. I gave it another shot today and I was finally able to install OS X Mavericks! Whoot, whoot! Here's what I did, I hope it works for someone as well.

1. Download a fresh copy (make sure you don't let your MAC go to sleep while downloading)

2. Unplug anything connected in the back of your MAC (except your power cord, of course) 😉

3. Create a new profile (one with full admin rights)

4. Restart and log in with the new profile

5. Install OS X Mavericks from your Launchpad

That's it! Like I said, it worked. I have tried all sorts of attempts suggested by several folks, except for removing my extra 4 Gigs of RAM, as someone suggested in one of this thread, which would have been my next step had this not worked. Anyway, good luck!

Hi All

Computer: MBP Mid 2009

I have been able to install my copy of Mavericks after facing this issue, by abandoning the usb boot drive.

I was trying to install to a freshly erased ssd from a usb boot drive that I made according to the instructions from Macworld. I tried several times to no avail and kept getting the message as per the OP.

What I then elected to do was use my bootable clone of Mountain Lion on a portable HDD, and boot the MBP from this drive. I then used the Mac App Store to download the installer for Mavericks.

On first try my erased SSD was not mounted, so I zapped the PRAM and rebooted from the clone and there she was.

I then proceeded to install mavericks to the fresh SSD inside the MBP - note you must select this drive during the install process.

Hope this helps some of you - It is also a reminder to me to always do a backup before upgrading.

Cheers

Steve

Yesterday I've installed it on two airs that had the same problem before. I've changed nothing, just downloaded it as usual and everything was ok.

I suppose that the problew was because of apple services were extremely loaded.

Finally it worked for me!!

After 5 attempts of downloading it at home with my two different wifi-networks, i had no success.

But then i tried it with the wifi-network of my parents, so different wifi and different internet-connection.

-> It worked, and no errors or so.

I can say, the problem was my internet connection!!