Windows 10: Windows 11 Home Work Account

Hi,I recently purchased a new laptop running windows 11 in S mode. I've taken it out of S mode and created an admin account using my personal 365 account and now joined it to my work network. For some reason the only account showing at the login screen is my local admin, so i don't have the option to log in as different company users.Is this normal? Have i purchased a device running the wrong OS and do i need to upgrade to Windows 11 Pro?So frustrated right now, so any assistance is appreciated.ThanksAndy

:)

 

Remove account

I suggest you backup your personalized files first before removing the account.
To delete an account, follow these steps:

1. Press WIN + X keys and click Command Prompt (Admin) from the menu.
2. Type the following command and press Enter. Replace test with the name of your sister's account. Code:

 

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

 

Unable to set up new computer with windows 11 work account

Hi Jose,

I followed your suggested steps but the same thing still happens when I complete the out of the box experience setup.

By the way, the only reason the device was even in the device list was because (as a troubleshooting step) I tried creating a local account and then connecting to my work account to verify that the windows install was working properly. So I'm not surprised I still got the same result