Hello,
I'm just playing with powershell at the moment, so there is no practical use for the functionality that I'm having issues with. However, it seems to be such a fundamental issue that I can't understand why it hasn't been asked and/or resolved.

I'm using powershell 2.0. When I try to list registry keys containing the / character I get the following output.
Get-ChildItem : The registry key at the specified path does not exist.
At line:1 char:3

The problem is most easily reproduced, and noticeable, by running the following command from HKCU:
Get-ChildItem -recurse | Where-Object {$_.Name -like "/"}
This should return only problematic registry keys.
If that doesn't reproduce the problem, try cd to HKLM: and run the following command.
$something = Get-ChildItem -recurse
This will store all the good objects that are returned instead of displaying them and make it easier to see the errors that should surely be found on any system.

I'm sure anyone reading this will assume, as I have, that the problem is that the provider is seeing the / char as an escape sequence. Therefore the path that is being used is, in fact, not a valid path.

I would greatly appreciate it if someone could show me a workaround. Otherwise, I will hope to see this issue resolved in the final release or the next version.

Thanks,
Harley

Looks like someone did create a new connect bug to track this. What's odd is that I see two or three old ones which are closed with the "won't fix" reason which makes no sense. I'll dig into it a little bit.

current open bug: https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=391188&SiteID=99

Also this one: https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=390694&SiteID=99

Thanks halr9000.
I can't look at the bug tracker on connect because it seems to be down at the moment, but I appreciate you bringing it back to someone's attention. I seems like a significant problem to me. I don't understand how it wouldn't be addressed. It shouldn't be a hard thing to address on a provider level.

The site is up, but it's weird about hotlinking directly to bugs. Might work better if you go to connect.microsoft.com, sign in, make sure you've joined the PowerShell project, and now the cookie is set so the URL should work.

I appriciate you taking interest in this little issue halr9000. Since the release of this last Windows 7 beta, I bet the focus of most professionals will be there. The connect post was much more detailed than my post, and illustrated more problems than I was aware of. I'm sure this will be addressed now. Please let me know if you find anything new.
Thanks