windows local system account whoami shows a different result than %username%
I'm learning about the "local system" account (aka "system" or SID "S-1-5-18") in Windows. This server fault answer is very helpful, but one thing I still don't understand is why the value returned by the whoami command is different from the %username% environment variable.
The latter is the name of my computer followed by a dollar sign "$".
windows user-accounts username
asked Feb 1 at 16:51
rory.aprory.ap
2291516
add a comment |
I'm learning about the "local system" account (aka "system" or SID "S-1-5-18") in Windows. This server fault answer is very helpful, but one thing I still don't understand is why the value returned by the whoami command is different from the %username% environment variable.
The latter is the name of my computer followed by a dollar sign "$".
windows user-accounts username
asked Feb 1 at 16:51
rory.aprory.ap
2291516
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20
add a comment |
I'm learning about the "local system" account (aka "system" or SID "S-1-5-18") in Windows. This server fault answer is very helpful, but one thing I still don't understand is why the value returned by the whoami command is different from the %username% environment variable.
The latter is the name of my computer followed by a dollar sign "$".
windows user-accounts username
asked Feb 1 at 16:51
rory.aprory.ap
2291516
I'm learning about the "local system" account (aka "system" or SID "S-1-5-18") in Windows. This server fault answer is very helpful, but one thing I still don't understand is why the value returned by the whoami command is different from the %username% environment variable.
The latter is the name of my computer followed by a dollar sign "$".
windows user-accounts username
windows user-accounts username
asked Feb 1 at 16:51
rory.aprory.ap
2291516
asked Feb 1 at 16:51
rory.aprory.ap
2291516
asked Feb 1 at 16:51
rory.aprory.ap
2291516
asked Feb 1 at 16:51
rory.aprory.ap
2291516
asked Feb 1 at 16:51
rory.aprory.ap
2291516
2291516
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20
add a comment |
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20
add a comment |
1 Answer
1
active
oldest
votes
Basically System is a special User, it effectively is your computers internal user so it kinda makes sense to use the hostname as name.
Take a look in Task Manager, go to the Details tabs and click PID ("Process ID") to sort the processes. The lowest few PIDs and the only process without a PID are all owned by SYSTEM and start at the earliest stages of the boot process. The Processes are run under the user "SYSTEM" and several are instances of ntoskrnl.exe - the Windows NT Kernel itself.
This Windows startup process article describes the general boot process and identifies the main components all of which are run as System.
Also worth mentioning the System user has special permissions so avoid modifying it or using it for none system tasks.
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401066%2fwindows-local-system-account-whoami-shows-a-different-result-than-username%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Basically System is a special User, it effectively is your computers internal user so it kinda makes sense to use the hostname as name.
Take a look in Task Manager, go to the Details tabs and click PID ("Process ID") to sort the processes. The lowest few PIDs and the only process without a PID are all owned by SYSTEM and start at the earliest stages of the boot process. The Processes are run under the user "SYSTEM" and several are instances of ntoskrnl.exe - the Windows NT Kernel itself.
This Windows startup process article describes the general boot process and identifies the main components all of which are run as System.
Also worth mentioning the System user has special permissions so avoid modifying it or using it for none system tasks.
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
add a comment |
Basically System is a special User, it effectively is your computers internal user so it kinda makes sense to use the hostname as name.
Take a look in Task Manager, go to the Details tabs and click PID ("Process ID") to sort the processes. The lowest few PIDs and the only process without a PID are all owned by SYSTEM and start at the earliest stages of the boot process. The Processes are run under the user "SYSTEM" and several are instances of ntoskrnl.exe - the Windows NT Kernel itself.
This Windows startup process article describes the general boot process and identifies the main components all of which are run as System.
Also worth mentioning the System user has special permissions so avoid modifying it or using it for none system tasks.
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
add a comment |
Basically System is a special User, it effectively is your computers internal user so it kinda makes sense to use the hostname as name.
Take a look in Task Manager, go to the Details tabs and click PID ("Process ID") to sort the processes. The lowest few PIDs and the only process without a PID are all owned by SYSTEM and start at the earliest stages of the boot process. The Processes are run under the user "SYSTEM" and several are instances of ntoskrnl.exe - the Windows NT Kernel itself.
This Windows startup process article describes the general boot process and identifies the main components all of which are run as System.
Also worth mentioning the System user has special permissions so avoid modifying it or using it for none system tasks.
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
Basically System is a special User, it effectively is your computers internal user so it kinda makes sense to use the hostname as name.
Take a look in Task Manager, go to the Details tabs and click PID ("Process ID") to sort the processes. The lowest few PIDs and the only process without a PID are all owned by SYSTEM and start at the earliest stages of the boot process. The Processes are run under the user "SYSTEM" and several are instances of ntoskrnl.exe - the Windows NT Kernel itself.
This Windows startup process article describes the general boot process and identifies the main components all of which are run as System.
Also worth mentioning the System user has special permissions so avoid modifying it or using it for none system tasks.
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
answered Feb 1 at 18:45
MisterSmithMisterSmith
2645
2645
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
add a comment |
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
This doesn’t explain the reason whoami behaves the way it does. It explains what the system user is, but that isn’t, what he author asked about
– Ramhound
Feb 1 at 18:59
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401066%2fwindows-local-system-account-whoami-shows-a-different-result-than-username%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please edit the question with these answers : Which specific version of Windows is this (Windows 10v1809 for instance) ? Are you starting cmd in a non-standard way, for instance, choosing "Run as Administrator" ?
– Christopher Hostage
Feb 1 at 19:04
Windows 7 Pro SP1, just start > run > cmd.
– rory.ap
Feb 2 at 15:20