Virtual root in a VHD mapped drive doesn't work

[lucasorth]

I'm trying to setting up the ProjFs environment in a VHD mapped drive that I created for this.
Everything went well, I set the --virtroot to @"X:\" (my vhd drive letter), and the folders in the first level appears as well when I opened my windows explorer.
But when I try to navigate to the second level of folders hierarchy, I mean, the second projected level, the Explorer thorws an error like this:

I wasn't be able to find any bug in the Managed-API, if it really exists or this is a "by design" limitation.

My solution requirements not allow me to create a sub folder and set the virtual root to it, cause the path would be changed.

[cgallred]

Thanks for the report. I was able to reproduce the issue locally, and it is a bug in the ProjFS platform components that the Managed-API library depends on.

I've filed an internal bug for me to work on. I expect I can have the fix put into a future update for Windows. What version of Windows did you see this on?

[lucasorth]

Thanks for the quick response. I've tested in the following windows versions, both with the same error behavior:
10.0.19045 build 19045
10.0.22631 build 22631

Besides, I tried the vhd creation and attach process by diskpart utility and also via PowerShell commands.