Windows 10: Cannot launch WSL using a non admin user account in Windows 10 Home edition

Is this an issue? I installed WSL 2 in Windows 10 Home Edition using an admin adccount. I switched my account from admin to a non-admin user account. I cannot launch wsl from this account. Does one need to be logged into an admin account to use WSL console?Thanks,

:)

 

RDP to non-admin account not working


I can RDP to an account that is an admin account but not to a non-admin account.
I have read to check the users and make sure the appropriate accounts have been added to the user list but the option to view or edit the user list is missing from my settings window:



[Advanced Button:]



is there something I can check/change in the reg editor or in group policies or something to make this appear or perhaps just to enable it directly for that account?
For reference this appears the same if I'm logged in as admin or as non-admin. (have to give admin privileges anyway to see this window in the first place)
Thanks to anyone who can help

 

Strange Windows 10 User Account issue.

Unfortunately I had done those steps numerous reboots, it just, reappears for no good reason. The base account isn't even a Microsoft account, it's a local account.

I haven't quite tried the built in administrator account on W10, but so far in my experience on my own computer, the built in account seemed to have absolutely no more control than I did on my own.

It's just strange, I go in, it warns me twice about deleting the account, then it's gone. Reboot, and it's back?

EDIT: Just to specify, both command line and Netplwiz both say only HIS account exists on the computer, it doesn't list this rogue account. This is what I meant in my first post about the fact that even Windows doesn't seem to believe it exists, HALF the time. *Frown

 

My admin account switched to a user account!

The first of the many diagrams in this thread show that the link Sign in with a local account instead is displayed for the account that is currently logged on and so the reversion procedure might work for this account. For normal circumstances, that would initiate the conversion back to a local account for the user account currently logged in - see my 23rd & 26th September 2016 posts in revert to local account from one converted to MSAccount. I have no way of knowing how Windows will react to an attempt to use this procedure for the Built-In Admin account and I do not know if that link Sign in with a local account instead will be displayed or not.

I think I side-stepped this issue by suggesting that that

• An extra password-protected Admin level account is created, and
• The Built-In Admin is disabled, and
• The recovery attempt focuses on whichever existing user account remains active afterwards.

Personally, I would reinstall Windows 10 without even attempting this recovery. Installation takes very little effort once everything is backed up and the only necessary user interactions are right at the start & right at the end so it can be initiated before making a pot of tea. It took about 30, 60 & 90 minutes for each of my computers [the 30 minuter is 6 months old, the 60 minuter is 7 years old, 90 minuter is 12 years old].

Raner - I am trying to avoid sounding like I am nagging you into doing a clean install.

• Once you have recovered the existing user account you can attempt to re-enable & remove the MSAccount link from your Built-In Admin if that link appears in Settings, Accounts.
• Bree says it cannot be done and I think the same but I have never tried - I have never been able to get to Settings using the Built-In Admin because it cannot run any Windows 10 Apps so I do not know how it can be done [but the diagrams in Bree's link shows that those users got there].
• Even though I have the safety of having created two spare password-protected Admin accounts I would not want to know that my Built-In Admin was sitting in the background but unable to help me if my other accounts were corrupted.

Denis