Garageband - OSStatus Error -36

Hello,

Recently i have had said error (OSStatus error -36) appear when trying to open a GarageBand project.
If i open it through GarageBand the error code pops up and the program freezes and i have to force quit. If i open the project up through the finder the error code appears but then i can continue as normal. At first it was only happening on 3 files. today i noticed it has started happening with others.

I had a very long phone conversation with a chap from the apple customer care and he went through fixes with him whilst he watched me do them, but to no avail. So i thought i would try my luck on here.

Has anyone had the same problems and/or know of a fix?

Any help would be greatly appreciated

Thanks!

Can you provide complete details for your model and year Mac, macOS, GarageBand version, and any components used with Mac or GarageBand?

Also, have you run, or done, any maintenance/security/cleaning apps on your Mac recently?

Recently i have had said error (OSStatus error -36) appear when trying to open a GarageBand project.

Click to expand...

You could take a look here and see if any of the results make any sense to you.

They sure doesn't to me but I'm sure not a programmer, except it appears to be some sort of error — no kidding!!!

https://www.osstatus.com/search/results?platform=all&framework=all&search=-36






- Patrick
======

Error 36 is related to i/o errors; and that usually means hard drive problems. Suggest you run First Aid on your hard drive . Also, when you post a problem for assistance, you should give us the particulars about your hardware and which version of macOS you're running.

ferrarr said:

Can you provide complete details for your model and year Mac, macOS, GarageBand version, and any components used with Mac or GarageBand?

Also, have you run, or done, any maintenance/security/cleaning apps on your Mac recently?

Click to expand...

Sorry for not adding the details.

I have MacBook Air 13 inch, Os Sierra, GarageBand v10.

I've ran first aid but didn't find any problems. I did have Dr Clean but have since removed it.

Hope that helps.

Do the non-working file projects work properly if you do get them opened and then Save them??

Have you tried making a copy and setup a new user on your Mac and then try working on them?

Does a new project work properly?

And what about trying to open and work on the existing file projects when booted up using Safe Boot Mode??





- Patrick
======

pm-r said:

Do the non-working file projects work properly if you do get them opened and then Save them??

Have you tried making a copy and setup a new user on your Mac and then try working on them?

Does a new project work properly?

And what about trying to open and work on the existing file projects when booted up using Safe Boot Mode??





- Patrick
======

Click to expand...

I've tried opening and saving them and opening in safe mode those didn't work.

The new projects I've had did open as normal but I noticed a couple of days ago that the errors started appearing

I haven't tried making a new user yet I'll give that a bash next.

The new projects I've had did open as normal but I noticed a couple of days ago that the errors started appearing

Click to expand...

I'd tend to agree with and as chscag suggested — possible hard drive problems.

But give a new user a try anyway… one never knows until one tries…




- Patrick
======

Tried the new user idea, same result. Thanks for your replies any way, ill look into getting a new drive if i must then.

JWD1981 said:

Tried the new user idea, same result. Thanks for your replies any way, ill look into getting a new drive if i must then.

Click to expand...

Do you already have an external bootable drive you could boot from and use to test??

Like your existing backup drive as an example. Using that could prove if your internal drive is failing or just goofy.




- Patrick
======