· Core Machine/Server: Totaldac internal player/server (storage path: \\192.168.1.200\music-nas)Control Devices: Windows PC / 13-inch iPad Air M4Roon Version: Active build (with recent app layout scaling changes)Issue Summary:A local WAV/FLAC album (Red Clay Road by Will Harrison) was recently deleted using Roon’s built-in "Delete Album" command. Following this deletion, the Roon core database appears to be permanently blocking the re-import of these specific files into the designated local player storage path: \\192.168.1.200\music-nas > Roon Imports > JOE.When attempting to re-import the files, the Roon PC drag-and-drop tool loops indefinitely or hangs on a spinning processing icon, refusing to advance the track database count past 7,699 tracks.Crucially, the exact same issue is now happening with a brand-new, freshly downloaded purchase (Wish You Were Here by Pink Floyd). This new album has a completely clean history and has never been deleted from Roon. Yet, when dragged into Roon, it triggers the identical loop, fails to index into the database, and cannot be added to the JOE folder profile.Furthermore, attempting a manual folder transfer via Windows File Explorer results in an "Access Denied" permission error on the target network directory for both folders, even though the storage path is correctly mapped and authenticated. The files are currently only accessible locally via an unstable workaround using the root directory and the Roon "Versions" option. I need assistance clearing the database locks and resetting the folder import permissions so new local 24-bit purchases can index seamlessly into the JOE storage profile.
Thanks for the detail, and for testing with a second album. That test is more useful than you might realise, and it points somewhere different from where you have landed.
It helps to know how the two pieces relate. Roon’s database and your music files are separate things. The database holds metadata, your edits, play history, playlists and settings, along with a reference to where each file lives. It does not contain the music itself, and it has no ownership of the folders the music sits in. That is also why there is nothing in it that could refuse a file. When you deleted that album, Roon removed its entries and the files, but it keeps no record that would block the same music being added again later. There are no database locks to clear.
Your own second test shows this. If a leftover lock from the deleted album were the cause, “Wish You Were Here” would have imported normally, since it has never been in Roon before. It did not. So the two albums have something in common, and the most likely candidate is the one you mention near the end: Windows Explorer refusing to write to \192.168.1.200\music-nas with Access Denied.
Roon cannot lock a folder on your NAS or change its permissions. What it does when you import is copy the files to that destination, so if the destination will not accept writes the import cannot finish.
Two things, please:
When the import hangs, does Roon show any message alongside the spinner, such as “Destination folder is read only” or “Destination folder unavailable”? Please tell us the exact wording if so.
Please try creating a new folder inside \192.168.1.200\music-nas\Roon Imports\JOE directly in Windows Explorer. If that also fails with Access Denied, the share’s permissions need fixing on the NAS before Roon can import anything there.
Once writing to that folder works from Windows, please try the import again and let us know how it goes.
Thank you for the clear explanation regarding the database and file separation. Your assessment is completely correct.
To answer your two questions:
When the import hangs, the spinning wheel displays absolutely no text or context alongside it—it simply spins indefinitely.
I just performed a full sequential network power cycle and attempted to create a new folder directly inside \\192.168.1.200\music-nas\Roon Imports\JOE via Windows Explorer. It immediately failed with a hard Windows error: “Destination Folder Access Denied. You need permission to perform this action.”
The issue is definitively a network share permissions block on the NAS folder itself. I have sent these exact findings to Vincent Brient at Totaldac so he can reset the folder permissions or provide the necessary administrative write credentials. I will keep this ticket open and update you as soon as the NAS share is unlocked.
Thank you for running that test and for the exact wording of the error. That settles it.
“Destination Folder Access Denied. You need permission to perform this action.” from Windows Explorer, with no Roon involved at all, means the share itself will not accept writes. Nothing on the Roon side can work around that, so contacting Vincent at Totaldac is the right move.
Once the permissions are sorted, please try the import again and let us know how it goes. If it still hangs after you can create a folder in that location from Windows Explorer, please come back to us, because at that point we would be looking at something different.
Reaching out to see where things stand on this. Were you able to get the share permissions sorted with Totaldac and try the import again from a folder that Windows Explorer can create in? If it is still hanging after that, let us know what you are seeing and we can take another look.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
