A file named Invoice [final].pdf can be a valid Windows filename while square brackets also have meaning in PowerShell wildcard patterns. Quoting the name keeps it together as an argument, but a cmdlet's Path parameter can still interpret that argument as a pattern.

Begin with the exact file visible in File Explorer. Confirm its folder and complete filename, including the extension. Do not rename it just to make an uncertain command stop complaining.

Test the exact item without changing it

In PowerShell on Windows, use Get-Item with LiteralPath for an exact filename. Replace the illustrative folder and name with your real path:

Get-Item -LiteralPath 'C:\Work\Invoice [final].pdf' |
    Select-Object -Property Name, FullName, Length

Microsoft documents LiteralPath as using the supplied location without interpreting characters as wildcards. Its separate Path parameter permits wildcard characters. The distinction belongs to the cmdlet as well as the shell's quoting rules.

Read the returned full path and filename. The Length value is another identity clue for a file, but matching a size alone would not prove that two files have identical content.

If the command still fails, compare the parent directory, spelling, extension and access error. LiteralPath addresses wildcard interpretation; it does not create a missing file or grant permission to a folder.

Decide whether the argument is a name or a pattern

Use literal selection when punctuation is part of one intended file's name. Use a wildcard-capable parameter only when a deliberate pattern should match a collection, and inspect that collection before any change.

Do not assume every command exposes LiteralPath or uses the same parameter names. Check the documentation for the later copy, move or other operation, preserving the intended exact-match behaviour. A successful Get-Item check is evidence about the selected item, not permission to apply an unrelated command blindly.

Keep the original filename and document links intact while investigating. Once exact selection is established, the next operation can be reviewed against the actual file rather than against an ambiguous pattern that happens to look like its name.

Sources: Microsoft Get-Item LiteralPath; Microsoft PowerShell wildcard rules.