Repository navigation
Explain native provider archival permissions and error 267 - #147
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provider-resource archival can report Windows error 267 under an unelevated token even when the EVTX export itself succeeds. The same export and EventViewerX archive API succeed after elevation on the affected workstation.
The guide explains how to check the file and parent directory, retry
Update-EVXLogArchivefrom an elevated terminal, and usewevtutilagainst an isolated copy to distinguish native Windows behavior from archive staging. This gives operators a practical diagnostic path before changing provider registration, permissions, or the Event Log service.Validation: direct
wevtutiland managedEventLogArchive.ArchiveResourcescomparisons retained the two-record export and produced its MTA companion after elevation. No service or system configuration changes were required.