It seems that PowerShell does not allow access to \\?\GlobalRoot\Device
paths. This is really useful if you are trying to use the Volume Shadow copy
service on Windows XP, especially with the vshadow.exe from the VSS SDK. On
anything other that Server 2003 you can only create temporary shadow copies
and the only way to access them is via \\?\GlobalRoot paths.
As an example, this fails in PowerShell:
It seems that these paths are just being blocked internally and returning
"Get-ChildItem : Paths that begin with \\?\GlobalRoot are internal to the
kernel and should not be opened by managed applications."
That seems a little too restrictive, especially for a tool that is meant for
system admin tasks. Are there any plans to address this?