Virtual root in a VHD mapped drive doesn't work

Open
#95 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
operating-systems

Research direction

Start by reproducing the ProjFs setup with --virtroot set to the VHD-mapped X:\ drive, then compare navigation through the first and second projected folder levels in Windows Explorer. Review the Managed-API behavior involved in virtual roots and establish whether the failure is a supported limitation or a defect; done means the behavior is explained and the issue is fixed or documented.

Written by the indexing model from the issue text.

Description

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:

image

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.

Dominant language
C#
Stars
174
Forks
40
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/ProjFS-Managed-API

All issues in microsoft/ProjFS-Managed-API

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.