It says this everytime I try to download the new content:

The same here. after over 20 times the download completed. While installing the loops it brake up again with the same allert: No internet connection.

and i have to download again.

I`m so angry about.

If I had wished this, i would have purchased a Windows PC!!

Hi Folks,

i just found out, that the download was complete (found all *.pkg - Files in a subfolder from "com.apple.MusicApps")

I copied the finishesd *.pkg - Files to another folder, before Garageband starts its own installation.

Then i installed these *.pkg - files by doubleklick and it worked fine. Only 2 files did not work, so it seems they are not ok. These files are:

MAContent10_GB_StereoDrumKitsRnB.pkg

MAContent10_GB_StereoDrumKitsRock.pkg

When i tried to install them a failure message appears. I think the "no internet connection" message is only a mistake from apple. there should be a message "file corupt" or so.

Sorry for my bad english.

The file "MAContent10_GarageBandCoreContent.pkg" is 1,54 GB from the beggining to the end of the download. Are you sure it is complete?

ok, i have to say that i did not do a GarageBand-Update. I only updated / downloaded the new soundlibrary and new drummers.

I think the "CoreContent" was not updated.

For me, CoreContent was the file that kept downloading, deleting, and re downloading itself until it finally went through the process and finished for good.

Day 4... still failing over and over and over and... two bug reports sent to Apple. Will just keep trying I suppose

appears i finally got it like 3 am EST last night.

one question for users: scrolling through drum kits using arrows they all seem to change in looks except for "Manchester" and "Motown Revisited". Is this what others are seeing?

During this 4 days of trying to update all downloaded and showed up in "List" (not greyed out) except for "Motown Revisted". Then "Manchester" also greyed out on like 20th try, now they all show but again those two look like the same kits?

Thanks

As many guys here, I kept trying and trying and sudently it worked out. Just like that, out of the blue.

Finally I tried the "restore purchase" option and the whole thing finally installed.

Right now installation finished ok. I think it's fixed, I hope...

Me too!! I need to edit sound files now [02:34 AM!!] and I regret I ever tryed to upgrade...

PLEASE HELP NOW !!! 😠😟😮➖⚠😢

Exactly the same problem, here, for 5 days now: absolutely unbebelievable, if this is a still unsolved Apple server problem (I agree that it mainly seems to be a problem with the "CoreContent" package, BTW)...

We need some help, here, Apple! :-)

As it also seemed to be a problem with authentication of the downloaded package(s), I tried to delete everything inside /private/var/folders/ (containing temporary and cache-like items, which are regenerated the next time), and then restarted and opened GarageBand again, letting it redownload the two remaining packages: well, this time finally it worked, even if I had to retry once again for the last package.

Don't know if it really was the clearing of /private/var/folders/, or simply a coincidence - anyway, perhaps worth trying, at least if everything else fails...

Well, the problem now seems to have been solved: on two other Macs, simply letting GarageBand resume the download - which IIRC took longer than before - was then followed by a sucessful install (and with no need to tinker with hidden folders, reinstalls, etc. etc.)... 🙂

Also had the same problem when trying to update.Always stalled when trying to install the last part, i.e. additional drummers etc. (..must be connected to the internet)

Since I´ve come across that problem when iworks was updated the last time I used the same solution.

Opening the appstore and logging in, then restart garageband while still being logged in to my account at the appstore.

And this time the installation completed without problem.

I don´t know if that´s a coincidence but I think it´s worth a try.

Since the additional stuff is from an inApp purchase it may be that you have to be logged in.