Detect if the current process is elevated in Dashboard #3833
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.
Summary of the pull request
Detect if the current process is elevated instead of whether the user… is in the administrator group for showing the Dashboard
If the user is running in a split token session (typical behavior for an administrator account with UAC enabled) the Widgets provider is running non-elevated and COM callbacks running in Dev Home(elevated) will not work.
However, if the user is running with UAC disabled and running everything as administrator by default Widgets service will also be running with the same token.
This change switches from detecting whether Dev Home is running as a user with the administrator SID to a check that determines if there is a split token for elevation.
For an account with UAC enabled Widgets will still not work:
However, for a device with UAC disabled running as admin they work:
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist