Apple Music on my PC stopped opening yesterday, with a “Could not open library” message and Error Code -50. Restarting the app didn’t help. I traced the problem to Windows Security’s Controlled folder access, which was blocking the library process, AMPLibraryAgent.exe. Allowing that executable through restored the app. Here’s how I identified the block and changed the permission.
Analyzing Apple Music Error Code -50: Controlled Folder Access
The message read, “An error occurred and the library could not be opened. Error code: -50,” with only an exit button. Rebooting initially helped, but the error returned when I reopened the app. That made it clear I needed to look beyond a one-off crash.
I compared what Windows Task Manager showed with the processes and notifications in the system tray. Windows Security was recording repeated attempts by a particular file to access a protected location. Following those records led me to AMPLibraryAgent.exe, giving me a concrete process to investigate rather than just another unexplained error in the music app.
In the Windows Security app’s Protection history, the category was Controlled folder access. The library agent had tried to reach C:\Music and was stopped by Defender’s ransomware protection. That connection between the process, the folder, and the protection record was what identified the block in my case.
The library agent handles local audio files, the playlist database, and cached album artwork. Those are all parts of the music library rather than unrelated background activity. Without read and write access to the folder, the app appears to stop because it can’t maintain that data consistently. That explanation is my interpretation of the failure, not a confirmed diagnosis from the developer. I also suspect a recent Windows security update temporarily affected trust in the process signature, but the protection record establishes the block itself more clearly than its underlying cause.
How to Allow Apple Music Through Windows Ransomware Protection
The next step is to allow the library agent through Windows’ folder protection. These settings grant the access it needs.
1. Open Windows Security: Click the search icon on the Windows taskbar, type “Windows Security,” and launch the app.
2. Virus & threat protection: Click on the shield icon labeled “Virus & threat protection” in the left menu.
3. Manage ransomware protection: Scroll down to the bottom of the screen and click “Manage ransomware protection.”
4. Access allowed apps: Click “Allow an app through Controlled folder access.” Select “Yes” if a User Account Control (UAC) prompt appears.
5. Add allowed apps: Click the [+ Add an allowed app] button in the center of the screen.
6. Select recently blocked apps: Choose “Recently blocked apps” from the dropdown menu.
※ This is much faster and more accurate than manually digging through the hidden WindowsApps folder.
7. Add the process: Locate AMPLibraryAgent.exe at the top of the blocked list and add it.
8. Restart Apple Music.
Conclusion
Once the agent was allowed and I restarted the app, the library loaded without the error prompt. The audio database opened, the albums appeared as they should, and playback worked again. That was the practical confirmation I wanted after following the protection-history trail.
It’s natural to blame an app when something you use every day suddenly fails. For recurring permission problems, though, Windows Defender’s protection history is worth checking as well.
I’m keeping this record for my future self, and for anyone else trying to work out a similar Windows permission block.
