Skip to content

Avoid Fail fast for registry key path not found during watcher re-arm#627

Merged
ChrisGuzak merged 1 commit intomicrosoft:masterfrom
SrinivasNunna:patch-1
Mar 24, 2026
Merged

Avoid Fail fast for registry key path not found during watcher re-arm#627
ChrisGuzak merged 1 commit intomicrosoft:masterfrom
SrinivasNunna:patch-1

Conversation

@SrinivasNunna
Copy link
Copy Markdown
Contributor

During a watcher re-arm attempt after key is deleted, applications using AppV layer, try to recreate the delted registry from cache and often fail with ERROR_FILE_NOT_FOUND, thus cauing wil callback to failfast and crash the user application

During a watcher re-arm attempt after key is deleted, applications using AppV layer, try to recreate the delted registry from cache and often fail with ERROR_FILE_NOT_FOUND, thus cauing wil callback to failfast and crash the user application
@ChrisGuzak
Copy link
Copy Markdown
Member

I understand this error codes are emitted by AppV and not the default Win32 API behavior. I also understand changing AppV is hard or not possible. please confirm that in your PR description.

@ChrisGuzak ChrisGuzak self-assigned this Mar 24, 2026
@ChrisGuzak ChrisGuzak merged commit 2edb790 into microsoft:master Mar 24, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants