For two days I tried everything I could to get the drag and drop to start working again in Yosemite on my MacBook Pro Retina. I even re-installed the OS via Disk Recovery. I wound up at the Apple Store where they couldn’t find the bug either, but we did the following and I am back up and running. There is a bit of a downside, so please read all the way through.
I have no idea if this will help you, but if you log in under a GUEST account and this drag and drop issue is NOT there - then try this. For whatever reason this bug was localized to just my single user settings Library. The GUEST account could drag and drop fine. Weird. Anyway, here’s what we did at the Apple Store that has kept me up and running….
- Create a new user
- Logout (deactivates the busted user library) and then login as that new user.
- Enable Root User (superuser) while logged in under this new user. YouTube has some 1min. videos on how to do this.
- Navigate to the Library (which is usually invisible) listed under your original admin user account.
- Rename this folder. I just added ORIGINAL to it.
- Also, create an alias for this folder and leave it there.
- Go turn off Root User and log out.
- Now, when you log back in under your usual User Acct. the system can’t find the Library system folder (because you renamed it) so it creates a fresh one. This new Library folder will still be invisible to you, but should work.
This fixed my drag and drop problem.
What this does though is kill all of your plists, saved website passwords, bookmarks, application settings, etc. for everything. I mean everything. Which kind of stinks.
This is why we created the alias in Step 05, click on it and you can open your ORIGINAL Library folder and drag out the files as you need them. I guess one day I'll drag over the one setting that borked my machine, but I haven't found it yet.
This is certainly not ideal and may not even be the best solution. But it got me up and running with no loss of files, just slows me down as I have to re-populate all my log-ins, etc.
Hopefully someone will come up with a better fix or patch.
Hope this helps.