René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Globber quietly fails expecting provider to handle no results","articleBody":"### Prerequisites\n\n- [X] Write a descriptive title.\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\n- [X] Search the existing issues.\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://docs.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\n\n### Steps to reproduce\n\nOn Windows:  `get-childitem \\\\.\\INVALID0\\*`\r\n\r\nNote that this is using device path syntax to a non-existing device\n\n### Expected behavior\n\n```console\nPath not found error\n```\n\n\n### Actual behavior\n\n```console\nNo results, no error\n```\n\n\n### Error details\n\n```console\nIt looks like somewhere in the globber it's ignoring a potential error here and just validating returned results against the wildcard.\n```\n\n\n### Environment data\n\n```powershell\nName                           Value\r\n----                           -----\r\nPSVersion                      7.4.0-preview.3\r\nPSEdition                      Core\r\nGitCommitId                    7.4.0-preview.3\r\nOS                             Microsoft Windows 10.0.25324\r\nPlatform                       Win32NT\r\nPSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}\r\nPSRemotingProtocolVersion      2.3\r\nSerializationVersion           1.1.0.1\r\nWSManStackVersion              3.0\n```\n\n\n### Visuals\n\n_No response_","author":{"url":"https://github.com/SteveL-MSFT","@type":"Person","name":"SteveL-MSFT"},"datePublished":"2023-05-08T18:33:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/19626/PowerShell/issues/19626"}