Duplicate endpoints cluttering Settings > Audio on PC (ref#K2H0F4)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· How do I clean up hundreds of duplicate endpoints?
Something went nuts and my Kef LSX II LT on my PC is showing up hundreds of times in Settings > Audio > Other network devices. How do I clean this up?

Tell us about your home network

· This isn't a network issue

Hello @Stan_Eisenberg

Thank you for reaching Roon support.

Can you try clearing your endpoint cache? You can do so using the following steps:

Note: Deleting these files will

  • Log you out of Tidal/Qobuz
  • Delete your endpoint names.
  • Delete saved DSP configs.

If this doesn’t help, please restore the backup you made before trying these steps.

Uh oh. So I deleted the contents of the Core folder (after making a copy) and Roon stopped working. It would start but my PC would forever be trying to connect. I waited over half an hour. Restored the contents.

Then I told it to restore from a backup from 1/5 which is before those endpoints were added. After the restore, it relaunched the server and now everything is completely hosed.

The roon server process won’t start up properly and I’m now Roon is completely dead in the water.

OK, I’m back in business.

So I noticed that Roon created a .restore_on_launch folder in the root RoonServer folder. I guessed that these were probably the files that were to be restored. For whatever reason, Roon wasn’t copying them over and the process was just cycling on and off. So I manually made a copy of the root RoonServer folder in case I needed to restore it, deleted the Database and Settings folders and moved over the ones from the .restore_on_launch folder.

Restarted Roon and that successfully took me back to before I added the LSX II endpoint - and now when I go to audio, I only see one LSX II endpoint in there as intended.

Thanks for pointing me in the right direction. Was a bumpier ride than expected, but we got where we needed to be in the end.

Phew! All good now.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.