Odd Powershell FileSystemProvider Behavior So, I've been working with Powershell more and more recently. I ran into a rather interesting ... bug, at least, I think it is anyway. The other day I decided to use Powershell instead of my normal command prompt to mount a WIM file to a folder on the filesystem, so I could view/edit it. I ran the command, and was told that the folder successfully mounted to a folder on the root of my c:\ drive. As per my personal custom, I quickly did a dir (alias for Get-ChildItem in Powershell) to make sure the folder was there (don't ask me why, but I do ... it's just habit). Surprisingly enough, however, the folder disappeared!

After opening up Windows Explorer, and traversing the folder structure, I knew something had to be up. I did an actual dir command in the regular command prompt, and it showed up. So, I guess what the problem is, is some sort of bug in the FileSystemProvider .NET class, which is the provider used in the Get-ChildItem Cmdlet to browse an NTFS (at least) filesystem.

I'm kinda curious to know if anyone else has noticed this same behavior ...  ¶ 1:08 PM