Identify what is duplicated
Choose one affected title and inspect whether the entries refer to the same physical file, different editions or different source routes. Keep the year and edition in the note. Two posters that look alike can still represent different media versions or server libraries.
An illustrative setup might expose a NAS folder directly and also expose that collection through a media server. This could make two routes worth checking before removing anything. The example does not establish that every Infuse installation combines those routes in the same way.
Inspect the current library configuration
Consult the installed release’s library controls and Firecore’s current documentation. Compare selected sources with the intended organisation. The historical support case points to duplicate server entries, while release notes can identify changes relevant to newer builds. Record the actual Infuse version.
Make a reversible configuration adjustment to one confirmed redundant source rather than deleting underlying files. Keep the working connection information privately so it can be restored. Do not remove somebody else’s server access or change shared NAS folders without the appropriate authority.
Verify more than one poster
After the supported adjustment, check the chosen title and another unaffected item. Confirm that playback still uses the intended source and that a legitimate alternate edition has not disappeared accidentally. Catalogue neatness should not come at the expense of lost media or access. Keep the previous source selection in your private notes.
If the duplication persists, provide Firecore with the app release, source types and a redacted example. State whether it concerns server entries, library cards or physical files. This preserves the difference between a dated suggested cause and the actual evidence in the reader’s current installation.