iTunes 12.5.3 update broke my iCloud Music Library (I think)

[PaulDoFish]

Hi all,

I just loaded some new music into my iTunes library today. Now, every time I try to update my iCloud Music Library, my iTunes crashes and I get a "Quit Unexpectedly" error message in MacOS.

This worked fine for me last week... The only difference in my environment is that I received iTunes update 12.5.3 yesterday, and I think that broke this functionality... Is anyone else experiencing this?

 

[royaltaste]

Hi,

I suffer under this issue since the 12.5.3 update, too. As soon as i try to match new mp3 iTunes quits unexpectedly. Have a look at the Apple iTunes Match Discussion. Some people are experiencing the same. They suggest downgrading to 12.5.2 via Time Machine Backup/an alternative method described over there.

 

[petsounds]

I installed 12.5.3 yesterday, and now the App Store is giving me an update for 12.5.3 again. Maybe they screwed up the release?

 

[tywebb13]

I installed 12.5.3 yesterday, and now the App Store is giving me an update for 12.5.3 again. Maybe they screwed up the release?

It's a different build.

The previous one was 12.5.3.16, and the new one is 12.5.3.17.

 

[DCIFRTHS]

I installed 12.5.3 yesterday, and now the App Store is giving me an update for 12.5.3 again. Maybe they screwed up the release?

I'm so glad you posted this! I was searching the forums for an answer because I had the same thing happen to me on macOS 10.11.6.
It kind of freaked me out. I installed it, and afterward I thought maybe I had malware that looked like the app store, and I just installed something nefarious

Maybe someone can check the exact version before they update iTunes? I think mine was at 12.5.3.16 BEFORE updating the to the "second" version of 12.5.3.x. After the second update, I'm at 12.5.3.17. It would be great if someone could verify for me though.

Thanks!

 

[tywebb13]

Maybe someone can check the exact version before they update iTunes? I think mine was at 12.5.3.16 BEFORE updating the to the "second" version of 12.5.3.x. After the second update, I'm at 12.5.3.17. It would be great if someone could verify for me though.

If you read the post prior to yours you will see that this has already been done.

 

[DCIFRTHS]

If you read the post prior to yours you will see that this has already been done.

oops. Can't believe I missed that.

Thanks!

 

[royaltaste]

12.5.3.17 seems to do the job for me.

 

[petsounds]

It's a different build.

The previous one was 12.5.3.16, and the new one is 12.5.3.17.

Then they should probably print the sub-version on the update page, as it looked like the same build. And you know, maybe update the release notes.