2 months is not bad there’s an issue I reported 2 years ago that is still not fixed.
What I found out: after adding a new album, wait for roon to finish the scan. If there are tracks missing, change the name of the folder of the album (change to uppercase or whatever). This forses a rescan by roon and on my system the missing tracks appear, same result as restarting the server)
How about, turning off the watched folder using disable, make your copy, after copy is done, enable the watch folder again.
This way Roon only “sees” the finished copy.
** see post 14 (ish) 
1 Like
I had a very similar problem some years ago. Roon only showed the first track or two from CD rips I just transferred to the Watched folder. The missing tracks just didn’t show up anywhere at all (no i/o errors, no skipped tracks mentioned). Performing a manual rescan didn’t help.
I discovered if I moved the problem album folder from one location within the Watched folder to a different location, also within the Watched folder, Roon would pick up all the missing tracks. So going forward I created a “temp” folder within the Watched folder. When I ripped a CD, I first transferred it to the temp folder (as expected Roon would only pick up the first couple tracks), then moved it to it’s normal location (Roon then picked up all the missing tracks).
This issue lasted without resolution for quite some time (a year or more?). Finally at some point (don’t exactly remember when), the problem went away, so I didn’t have to use the work around described above any longer.
This current issue really feels like a reoccurrence of the issue I had before, except for the error message being displayed this time.
Roon seriously needs to fix this asap.
Maybe. It could be a recurrence of the same symptoms with a different cause, but the same workarounds remain effective…
Maybe counterintuitively, I think the ‘solution’ might be for Roon to not try to process new files immediately, until it’s sure the copy is complete. I doubt it’s that easy. There are plenty of examples of ‘stuff’ that sounds easy - until you try to code it…
1 Like
Just a thought - if you create a ‘transfer’ folder outside the watched folder, but on the same drive, a ‘move’ into the watched folder might also work.
Just wanted to add a +1 that this has never happened to me before, and in the last month there have been tracks missing from every album I import. Restarting the core works to restore the tracks, but is a massive PITA.
I don’t remember if I tried that before or not; it’s been a few years since I was experiencing that issue. It’s certainly worth a try for anyone experiencing this issue.
I’ve ripped a couple CDs since the current issue popped up, but they were picked up fine by Roon, no missing tracks or error messages, when I transferred them to the Watched folder.
1 Like
For my part it is a roon problem concerning the I/O errors because when I use the previous version Roon 2.044, I no longer have this problem.
Temporarily disabling the storage location before copying in the files works and is a little simpler than have to stop the server.
As Andy mentioned, there are different solutions. Stopping server, diabling watch folder, renaming folder, moving folder to a temp location.
For me closing and restarting server is easiest, Roon runs on a Windows NUC, and it’s simply right clicking taskbar icon, closing, and then double click desktop icon.
My point is that we should not have to do this stuff. I get it that new code may introduce issues, but we have been waiting for a fix for this basic functionality for more than two months now, It worked flawlessly before, so make it work again before adding all sorts of other added things.
2 Likes
It’s “The Roon Dance™”. 
This happened to me before and renaming the album folder would cause Roon to re-scan and pickup and album.
Recently I have moved Roon Core to a different Windows 11 machine. It was previously running on my QNAP NAS. Now it happens with every album I copy to the watched folder. Very annoying. This is clearly a Roon problem where Roon tries to scan the file before it was fully copied to the storage location.
1 Like
Hello All,
It has been some time since our last communication regarding this issue, so I wanted to touch base with an update. Our development team has been actively working on this, and the ticket has made significant progress recently.
We’re aiming to include the necessary changes in an upcoming release in the near future after these changes pass QA testing. While we can’t provide an exact timeline, we’ll keep you updated as soon as we have more details.
Thanks again for your patience as we work on improving this behavior!
5 Likes
Wish I read this thread earlier
Don’t know if it helps but I had this error today and discovered that if I add the tracks one at a time there is no problem but when I moved multiple tracks into my ROON library only the first was copied correctly and the rest had i/o failure errors.
Definitely not fixed in the EA 1515 release.
1 Like
Hi @noris Do we have any updates? Would be great to get this fixed its quite bothersome having to take this many steps just to add a new album to your library 