Login is with a pin code and right clicking on cmd
allows running in an elevated mode as Administrator
so that new accounts can be created:
adding a user:
PS C:\Windows\System32>
PS C:\Windows\System32> New-LocalUser
cmdlet New-LocalUser at command pipeline position 1
Supply values for the following parameters:
Name: nicholas
Password: *****************************************
Name Enabled Description
---- ------- -----------
nicholas True
PS C:\Windows\System32>
PS C:\Windows\System32>
PS C:\Windows\System32> Get-LocalUser
Name Enabled Description
---- ------- -----------
Administrator False Built-in account for administering the =
computer/domain
DefaultAccount False A user account managed by the system.
defaultuser100001 True
foo True
Guest False Built-in account for guest access to the =
computer/domain
nicholas True
WDAGUtilityAccount False A user account managed and used by the system =
for Windows Defender Application Guard scen...
PS C:\Windows\System32>
While the Administrator account isn't enabled, the foo
user can run cmd
with Administrator
privileges. The newly created account shows as enabled yet isn't available from the login-screen as an option.
system info:
PS C:\Users\foo>
PS C:\Users\foo> [System.Environment]::OSVersion
Platform ServicePack Version VersionString
-------- ----------- ------- -------------
Win32NT 10.0.22621.0 Microsoft Windows NT 10.0.22621.0
PS C:\Users\foo>
PS C:\Users\foo>
PS C:\Users\foo> cmd /c ver
Microsoft Windows [Version 10.0.22621.1105]
PS C:\Users\foo>
While Windows 10
is shown above, winver
shows Windows 11
:
the newly created user isn't listed as an option to login. There are no options, only the single account.
I'm not understanding the finer points distinguishing an account from a profile. Can I not login as a different user somehow?
From IRC, a suggestion from Akik is to run:
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
and another suggestion from jborean93 is: