· Other – My issue isn’t listed above
metadata improver: paused - NEVER had this issue till recent (no changes to my system)
Netgear OrbiRBE971 (router + wireless)-Netgear dumb switches - ROCK server (intel) standalone - Purchased patch cables (nice ones and yes swithed em out) - ATT Fiber to router.
Hey @Matthew_Griffith,
Thanks for writing in and for sharing your report!
Before anything else, have you safely stopped Roon Server from running, and then rebooted both your ROCK and primary router? Let me know if this helps.
If it doesn’t, it may be worth testing out a different DNS server - here’s a step-by-step on how to change the DNS settings on your ROCK:
Open a web browser on a device connected to the same network as your ROCK.
http://rock.local/ (on macOS or Windows with Bonjour installed).8.8.8.8 and 8.8.4.41.1.1.1 and 1.0.0.1208.67.222.222 and 208.67.220.220Restart the ROCK(make sure Roon Server is stopped) and let me know if you continue to experience the paused metadata improver. Thank you! 
Have you tried changing the DNS server assigned in the Orbi router settings? Usually this is in the settings admin page under Advanced Setup → DNS. Try Google (8.8.8.8) or Cloudflare (1.1.1.1), similar to the instructions above.
Let us know if this helps. Thanks!
This thread will autoclose eventually without a response from the OP. Please let us know at your convenience whether the DNS change suggested above had any effect. We’ll keep an eye out for your response. Thanks!
Unfortunately did not work 
I changed the DNS on the Orbi to 8.8.8.8 and matched that on ROCK w static IP and 8.8.8.8
Still shows paused and cannot communicate.
Weird thing is i have NOT changed my network configuration NOR changed my computer configuration in the last 8 months, and until recently (as in 3 weeks ago) this has never once happened to me. VERY baffling. My next step is to shut down my entire system from end to end (and there are about 20 parts) and start one by one booting up the fiber interface, then my 3x mesh system (ROCK is hardwired btw), then the 6 routers, then the NAS, then the ROCK then the computer, then ROON software and see where that goes. Will take me about 2 hours to do all that. I will try this weekend and see what happens.
I am stymied as to what’s going on.
Since you are the experts, can this be caused by some DB corruption? Amount of files limitation? Not sure what’s buried in your software.
In the meantime, if you have any other ideas, please let me know.
Kind regards, Matt
Hello @Matthew_Griffith,
Would you kindly perform a hardware restart by unplugging and then plugging back in the power of your ROCK device? Please let us know how it goes afterward.
The latest diagnostics show analysis failing on about 100 different tracks on 9/25. This is happening with local content across an SMB share, within a set of watched folders that all seem to contain the same nomenclature _Not-iTunes .
This doesn’t directly mean that tracks or database content have become corrupted. I’d first navigate to Roon Settings → Library and select “Clean Up Library” before re-scanning your watched folder locations within Roon.
There are some additional generic network errors reported when RoonServer connects to Roon’s own cloud services. We don’t have any confirmed instances of these failures since you changed the DNS service on 9/19 per your post above.
This suggests you might have had two problems - DNS and some dangling track associations/incomplete metadata headers with library tracks. The former is resolved - a library cleanup might help with the latter.
We’ll watch for your response. Thanks!
Glad to hear one problem solved. On to the second. How can I see a list of all those songs so I can manually fix this issue. The annoying part is the upper right spinning circle will NOT stop and its annying as heck. Always feels “off” and that something is broken…
Thanks for the help
You can typically review the “Skipped Files” option within your Roon Settings>Library page.
That said, you’re best bet would be to analyze the health of your files using a dedicated app meant to do so, like dbpoweramp. It can also fix any potentially corrupt files.
This means Roon is still analyzing your library - fixing your problematic files will likely solve this issue as well. 
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
This thread will shortly close due to inactivity. Please reach out if you have any further questions in the meantime. Thanks!
· Other
· None of the above
· Other
Still trying to fix metadata improver: paused
Same as before - no changes
Update since 19 days ago… I went into all my skipped files and fixed all the errors on unreadable files and such. Quick Q as well… So it is skipping some DFF files, and cannot read some jpeg files (even though I cna open them fine and even reformatted some of them ) I moved all the offending files outside of Roon view and STILL get the metadata imporver paused
Just so yo know after a total reboot of EVERYTHING, the adding muic to librabry part goes fine. Scanning and IDing seems to go fine and at some point (never consistent) BAM… metadata improver paused (cannot communincate) - Nothing is wiereless, I can see if my interent drops (It has not since reboot yet still says same)
Maybe a different approach is what EXACTLY is the improver looking for? maybe a pathway to connect? (Ip address I can check), what is it doing to “improve” the file? Is there a way to turn it off so that VERY ANNOYING spinning wheel stops? For someone with OCD this literally drives me NUTS. Everything else works excep this improver. Any way to get a list of the files its trying to improve and I can go down that rabbit hole? Thanks for your dillegence in helping solve this annoying issue.
Kind regards,
Matt
Hello @Matthew_Griffith ,
We are performing a review of older threads and saw this one remained unanswered, apologies. It has been some time since we last heard from you, are you still seeing this issue presently? If so, please let us know and we can take another look, thank you!
We’re going to auto-close this thread due to inactivity at this time, but you can reactivate it by submitting a new tech support request here. Our team will promptly reopen the case and respond. Thank you!