1

On a Windows 10 enterprise machine I have configured shell launcher according to this technical article.

I only configured a custom shell for user1, who is not an admin; I didn't set a default shell nor changed the shell for administrators. When I log in with user1 credentials everything works as expected.

Otherwise when I log in as an administrator I only have a command window. I can launch explorer from it but I have other limitations.

This is an unexpected behavior, I thought other users would not been affected from the custom shell set for user1. How can I gain full control of the machine when I need to do administrative tasks ? Am I supposed to disable shell launcher via powershell ?

Improve this question
2
  • The referenced article is for setting up a shell on a kiosk system, not one for general use. The article referenced specifically calls out the fact that it replaces explorer.exe. However, it appears that this article, also about Shell Launcher, provides information on using Shell Launcher for customizing the shell on a per-user basis.
    – Jeff Zeitlin
    Commented Jun 11, 2020 at 9:51
  • It seems I solved the problem. I set the default shell to explorer.exe, so nothing change for every other user except user1. According to my experience setting a custom shell for a single user SID causes the default shell to be set to cmd.
    – Filippo
    Commented Jun 11, 2020 at 10:38

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .