关节炎挂什么科

Question

I don't know anything about Windows and try to understand the concepts about Permissions. Unfortunately, simply Googling doesn't help at all.

Windows says that my user is a member of the "Administrator" group. But yet, when I normally run programs, such as PowerShell, they reject to do certain things, such as installing new services. However when I select "Run as Administrator" in the Start-Menu, they suddenly are able to do so. What's the mechanism behind that?

I created a file within a process (PowerShell) that was "Run as Administrator" and then checked the owner of the file in Windows. But much to my surprise, the owner was my own user, instead of the "Adminstrator" user.

What's going on?

Answer 1

See the Microsoft article Understanding User Account Control (UAC) and especially the section Standard and Administrator Access Tokens that fully explains what happens:

Standard and Administrator Access Tokens

1. When an administrator logs on, the user is assigned two separate access tokens:
   • a full administrator access token and a
   • standard user access token.
2. The full administrator access token is not invoked until the user attempts to perform an administrative task.
   • In other words, if you log on as a member of the local administrators group, you will run with your administrative privileges disabled until you attempt to run an application or task that has been marked to require administrative privileges. When UAC is enabled, local administrator accounts run as standard user accounts until elevation is required.