Menu
Which version of GarageBand do you have installed? If you are currently using GarageBand 6.0.5, you are running the latest version of GarageBand '11. Then there is no need to update.But if you want to update to GarageBand 6.0.5 and you installed GarageBand '11 from an iLife DVD, use the Downloads page to download the updater to GarageBand 6.0.5.
Garageband for PC Download without Bluestacks (Windows 10, 8, 7) – The new in thing for aspiring musicians and DJ’s is the Garageband. It is an app developed by Apple for iOS and MAC users that provide tools for spinning new and catchy tunes. Gone are the days when you would require a complete studio. A new Mac and I wanted to put the old (6.0.5) version of GarageBand. Hey guys I tried to download it ( currently on high Sierra 10.3.3 ).
See this link:If you want to update to the newest GarageBand 10, it requires a purchase from the AppStore. GarageBAnd 10 is a major new release and not a free update to GarageBAnd 6.0.5. Try to update using the download from the support page:It should work, if your Mac came with MacOS X 10.6.8 or earlier and installer DVDs. If GarageBAnd came preinstalled with MacOS X 10.7 or newer, you need to install the update from the AppStore, however. Then check, if GarageBand is showing on the Purchases tab of the AppStore. If GarageBAnd is not showing in your Purchases history, you may be using a different AppleID from the one you were using when you set up your Mac. Or may have moved to a different country Then sign into the AppStore with your original AppleID.
The download didn't work. 'GarageBand6.0.5Update.pkg can't be installed because its digital signature is invalid'. Failed numerous times.
Garageband is not showing in purchased tab. Probably different Apple ID too old to remember. I'm done with this and ready to move it to the trash and delete it.
Are there any potential issues with that? Also, while I truly appreciate your help, are you an Apple employee? I ask because I need sound advise from someone qualified regarding deleting this application. The download didn't work. 'GarageBand6.0.5Update.pkg can't be installed because its digital signature is invalid'. Failed numerous timesThat is a problem of the system date.
The GarageBand 6.0.5 update is more than three years old and Apple's certificates do expire. Set the date of your Mac back three years (in the System Preferences Date&Time) and then try again to run the installer. Three years ago the signature will have been valid.I'm done with this and ready to move it to the trash and delete it. Are there any potential issues with that?GarageBand is not part of the system and it is safe to remove it. Only you will not be able to reinstall GarageBand '11 it if you ever want to use GarageBand. You will have to buy the new GarageBand 10, that does not support all features of GarageBand '11.Also, while I truly appreciate your help, are you an Apple employee?This is a User to User forum.
We are all users like you here. If you want help from an Apple employee use the support page.
Apple Footer.This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
For about 4 days App Store has been telling me that there is an updater to GarageBand 6.0.5 available. However whenever I click the Update button and enter my Apple ID, after a few seconds App Store says 'This item is temporarily unavailable. Try again later.' I have experienced this on both my MacBook Pro and my Mac Pro, so it is unlikely to be a single-machine incompatability. However both of these machines are running OS X 10.10.5, FWIW.The updater was released March 7, 2012.
My MacBook Pro has GarageBand 6.0.4, which is called GarageBand '11 (I haven't even looked at the version on my Mac Pro, since there isn't even the faintest chance I would ever run GarageBand on it).It's taking Apple a long time to fix whatever the problem is.David H. At least I'm not the only one experiencing this.However I'm not about to do what Carhole did to fix it, which is to reboot into OS X 10.11. So it seems that Apple may have done something to App Store that makes Updates not work for us laggards.Given my experiences back in July(?) trying to download OS X 10.10.3 onto the newly-installed second drive on my inherited Mac Pro, where App Store was insisting that I verify my credit card info even though I've never bought anything from App Store, it'll take about a week for Apple to recognize/fix the bug.David H.
Further results:(1) Clicking on name of update at left of Updates window in App Store produces dialog with message 'The item you've requested is not currently available in the U.S. As to that, look at my Tribus. Oh to be in England, now that Fall is here.(2) On my Mac Pro, App Store now reports a second update available, for iPhoto 9.6.1 (which I already installed on my Mac BookPro 9/4/2015). Same results trying to update that.(3) I have now put this on Apple Bug Reporter as #22967682.David H. IPhoto and Aperture updates were unavailable for me. But I found that I could install them after simply removing the apps. I don't have Garage band.I don't have either GarageBand or iPhoto installed on my Mac Pro, which—insofar as its 'Macintosh HD New' boot drive is concerned—is simply a cheap (I inherited it) substitute for a Mac Mini as an OS X 10.10.5 Retrospect backup server.
But, as reported above, my Mac Pro has the same kind of App Store problem my MacBook Pro does.Dare I suggest that, given your French-sounding user name and the time-of-day you posted (I'm merely a late-rising insomniac), you may be a European? I suspect this problem includes an Apple screw-up involving U.S. Versus foreign App Stores.David H. It's more likely to be a local networking problem confined to the area you are in. If the App Store was FUBAR then there would be more than just one person complaining.
The quick way to check is to log into a VPN based somewhere else and then try.The App Store generally asks for card verification if nothing has been bought for a while.Since I am retired, I don't have access to a VPN. Given that the MacBook Pro is a laptop, I could eventually haul it up to one of my brothers' apartments and try accessing App Store from there. I think my youngest brother has Time Warner.
As you—JoelB—should well know by now, my little two-room apartment LAN is connected to DSL from big old Verizon. The fact is I don't use GarageBand even on my MacBook Pro; I just like to keep my apps updated.It may not look that way from across the Pond, but Hawaii—where Carhole (as linked to in my second post in this thread) resides—is a long way from New York City. And Iowa—where LtKernelPanic who reported also having the problem in a post just after yours resides—is also a long way from NYC.
So this is not 'likely to be a local networking problem confined to the area you are in'. OTOH years ago Hawaii used to be covered by GTE, but I think GTE's phone system was subsequently sold to Verizon.
So maybe 'confined to the area you are in' is true, if you define 'the area you are in' as anywhere in the U.S.A. Covered by Verizon.BTW, thank you in your post for unintentionally classifying the problem I had with App Store in July as a canonical example of a 'conceptual bug'. The temporarily-difficult-to-grasp (for Apple) concept being that someone might use the App Store for free downloads but never buy anything there.
As I said, that problem cleared up after about a week, despite my not having done anything about it. I suspect this problem, too, is an example of a complicated 'conceptual bug' resulting from changes to App Store for OS X 10.11. With my prodding them, Apple will fix it eventually.David H.
It's more likely to be a local networking problem confined to the area you are in. If the App Store was FUBAR then there would be more than just one person complaining.
The quick way to check is to log into a VPN based somewhere else and then try.The App Store generally asks for card verification if nothing has been bought for a while.Since I am retired, I don't have access to a VPN. Given that the MacBook Pro is a laptop, I could eventually haul it up to one of my brothers' apartments and try accessing App Store from there. I think my youngest brother has Time Warner. As you—JoelB—should well know by now, my little two-room apartment LAN is connected to DSL from big old Verizon. The fact is I don't use GarageBand even on my MacBook Pro; I just like to keep my apps updated.It may not look that way from across the Pond, but Hawaii—where Carhole (as linked to in my second post in this thread) resides—is a long way from New York City. And Iowa—where LtKernelPanic who reported also having the problem in a post just after yours resides—is also a long way from NYC. So this is not 'likely to be a local networking problem confined to the area you are in'.
OTOH years ago Hawaii used to be covered by GTE, but I think GTE's phone system was subsequently sold to Verizon. So maybe 'confined to the area you are in' is true, if you define 'the area you are in' as anywhere in the U.S.A. Covered by Verizon.BTW, thank you in your post for unintentionally classifying the problem I had with App Store in July as a canonical example of a 'conceptual bug'.
The temporarily-difficult-to-grasp (for Apple) concept being that someone might use the App Store for free downloads but never buy anything there. As I said, that problem cleared up after about a week, despite my not having done anything about it. I suspect this problem, too, is an example of a complicated 'conceptual bug' resulting from changes to App Store for OS X 10.11. With my prodding them, Apple will fix it eventually.David H.Free VPN services are available on the Internet. Just search for them.You need to work whether:.
It's a local networking problem. A problem with the App Store App. A problem with the App Store itselfIt is likely to be a problem somewhere around the first or second reasons.My advice would be to upgrade to 10.11. I suspect I will get a long, multi-paragraph explanation of why this is beyond you.Apple is most likely to fix problems with 10.11. Fixing problems with 10.10 is now unlikely.
Apple usually only fix security bugs in their old operating systems. BTW, thank you in your post for unintentionally classifying the problem I had with App Store in July as a canonical example of a 'conceptual bug'. The temporarily-difficult-to-grasp (for Apple) concept being that someone might use the App Store for free downloads but never buy anything there. As I said, that problem cleared up after about a week, despite my not having done anything about it. I suspect this problem, too, is an example of a complicated 'conceptual bug' resulting from changes to App Store for OS X 10.11. With my prodding them, Apple will fix it eventually.David H.You can set up an Apple Id account without a credit card. It took me a whole 10 seconds to Google that info.
That's been available for months. It's more likely to be a local networking problem confined to the area you are in. If the App Store was FUBAR then there would be more than just one person complaining. The quick way to check is to log into a VPN based somewhere else and then try.Since I am retired, I don't have access to a VPN. Given that the MacBook Pro is a laptop, I could eventually haul it up to one of my brothers' apartments and try accessing App Store from there. I think my youngest brother has Time Warner.
As you—JoelB—should well know by now, my little two-room apartment LAN is connected to DSL from big old Verizon. The fact is I don't use GarageBand even on my MacBook Pro; I just like to keep my apps updated.It may not look that way from across the Pond, but Hawaii—where Carhole (as linked to in my second post in this thread) resides—is a long way from New York City. And Iowa—where LtKernelPanic who reported also having the problem in a post just after yours resides—is also a long way from NYC.
So this is not 'likely to be a local networking problem confined to the area you are in'. OTOH years ago Hawaii used to be covered by GTE, but I think GTE's phone system was subsequently sold to Verizon. So maybe 'confined to the area you are in' is true, if you define 'the area you are in' as anywhere in the U.S.A.
Covered by Verizon.David H.Free VPN services are available on the Internet. Just search for them.You need to work whether:. It's a local networking problem. A problem with the App Store App. A problem with the App Store itselfIt is likely to be a problem somewhere around the first or second reasons.My advice would be to upgrade to 10.11. I suspect I will get a long, multi-paragraph explanation of why this is beyond you.Apple is most likely to fix problems with 10.11. Fixing problems with 10.10 is now unlikely.
Apple usually only fix security bugs in their old operating systems.One thing to keep in mind; per the last sentence of my first paragraph quoted in this post, I don't particularly care if this problem is fixed quickly. I only posted the problem because other people running OS X. BTW, thank you in your post for unintentionally classifying the problem I had with App Store in July as a canonical example of a 'conceptual bug'. The temporarily-difficult-to-grasp (for Apple) concept being that someone might use the App Store for free downloads but never buy anything there. As I said, that problem cleared up after about a week, despite my not having done anything about it. I suspect this problem, too, is an example of a complicated 'conceptual bug' resulting from changes to App Store for OS X 10.11.
With my prodding them, Apple will fix it eventually.David H.You can set up an Apple Id account without a credit card. It took me a whole 10 seconds to Google that info. That's been available for months.Yes, I set up an Apple ID account without a credit card when I upgraded my MacBook Pro from OS X 10.6 to OS X 10.10.2 sometime this spring. I successfully updated the MBP from the App Store to OS X 10.10.3 later this spring, and ran other Updates from the App Store to the MBP.All of a sudden in July I could not use App Store to download OS X 10.10.3 to the new drive on my Mac Pro, because it wanted me to verify a credit card I had never given it. I then tried to use App Store to download OS X 10.10.3 to an external drive on my MBP to be copied to the Mac Pro, and I couldn't do that either for the same reason.
About a week later the App Store demand for credit card verification simply went away, and I was able to use App Store to download OS X 10.10.3 to the new drive on my Mac Pro.My conclusion is that there was a 'conceptual bug' in the App Store in July that Apple fixed. I still have not given App Store a credit card.David H. FYI, Apple Bug Reporter now says, of my bug report 22967682, 'Duplicate of 22918688 (Open)'. As a result, I'm not going to bother finding a free VPN in order to test whether this is a local networking bug.BTW, does anyone know how to look at other people's bug reports on Apple bug Reporter?David H.AFAIK you can't unless you are an Apple employee. So unless you know what Bug # 22918688 is it would best to continue to research the issue. 'Duplicate of' just means there's someone else with the same symptoms as you. Hi,I'm located in the UK, using a MacBook Air, and also experiencing the same issue.
I don't think there is a block from an operator (following the comment of another user about Verizon), therefore I suspected that this was more an issue with AppStore.Before I had the same issue with iMovie (last year). I had to follow some instructions from one article to get that fixed. I'm not finding that article, or new ones to help resolving this problem with GarageBand either.Today I had a new upgrade being pushed for updating iMovie and I could successfuly have this done this time.
So I started to look for this in an Apple Forum, and the new version of GarageBand is the 10. There are no upgrades after 6.0.5. Therefore this is a bug in their AppStore.I updated the forum. You can see there my screenshot of what I'm seeing on my computer attached there.Hopefully we will get a resolution soon.Cheers,Adriana. This morning, when I booted my Mac Pro to run the daily incremental backup of my MBP using Retrospect 12.5, I saw—as I had expected—that App Store was showing iMovie 10.1 as being available for the Mac Pro. It installed apparently fine; clicking the Open button for iMovie in the Updates panel of App Store starts the app, although (unlike on the MBP) there is no iMovie icon in Applications on the Mac Pro.
Since I am photographically illiterate, I have not attempted to do anything with iMovie on either machine.However, on my Mac Pro, App Store is still showing both Garage Band 6.0.5 and iPhoto 9.6.1 as '. Not currently available in the U.S. If you follow the link in adriviola's post just above this, you will appreciate that the unavailability of these Updates is a worldwide App Store configuration problem having to do with 'obsolete' versions of Apple apps. I strongly suspect this will be solved, not by Apple programmers, but by Apple marketing people after occult communication with the spirit of SJ. Or, put another way, Apple is doing this intentionally.David H.
This morning, when I booted my Mac Pro to run the daily incremental backup of my MBP using Retrospect 12.5, I saw—as I had expected—that App Store was showing iMovie 10.1 as being available for the Mac Pro. It installed apparently fine; clicking the Open button for iMovie in the Updates panel of App Store starts the app, although (unlike on the MBP) there is no iMovie icon in Applications on the Mac Pro. Since I am photographically illiterate, I have not attempted to do anything with iMovie on either machine.However, on my Mac Pro, App Store is still showing both Garage Band 6.0.5 and iPhoto 9.6.1 as '. Not currently available in the U.S. If you follow the link in adriviola's post just above this, you will appreciate that the unavailability of these Updates is a worldwide App Store configuration problem having to do with 'obsolete' versions of Apple apps. I strongly suspect this will be solved, not by Apple programmers, but by Apple marketing people after occult communication with the spirit of SJ.
Or, put another way, Apple is doing this intentionally.David H.Yes, because Apple is out to get you. This morning, when I booted my Mac Pro to run the daily incremental backup of my MBP using Retrospect 12.5, I saw—as I had expected—that App Store was showing iMovie 10.1 as being available for the Mac Pro. It installed apparently fine; clicking the Open button for iMovie in the Updates panel of App Store starts the app, although (unlike on the MBP) there is no iMovie icon in Applications on the Mac Pro. Since I am photographically illiterate, I have not attempted to do anything with iMovie on either machine.However, on my Mac Pro, App Store is still showing both Garage Band 6.0.5 and iPhoto 9.6.1 as '. Not currently available in the U.S. If you follow the link in adriviola's post just above this, you will appreciate that the unavailability of these Updates is a worldwide App Store configuration problem having to do with 'obsolete' versions of Apple apps. I strongly suspect this will be solved, not by Apple programmers, but by Apple marketing people after occult communication with the spirit of SJ.
Or, put another way, Apple is doing this intentionally.David H.Yes, because Apple is out to get you.Yes, JoelB, but (assuming you are even semi-serious in your post) the reason Apple is out to get me—as they are out to get adriviola—is because we haven't spent enough money in the App Store on new versions of Apple apps. I don't know about adriviola, but please remember that I have not yet given App Store my credit card. Somewhere in Cupertino there's undoubtedly a task force periodically meeting about us 'problem' Apple customers.David H. This morning I found App Store had 3 new updates for my MacBook Pro running OS X 10.10.5: iTunes 12.3.1, Safari 9.0.1, and Security Update 2015-004. I installed them.
App Store for my Mac Pro had the same 3 new updates; I installed those there, too.App Store on my MBP still says GarageBand 6.0.5 is 'not currently available in the U.S. App Store on my Mac Pro still says the same thing, but also still says it for iPhoto 9.6.1 (which, as I mentioned several posts above, I updated on the MBP on September 4th).This increasingly sounds like a configuration problem on App Store itself, especially since my MBP version of App Store.app was last updated on August 13th. As I've paranoidically (paranoidially, paranoidly?) said I don't think this is a case of 'the right hand not knowing what the left hand is doing', but of the right hand—AKA Apple Marketing—specifically telling the left hand what to do.David H. This morning I found App Store had 3 new updates for my MacBook Pro running OS X 10.10.5: iTunes 12.3.1, Safari 9.0.1, and Security Update 2015-004. I installed them.
App Store for my Mac Pro had the same 3 new updates; I installed those there, too.App Store on my MBP still says GarageBand 6.0.5 is 'not currently available in the U.S. App Store on my Mac Pro still says the same thing, but also still says it for iPhoto 9.6.1 (which, as I mentioned several posts above, I updated on the MBP on September 4th).This increasingly sounds like a configuration problem on App Store itself, especially since my MBP version of App Store.app was last updated on August 13th.
As I've paranoidically (paranoidially, paranoidly?) said I don't think this is a case of 'the right hand not knowing what the left hand is doing', but of the right hand—AKA Apple Marketing—specifically telling the left hand what to do.David H.Given that GarageBand 10 is a free update how does Apple benefit from this.?FWIW I can see the update to Garageband 10.1 but it doesn't appear to download. But this is very low priority for me as I've never used Garageband.
This morning I found App Store had 3 new updates for my MacBook Pro running OS X 10.10.5: iTunes 12.3.1, Safari 9.0.1, and Security Update 2015-004. I installed them. App Store for my Mac Pro had the same 3 new updates; I installed those there, too.App Store on my MBP still says GarageBand 6.0.5 is 'not currently available in the U.S. App Store on my Mac Pro still says the same thing, but also still says it for iPhoto 9.6.1 (which, as I mentioned several posts above, I updated on the MBP on September 4th).This increasingly sounds like a configuration problem on App Store itself, especially since my MBP version of App Store.app was last updated on August 13th.
As I've paranoidically (paranoidially, paranoidly?) said I don't think this is a case of 'the right hand not knowing what the left hand is doing', but of the right hand—AKA Apple Marketing—specifically telling the left hand what to do.David H.Given that GarageBand 10 is a free update how does Apple benefit from this.?FWIW I can see the update to Garageband 10.1 but it doesn't appear to download. But this is very low priority for me as I've never used Garageband.On App Store from my MBP, GarageBand 10.1 is $4.99. That doesn't sound like a free update to me, but things may be different in Blighty. As for iPhoto 9.6.1, I won't bother to insult the intelligence and knowledge of other readers by detailing the deficiencies and pitfalls of Photos vs. IPhoto.David H. This morning I found App Store had 3 new updates for my MacBook Pro running OS X 10.10.5: iTunes 12.3.1, Safari 9.0.1, and Security Update 2015-004. I installed them.
App Store for my Mac Pro had the same 3 new updates; I installed those there, too.App Store on my MBP still says GarageBand 6.0.5 is 'not currently available in the U.S. App Store on my Mac Pro still says the same thing, but also still says it for iPhoto 9.6.1 (which, as I mentioned several posts above, I updated on the MBP on September 4th).This increasingly sounds like a configuration problem on App Store itself, especially since my MBP version of App Store.app was last updated on August 13th. As I've paranoidically (paranoidially, paranoidly?) said I don't think this is a case of 'the right hand not knowing what the left hand is doing', but of the right hand—AKA Apple Marketing—specifically telling the left hand what to do.David H.Given that GarageBand 10 is a free update how does Apple benefit from this.?FWIW I can see the update to Garageband 10.1 but it doesn't appear to download.
But this is very low priority for me as I've never used Garageband.On App Store from my MBP, GarageBand 10.1 is $4.99. That doesn't sound like a free update to me, but things may be different in Blighty. As for iPhoto 9.6.1, I won't bother to insult the intelligence and knowledge of other readers by detailing the deficiencies and pitfalls of Photos vs. IPhoto.David H.I think it's very unlikely that Apple are specifically withholding an update just so they can get users to fork out $ 4.99 for the new version.App Store on my MBP still says GarageBand 6.0.5 is 'not currently available in the U.S. App Store on my Mac Pro still says the same thing.This increasingly sounds like a configuration problem on App Store itself, especially since my MBP version of App Store.app was last updated on August 13th.
As I've paranoidically (paranoidially, paranoidly?) said I don't think this is a case of 'the right hand not knowing what the left hand is doing', but of the right hand—AKA Apple Marketing—specifically telling the left hand what to do.David H.Given that GarageBand 10 is a free update how does Apple benefit from this.?FWIW I can see the update to Garageband 10.1 but it doesn't appear to download. But this is very low priority for me as I've never used Garageband.On App Store from my MBP, GarageBand 10.1 is $4.99.
That doesn't sound like a free update to me, but things may be different in Blighty.David H.I think it's very unlikely that Apple are specifically withholding an update just so they can get users to fork out $ 4.99 for the new version.Let's arbitrarily assume there are 5 million active GarageBand users in the U. (I did try naively searching with Google, but couldn't find a number). Getting all those users to fork out $5 for the new version would bring Apple $25 million. At $100K per developer year ($80K developer salary, plus 25% overhead), that's 250 developer years—which would provide a lot of new features/bugfixes. Looking at the Top Paid on App Store, I see the game 'Batman Arkham City' selling for $4.99—and those developers have to pay an App Store commission.IMHO, JoelB, you need to work on your marketing-think.
Not intelligent-marketing-think; that may have departed from Apple along with SJ.Yes, color me cynical. It probably comes from 25 years of also dealing with Brand M.David H.
Let's arbitrarily assume there are 5 million active GarageBand users in the U. (I did try naively searching with Google, but couldn't find a number). Getting all those users to fork out $5 for the new version would bring Apple $25 million. At $100K per developer year ($80K developer salary, plus 25% overhead), that's 250 developer years—which would provide a lot of new features/bugfixes. Looking at the Top Paid on App Store, I see the game 'Batman Arkham City' selling for $4.99—and those developers have to pay an App Store commission.IMHO, JoelB, you need to work on your marketing-think. Not intelligent-marketing-think; that may have departed from Apple along with SJ.Yes, color me cynical.
It probably comes from 25 years of also dealing with Brand M.David H.Garageband 6 still works in Yosemite, and there's nothing forcing people to upgrade further. And Garageband 10 actually removes features such as podcasting. If you balk at paying $ 4.99 it's better to stay on Garageband 6.People come up with conspiracy theories because it feels better to think that there are problems caused by reasons, rather than just bugs that need fixing. Let's arbitrarily assume there are 5 million active GarageBand users in the U.
(I did try naively searching with Google, but couldn't find a number). Getting all those users to fork out $5 for the new version would bring Apple $25 million.
At $100K per developer year ($80K developer salary, plus 25% overhead), that's 250 developer years—which would provide a lot of new features/bugfixes. Looking at the Top Paid on App Store, I see the game 'Batman Arkham City' selling for $4.99—and those developers have to pay an App Store commission.IMHO, JoelB, you need to work on your marketing-think. Not intelligent-marketing-think; that may have departed from Apple along with SJ.Yes, color me cynical. It probably comes from 25 years of also dealing with Brand M.David H.Garageband 6 still works in Yosemite, and there's nothing forcing people to upgrade further. And Garageband 10 actually removes features such as podcasting. Further results:(1) Clicking on name of update at left of Updates window in App Store produces dialog with message 'The item you've requested is not currently available in the U.S.
As to that, look at my Tribus. Oh to be in England, now that Fall is here.(2) On my Mac Pro, App Store now reports a second update available, for iPhoto 9.6.1 (which I already installed on my Mac BookPro 9/4/2015).
Same results trying to update that.(3) I have now put this on Apple Bug Reporter as #22967682.David H.These are not bugs Apple will fix; they aren't bugs.Here is the process to get Garageband 6.0.5 and iPhoto 9.6.1 on your computer.First, open the App Store application and look in the Purchases section to confirm you see iPhoto and Garageband 6.0.5 in there after signing in. If you do not have either application listed in the Purchases section you will never be able to update iPhoto as it's now a discontinued product. If you don't have Garageband 6.0.5 there, then follow the link to the script in the post above mine to fix the expired certificate in the Garageband 6.0.5 updater and install that.Assuming you do have both iPhoto and Garageband 6.0.5 listed in the Purchases section of the App Store, delete both applications from your Applications folder. Then quit and reopen the App Store application and install both iPhoto and Garageband from the Purchases section. Given the age of the installer it's probably an expired certificate.Try using the script atThanks, JoelB.I tried that successfully, via the instructions for using the Python script posted in the comments below it. However, when I opened the.pkg in the.dmg generated by opening the 'flattened' (certificate-removed) version of the update, I got 'The version of GarageBand installed on this Mac must be updated through the Mac App Store.
Check the Mac App Store to see if an update is available.' I will now try the procedure suggested by chrisf in the post below yours, but before that I'll retry yours after 'deleting' my GarageBand.app.David H.P.S. That retry didn't work, because 'GarageBand 6.0 or later is required to install this update.' On to the App Store. Further results:(1) Clicking on name of update at left of Updates window in App Store produces dialog with message 'The item you've requested is not currently available in the U.S. As to that, look at my Tribus.
Oh to be in England, now that Fall is here.(2) On my Mac Pro, App Store now reports a second update available, for iPhoto 9.6.1 (which I already installed on my Mac BookPro 9/4/2015). Same results trying to update that.(3) I have now put this on Apple Bug Reporter as #22967682.David H.These are not bugs Apple will fix; they aren't bugs.Here is the process to get Garageband 6.0.5 and iPhoto 9.6.1 on your computer.First, open the App Store application and look in the Purchases section to confirm you see iPhoto and Garageband 6.0.5 in there after signing in. If you do not have either application listed in the Purchases section you will never be able to update iPhoto as it's now a discontinued product. If you don't have Garageband 6.0.5 there, then follow the link to the script in the post above mine to fix the expired certificate in the Garageband 6.0.5 updater and install that.Assuming you do have both iPhoto and Garageband 6.0.5 listed in the Purchases section of the App Store, delete both applications from your Applications folder. Then quit and reopen the App Store application and install both iPhoto and Garageband from the Purchases section.Thanks, chrisf.Your suggested process worked fine for getting iPhoto 9.6.1 on my Mac Pro computer (which I normally just use as my Retrospect 12.5 backup server; I already had iPhoto 9.6.1 on my MacBook Pro—my main work machine).
Since I had never had iPhoto in the Applications folder on my Mac Pro but had Purchased it for the MBP in December 2014, I simply had to click the button in App Store Purchases to download it onto the Mac Pro.(One interesting side-note is that App Store downloaded iPhoto 9.6.1 not into the normal Applications folder, but into /Documents/PhotosRestored/Media Set Red/Applications. This is a folder I restored from the MBP with Retrospect on 31 July, so that I could print a photo from DropBox on an inherited USB color printer cabled to the Mac Pro. When I found iPhoto.app 9.6.1 there today, I also found the iMovie.app I had Updated from the App Store earlier this month that had mysteriously never appeared in the normal Applications folder. So there's either a bug in Retrospect that subsequently confuses App Store.app, or a bug in App Store.app that is confused by a by a prior Retrospect Restore script; take your pick, Retrospect haters! I'll report the problem as a Retrospect bug on forums.retrospect.com.)As noted in my post above this one, the link in JoelB's post has not solved my problem in getting the Garageband 6.0.5 updater.
Your suggestion has not helped with that either, because App Store doesn't show that I ever purchased GarageBand. I now think that there may be a bug in either App Store.app or the App Store itself that is reporting an expired certificate for the updater as 'not currently available in the U.S. I now think that there may be a bug in either App Store.app or the App Store itself that is reporting an expired certificate for the updater as 'not currently available in the U.S.
The version of Garageband 6.0.5 in the App Store isn't affected by the expired developer certificate. Garageband 6 isn't available for purchase through the App Store any more. If it's not in your purchased list, you will never be able to update it.
This isn't a bug; Apple simply doesn't sell it any more and that's why you see the error. I now think that there may be a bug in either App Store.app or the App Store itself that is reporting an expired certificate for the updater as 'not currently available in the U.S. The version of Garageband 6.0.5 in the App Store isn't affected by the expired developer certificate. Garageband 6 isn't available for purchase through the App Store any more. If it's not in your purchased list, you will never be able to update it.
This isn't a bug; Apple simply doesn't sell it any more and that's why you see the error.Please read my OP. The updater for GarageBand 6.0.5 showed up in App Store.app on both my MacBook Pro and my Mac Pro around 30 September; it wasn't there before. Since GarageBand never was in my Purchased list (it almost certainly downloaded as part of OS X 10.10.2 or 10.10.3), isn't the appearance of the updater a bug in itself? The bug may be a mis-configuration of App Store, possibly a by-product of preparations for OS X 10.11 as I have speculated above, but it is surely a bug.
And it also happened to Carhole (see the link in the second post in the thread; he/she succeeded in downloading the updater by booting into OS X 10.11) and LtKernelPanic and adriviola.David H. Since GarageBand never was in my Purchased list (it almost certainly downloaded as part of OS X 10.10.2 or 10.10.3), isn't the appearance of the updater a bug in itself?Garageband is included with Macs. If you are using a used Mac, that copy will have been assigned to the original owner's App Store account, not yours, and there's now no way to get version 10 free anymore.Whether or not we regard the current behavior as a bug, Apple isn't going to fix it because the program is discontinued. If you want to use a current version of Garageband, you'll need to buy it.I believe you have misread what the other posters have said.If you had assigned your free copy of Garageband 6 to your App Store account before it became unavailable, you'd be able to upgrade to version 10 for free.
Because you have not done so, you can't upgrade to 10 for free. If you bought your Mac new, you may be able to call Apple and get them to give you a copy. I never purchased Garageband 10 either, but it's available to me in my purchases (as is 6.0.5.)Of course if you have no intention of actually using Garageband, just delete the copy you have and be done with it.
I've never used it, personally. Since GarageBand never was in my Purchased list (it almost certainly downloaded as part of OS X 10.10.2 or 10.10.3), isn't the appearance of the updater a bug in itself?Garageband is included with Macs. If you are using a used Mac, that copy will have been assigned to the original owner's App Store account, not yours, and there's now no way to get version 10 free anymore.Whether or not we regard the current behavior as a bug, Apple isn't going to fix it because the program is discontinued. If you want to use a current version of Garageband, you'll need to buy it.I believe you have misread what the other posters have said.If you had assigned your free copy of Garageband 6 to your App Store account before it became unavailable, you'd be able to upgrade to version 10 for free. Because you have not done so, you can't upgrade to 10 for free. If you bought your Mac new, you may be able to call Apple and get them to give you a copy.
I never purchased Garageband 10 either, but it's available to me in my purchases (as is 6.0.5.)Of course if you have no intention of actually using Garageband, just delete the copy you have and be done with it. I've never used it, personally.I have now solved the problem completely for my MacBook Pro, and partially for my Mac Pro.The first thing I did was to phone Apple Support. I spent an hour on the phone, mostly on hold, while an advisor named Nathan (per the 'we'd love to hear about your experience contacting AppleCare Telephone Support' e-mail) contacted three different Apple departments to try to 'assign your free copy of Garageband 6 to your App Store account'. No can do.As I told Nathan, GarageBand 10 may someday be a great app, but right now I'd rather have an up-to-date copy of GarageBand 6. He suggested that I buy (for free) from the App Store a copy of The Unarchiver, and try to hack the stand-alone GarageBand 6.0.5 updater to make 'The version of GarageBand installed on this Mac must be updated through the Mac App Store.' Error non-fatal.
However the only human-readable file I unarchived was Localizable Strings for the English.lproj, and I lack the developer tools or time to hack into a presumed script file in non-human-readable distributed form. I did download the tool Packages, but one look at that convinced me I wouldn't be able to build my own copy of the updater.So I tried another tack. From JoelB's link in post (thanks, JoelB) I had found out about the Python script flatpkgfixer.py, so I had downloaded that and followed the instructions below to run it in Terminal. This gave me a version of GarageBand6.0.5Update.dmg that was 'flattened' to remove the certificate, but I had found out per post that I needed a non-App-Store-designated version of GarageBand to run the update on.And then I realized I have one. It's time for a bit of full disclosure, so readers who object to my 'over-sharing' may choose to simply accept that I have a non-App-Store-designated PowerPC version of GarageBand on another drive I have called 'Ronny's Macintosh HD', and may choose to skip to the next paragraph.
I inherited my Mac Pro from my long-time guitar teacher (I wrote the Wikipedia article; if you want to get an idea of typical frustrations of a novice Wikipedia contributor, click the associated Talk tab at the top left of the article). The Wikipedia article can't say so because there are no 'reliable sources' per WP standards, but Ronny—despite having macular degeneration—continued to work on audio documents related to his work until he died at age 88—using software installed for him by another former student I'll call M. Took home two hard drives containing the audio documents, but I inherited Ronny's Mac Pro with the boot drive—which contains a lot of software including GarageBand 6.0.5. Ronny's copy of GarageBand is for PowerPC; he was a long-time Mac user, and M. Copied over everything onto the Mac Pro that Ronny got from the N.Y. State Commission for the Blind in 2011—which boots OS X 10.6.8 and hence can still run PowerPC apps. I have left Ronny's Macintosh HD drive essentially untouched, and installed a (second-drive) Macintosh HD New to boot OS X 10.10 on the Mac Pro for my own use.I moved my MBP copy of GarageBand.app 6.0.4 to the Trash, then copied the Garage.Band.app from Ronny's Macintosh HD over to my MBP Applications folder (I did so using the DropBox that M.
Had set up in 2013 for communication between Ronny and him). Finally I ran the.pkg from the 'flattened' GarageBand6.0.5Update.dmg, and that—even though it was updating a PowerPC app under OS X 10.10.5—gave me an apparently fully-operational GarageBand 6.0.5 on the MBP.
The Updates notice for GarageBand disappeared from App Store.app on the MBP.Next I tried to do the same thing on the Mac Pro's Macintosh HD New, omitting moving any copy of GarageBand.app from Applications to Trash because GarageBand had never been installed on Macintosh HD New. (After it took two hours to copy the 'flattened' GarageBand6.0.5Update.dmg from the MBP to the Mac Pro using DropBox, I resolved to do all such copying in future on a USB thumb drive via 'sneakernet' (oh, the shame!
).) When I tried to open GarageBand.app on the Mac Pro's Macintosh HD New-Applications, it said it would not execute unless I gave it a location for finding certain files. I eventually copied both Library-Audio and Library-ApplicationSupport-GarageBand from the MBP. GarageBand.app will now open from the Mac Pro's Macintosh HD New-Applications, but there is a blank screen instead of an initial dialog; the Updates notice for GarageBand did not disappear from App Store.app on the Mac Pro's Macintosh HD New. One possibility is that there are certain files not labeled '.GarageBand.' In other folders that need to be copied; when I start it, GarageBand.app from the Mac Pro's Macintosh HD New-Applications puts up a brief dialog about 'Initializing Jam Packer.'
Since I will almost certainly never be running GarageBand from the Mac Pro's Macintosh HD New-Applications folder, do I really care? Can I live with the Updates notice for GarageBand still remaining in App Store.app on the Mac Pro's Macintosh HD New? Does anybody have a suggestion as to how to make GarageBand run correctly from the Mac Pro's Macintosh HD New-Applications folder?BTW, Apple's recent response to this whole situation has been to replace the App Store message 'This item is temporarily unavailable. Try again later.'
With 'The version of GarageBand installed on this Mac must be updated through the Mac App Store.' That message makes it crystal clear that this problem is in fact caused by an Apple Marketing decision.David H.P.S.: Credited JoelB for link to flatpkgfixer.py. Minor time-line-clarifying edits.P.P.S: I discovered I did save the the new version of the App Store message in one of my posts, so have replaced it here. BTW, Apple's recent response to this whole situation has been to replace the App Store message 'This item is temporarily unavailable.
Try again later.' With a somewhat-clearer message, which I cannot remember and which I no longer see on either my MBP or my Mac Pro. That message IIRC says that the listed update cannot be applied from App Store because the application was not Purchased, and thus makes it crystal clear that this problem is in fact caused by an Apple Marketing decision.David H.P.S.: Credited JoelB for link to flatpkgfixer.py. Minor time-line-clarifying edits.LOL. Thats because you have been messing around introducing applications from other sources rather than evidence of your grand conspiracy to part you with $ 4.99. If you do that with any app you will get the same message, even apps that are currently supported.Garageband 6 has been EOL'd by Apple.
It's unlikely ever to have any fixes to bugs whether they are in the App or problems with the App store.You have certainly spent a lot more time than I would on an App that you never use anyway. Why not just delete it completely.?
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |