File-Based Discovery deduplicates text files with same name and size across different folders due to nil version in hash<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue File-Based Discovery creates only one Unidentified File Set record for text files with the same name and size located in different folders. This occurs because the deduplication hash does not include the file path, and text files always have a nil version. Symptoms Two text files with the same name and size in different directories result in only one Unidentified File Set recordFile path is not considered in deduplicationCustomer expects separate records for files in different locationsNo errors logged — deduplication is silent Cause The FBD deduplication logic computes a SHA256 hash using: file_name + '.' + file_version (if not nil) + '.' + file_size. A business rule prevents insertion of records with matching hashes. File path is intentionally excluded from the hash per PRB1613464. For text files (.txt), the VersionResolver cannot extract version information because it relies exclusively on Windows PE VERSIONINFO metadata embedded in binary files (.exe, .dll). With path excluded and version absent, two text files sharing the same name and size produce identical hashes and are treated as the same file. This is working as designed. Resolution This is working as designed. File path exclusion from the hash was a deliberate fix under PRB1613464.FBD can differentiate versions for .exe and .dll files because they carry embedded VERSIONINFO metadata.FBD cannot look at the contents inside a file to determine the version, nor can it use the file path as a determining factor.For use cases requiring file version tracking across locations for auditing purposes, consider using Event Management instead of Discovery.See also KB2977718 for the full FBD deduplication chain documentation.