Skip to content
Discussion options

You must be logged in to vote

This is intentional behavior. Logs don't fail if the UAC prompt is not granted/accepted, they just operate without the registered name.

The community build is designed for user's who control their computer, meaning they can answer UAC prompts with authority at installation time. Certified Builds account for elevation, machine-level installation concerns, and organizational deployment. These builds handle the event source name registration automatically.

We could add a warning in the installer, giving users the chance to cancel the install on failed name registration if desired. This would still be suppressed in silent installations though.

I'm going to move this to a discussion because th…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by coreybutler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1477 on October 24, 2026 15:33.