Windows 10: Different Directory Listings under Different Accounts
up vote
0
down vote
favorite
Consider the following on a freshly-installed Windows 10 environment with a single account named "User":
Logged in as "User", I create a file named "Test.txt" on my desktop and copy this to "C:". Windows displays a dialog warning me that this cannot be done unless permissions are elevated; I do this.
With this file now at the top level of my C drive, I now open CMD.exe as Administrator (by right-clicking the file from Explorer and choosing "Run as Administrator").
I CD to my C drive, and get a file listing of everything. My previously-copied text file is not there.
Next, still using the elevated copy of CMD I copy the Notepad executable from my Windows directory to the same top level of C; performing a "dir" confirms that this file is there.
Finally, I close CMD and go back to Explorer. Whilst I am still able to see my test text file as before, the just-copied executable for Notepad is not visible.
Is this behaviour due to some kind of permission/account differences - should I not expect to see files in C when running CMD as admin?
Thanks.
windows windows-10
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
Consider the following on a freshly-installed Windows 10 environment with a single account named "User":
Logged in as "User", I create a file named "Test.txt" on my desktop and copy this to "C:". Windows displays a dialog warning me that this cannot be done unless permissions are elevated; I do this.
With this file now at the top level of my C drive, I now open CMD.exe as Administrator (by right-clicking the file from Explorer and choosing "Run as Administrator").
I CD to my C drive, and get a file listing of everything. My previously-copied text file is not there.
Next, still using the elevated copy of CMD I copy the Notepad executable from my Windows directory to the same top level of C; performing a "dir" confirms that this file is there.
Finally, I close CMD and go back to Explorer. Whilst I am still able to see my test text file as before, the just-copied executable for Notepad is not visible.
Is this behaviour due to some kind of permission/account differences - should I not expect to see files in C when running CMD as admin?
Thanks.
windows windows-10
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Consider the following on a freshly-installed Windows 10 environment with a single account named "User":
Logged in as "User", I create a file named "Test.txt" on my desktop and copy this to "C:". Windows displays a dialog warning me that this cannot be done unless permissions are elevated; I do this.
With this file now at the top level of my C drive, I now open CMD.exe as Administrator (by right-clicking the file from Explorer and choosing "Run as Administrator").
I CD to my C drive, and get a file listing of everything. My previously-copied text file is not there.
Next, still using the elevated copy of CMD I copy the Notepad executable from my Windows directory to the same top level of C; performing a "dir" confirms that this file is there.
Finally, I close CMD and go back to Explorer. Whilst I am still able to see my test text file as before, the just-copied executable for Notepad is not visible.
Is this behaviour due to some kind of permission/account differences - should I not expect to see files in C when running CMD as admin?
Thanks.
windows windows-10
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Consider the following on a freshly-installed Windows 10 environment with a single account named "User":
Logged in as "User", I create a file named "Test.txt" on my desktop and copy this to "C:". Windows displays a dialog warning me that this cannot be done unless permissions are elevated; I do this.
With this file now at the top level of my C drive, I now open CMD.exe as Administrator (by right-clicking the file from Explorer and choosing "Run as Administrator").
I CD to my C drive, and get a file listing of everything. My previously-copied text file is not there.
Next, still using the elevated copy of CMD I copy the Notepad executable from my Windows directory to the same top level of C; performing a "dir" confirms that this file is there.
Finally, I close CMD and go back to Explorer. Whilst I am still able to see my test text file as before, the just-copied executable for Notepad is not visible.
Is this behaviour due to some kind of permission/account differences - should I not expect to see files in C when running CMD as admin?
Thanks.
windows windows-10
windows windows-10
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 20 at 19:00
user965628
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 20 at 19:00
user965628
1
asked Nov 20 at 19:00
user965628
1
1
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user965628 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
You are seeing UAC Virtualization in practice. When I first saw it I was stumped. It was developed for Windows 7 and continues in Win 10. If a normal user writes to one of the protected areas, Windows stores it in the users profile where it is only accessible by that user. Works with registry changes as well.
More from MS here
answered Nov 20 at 19:08
uSlackr
8,3232445
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You are seeing UAC Virtualization in practice. When I first saw it I was stumped. It was developed for Windows 7 and continues in Win 10. If a normal user writes to one of the protected areas, Windows stores it in the users profile where it is only accessible by that user. Works with registry changes as well.
More from MS here
answered Nov 20 at 19:08
uSlackr
8,3232445
add a comment |
up vote
1
down vote
You are seeing UAC Virtualization in practice. When I first saw it I was stumped. It was developed for Windows 7 and continues in Win 10. If a normal user writes to one of the protected areas, Windows stores it in the users profile where it is only accessible by that user. Works with registry changes as well.
More from MS here
answered Nov 20 at 19:08
uSlackr
8,3232445
add a comment |
up vote
1
down vote
up vote
1
down vote
You are seeing UAC Virtualization in practice. When I first saw it I was stumped. It was developed for Windows 7 and continues in Win 10. If a normal user writes to one of the protected areas, Windows stores it in the users profile where it is only accessible by that user. Works with registry changes as well.
More from MS here
answered Nov 20 at 19:08
uSlackr
8,3232445
You are seeing UAC Virtualization in practice. When I first saw it I was stumped. It was developed for Windows 7 and continues in Win 10. If a normal user writes to one of the protected areas, Windows stores it in the users profile where it is only accessible by that user. Works with registry changes as well.
More from MS here
answered Nov 20 at 19:08
uSlackr
8,3232445
answered Nov 20 at 19:08
uSlackr
8,3232445
answered Nov 20 at 19:08
uSlackr
8,3232445
answered Nov 20 at 19:08
uSlackr
8,3232445
8,3232445
add a comment |
add a comment |
user965628 is a new contributor. Be nice, and check out our Code of Conduct.
user965628 is a new contributor. Be nice, and check out our Code of Conduct.
user965628 is a new contributor. Be nice, and check out our Code of Conduct.
user965628 is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1377070%2fwindows-10-different-directory-listings-under-different-accounts%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
