Skip to content

Published: September 24, 2015 | Applies to:

If you can't logon due to "Your account has been disabled. Please see your system administrator." message in Windows 10, fix it here.

Sometimes, we face pretty odd and weird issues that makes us technically challenged to work on a Windows machine. Due to different permissions levels, we can create various kind of user accounts such as administrator, standard, child account etc etc. The built-in administrator account has all the privileges to modify other user accounts. He can enable or disable accounts on his wish. If he has blocked an user account, the user will receive following message at logon screen:

Your account has been disabled. Please see your system administrator.

FIX - Your Account Has Been Disabled. Please See Your System Administrator

But what if you’re the administrator and your account itself is blocked. In such cases, there may be two cases possible. Either you can boot to your system or not. Here are the fixes for corresponding for these situations:

FIX : Your Account Has Been Disabled. Please See Your System Administrator.

FIX 1 – Using Local User and Group snap-in

1. Press W8K + R and type lusrmgr.msc into Run dialog box, click/tap OK to open Local Users and Groups snap-in.

This File Does Not Have A Program Associated With It For Performing This Action In Windows 10

2. Next, click/tap on Users and then double click on your administrator or user account in the lusrmgr window, for which you’re facing issue.

FIX - Your Account Has Been Disabled. Please See Your System Administrator

3. In the administrator or user account property sheet, you have to uncheck Account is disabled option if it was checked already. Click Apply followed by OK.

FIX - Your Account Has Been Disabled. Please See Your System Administrator

You can now close Local Users and Groups snap-in window and re-try to log in into problematic account and it should work.

FIX 2 – Using Command Prompt at boot

1. Boot into System Recovery Options. Hit the Command prompt entry at following screen:

FIX - Windows 10 Master Boot Record Is Corrupted

2. Last step will result in opening of Command Prompt at boot.

FIX - Windows 10 Master Boot Record Is Corrupted

Select your admin account and enter your select account password to continue.

FIX - Windows 10 Master Boot Record Is Corrupted

3. Then type following command in the Command Prompt window:

net user administrator /active:yes

FIX - Your Account Has Been Disabled. Please See Your System Administrator

After running this command, you’ll get The command completed successfully message. You can then close the Command Prompt and reboot. After restarting the machine, you’ll be able to log-in.

Hope this helps!

Fix other logon issues:

1. [FIX] Your Device Is Offline. Please Sign In With The Last Password Used On This Device.

2. [FIX] The Group Policy Client Service Failed The Sign-in. The Universal Unique Identifier (UUID) Type Is Not Supported.

3. [FIX] “You Can’t Sign In To Your PC Right Now” In Windows 8 Or Later


SHARE: Facebook Google+ Twitter

8 Comments

  • but i totally cant do anything…..i juz stucked in the window tat keep popping your account has been disable…….

  • Yes i have also the same problem “i totally cant do anything…..It just stucked in the window tat keep popping your account has been disable”

  • Kapil Arya

    ^^ You should boot from your recovery or installation media and follow FIX 2.

  • I had booted from recovery and followed your FIX 2 method. But facing the same problem i.e Your Account Has Been Disabled. Please See Your System Administrator. thank you for helping us by sharing your knowledge.

  • THANK YOU SO MUCH FOR THE SHARING OF YOUR IDEA MAN.YOUR SUCH A GOOD MAN

  • Kapil Arya

    ^^ Glad we could help :D

  • I have the problem too with my stand alone desktop pc one other user on the w7 . None of the solutions suggested on this I have tried worked. The screens depicted in them were not seen on my PC. The only user account probably with admin rights was disabled; new account with admin rights entered; shut off probably before saving the stuff. Absolutely no way to get into the system or out of the loop – power down only stopped the system.

    If you know how to modify the registry with regedit let me know. That seemed to be okay. Upgrade from w7 through w7 update screens worked okay for 4 days the time took me to get to know the w10 with its totally bad colors (!) and different icons on desk top. Then the system crashed and auto recovered but lost the original desktop; took another 1 1/2 days to figure out to get back my w7 desktop items. Then wanting to revert to W7 required the new user account created. So finally figured out it was the auto-recovered account. Trying to see the disabling and creating new account work, I royally got the screw up.

    I had a boot-able pen drive for w10 setup downloaded from ms through media creation tool could get me to safe mode with prompts. Activation of default admin, guest, user, adding new user local group, etc., through ‘net user’ looked fine until reboot w/o the pen drive. The went back to the square one – locked with the user name disabled. w7 user name with admin rights was the w10 and recovered w10 user names. CAN’T ROLL BACK TO W7. Reset will destroy all programs including windows.old file. Messing up registry with importing a SAM hive from a w8 laptop worked okay on the surface. Rebooting got the problem fixed it back.

    Thanks.

    Riki

  • what will i do when my administrator and local account both are disable???

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    What's New


    Recent Comments

    • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

      1 hour ago

    • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

      2 hours ago

    • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

      3 hours ago

    • Charles : I followed your steps but got stuck at step 9 since I couldn...

      9 hours ago

    • Barry : Fantastic! You solved my problem with very clear instruction...

      10 hours ago

    • Keith Fessey : Ok, so whats the difference between the "recovery key" and t...

      14 hours ago


    Windows Group Policy Troubleshooting