Maybe it is better to skip that altogether if provider is not FileSystem provider?
e.g.: resolvedPath.Provider.Name.Equals(FileSystemProvider.ProviderName, StringComparison.OrdinalIgnoreCase)

... that section altogether ...

... that "DirectoryInfo code section" section altogether ...

I agree checking for the provider seems to be a better option.

will make the change

Need to make sure that FileSystem paths continue to work as they were before this new catch handler; 2 tests:

1. remove-item with -Path and filesystem path that contains *
2. remove-item with -LiteralPath and filesystem path that contains *

Looks like there's tests for -Path, I'll add a test for -LiteralPath with *

Looks like the current code does nothing if you use a * with -literalpath:

remove-item -literalpath .\a*.xml

I'll fix it so it returns error when using -literalpath, but it's a breaking change

Please add -ErrorAction SilentlyContinue -Force

will add

Please assign to null.

$null = New-Item -Force $testPath

will fix

I agree checking for the provider seems to be a better option.