A filename list reports notes.docx twice. One copy is in Notes and the other is in Archive. Add each path relative to the project root so the list remains meaningful when the project is moved.

Example project root. The filename alone is ambiguous.
Build the list, then export it
Set the project root and choose a new CSV path outside it. The command gathers the recursive results before writing the file, and -NoClobber protects an existing CSV of the same name.
$root = (Get-Item -LiteralPath 'C:\Work\Workshop').FullName
$prefix = $root.TrimEnd('\') + '\'
$items = @(Get-ChildItem -LiteralPath $root -File -Recurse -ErrorAction Stop)
$items | ForEach-Object {
[pscustomobject]@{
RelativePath = $_.FullName.Substring($prefix.Length)
Bytes = $_.Length
}
} | Export-Csv -LiteralPath 'C:\Work\workshop-inventory.csv' -NoTypeInformation -NoClobber -Encoding UTF8Verify the duplicate names are distinct rows
Open the CSV and find Notes\notes.docx and Archive\notes.docx. Confirm the relative paths do not begin with a drive letter and that Bytes is separate from the path. Check one size against the source file’s properties. This is a normal recursive listing, so assess separately whether hidden files belong in your inventory.

Example export. Open the CSV and verify that both paths and their sizes survived.
Reference Microsoft’s Export-Csv reference.



