ProjFS doesn't allow deletion of virtualization root directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- operating-systems
Research direction
Start by reproducing the Win10 1903 behavior with a ProjFS virtualization root and observe Explorer deletion. Investigate how root deletion is handled around the PRJ_NOTIFICATION_PRE_DELETE callback; done means the provider receives the root notification and can allow or block deletion with the expected result instead of error 0x80070032.
Written by the indexing model from the issue text.
Description
Note: I tried finding a ProjFS category in Feedback Hub because https://github.com/Microsoft/VFSForGit/issues/504 mentioned that one was in progress, but I couldn't find it.
Repro steps (I am running on Win10 1903):
- Add a virtualization root.
- Go into Explorer and try to delete the folder.
Expected results: I had expected ProjFS to support root deletion, specifically sending a PRJ_NOTIFICATION_PRE_DELETE for the root context so I can shut down my virtualization provider and return success or optionally block the deletion using an error code.
Actual results: Other than one directory enumeration callback, I don't receive a callback in my provider and Explorer shows an "unexpected error" dialog showing error code 0x80070032
This is important for my project because I am working on using ProjFS to virtualize my company's build output. I want to developers to be able to delete the root virtualization directory to do a completely clean build, but that doesn't work right now. Their workaround would be to run "rm -rf build/*" but that is confusing.
- Dominant language
- C#
- Stars
- 174
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/ProjFS-Managed-API
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/ProjFS-Managed-API#99 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/ProjFS-Managed-API#96 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
microsoft/ProjFS-Managed-API#95 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in microsoft/ProjFS-Managed-API
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100