The System Administrator Has Restricted the Type of Logon – Here How To Fix it

It can be frustrating when you try to log into a computer and get an error message that the system administrator has restricted the type of logon you are attempting. This usually happens in corporate environments where system administrators want to limit access and maintain security.

There are a few things you can try to get around these logon restrictions, but you’ll need to proceed with caution – you don’t want to do anything that goes directly against your company’s security policies. This article will walk you through some troubleshooting steps to try to resolve the issue.


Troubleshoot Your Logon Attempt

The System Administrator Has Restricted the Type of Logon – Here How To Fix it 1

Double Check Your Credentials

The first thing to do is make sure you are using the correct username and password. Simply mistyping your credentials could trigger the error message about logon restrictions. Carefully re-enter your username and password to see if that allows you to bypass the error message.


Try Logging in from a Different Machine

If you are getting the logon restriction error on one machine, try moving over to a different computer and attempt logging in there. If you can log in successfully from another machine, then the issue is isolated to the first computer. It could be a corrupt profile or outdated security settings on that specific workstation.


Reset Your Password

Request a password reset from your system administrator or use self-service password recovery options if available. Logging in with a brand new password that has just been reset may allow you to bypass the restrictions.


Switch Logon Types

If you are using your personal Microsoft account try switching to log in with your corporate credentials instead. Or vice versa – if you are attempting to log in with a company account, try your personal Microsoft profile. The system administrator may have only limited one type of logon.


Check with Your System Administrator

If you’ve tried the above steps and are still running into login problems, it’s time to engage with your system administrator. They should be able to explain what restrictions are in place and why. Here are some things to check with them on:


Confirm Your Account Status

Make sure your user account is active and not restricted. System administrators have the ability to disable accounts or limit logons. Ask them to verify that your user account is still in good standing.


Review Security Group Memberships

In a corporate domain environment, user accounts are assigned to security groups that grant access to certain systems and resources. Have the system admin confirm you are still a member of the proper groups for the computer you are trying to access.


Check for Policy Changes

Find out if any new domain policies have been put in place that could be blocking your logon attempt. For example, your system admin may have implemented a new policy to disable external Microsoft account logons for additional security.


Investigate Two-Factor Authentication Issues

If two-factor authentication has been enabled, problems with your second factor could be preventing logon. Work with the system admin to troubleshoot your two-factor authentication setup.


Try an Alternate Account

If your personal account continues to be blocked, ask your system administrator if you can access the computer using an alternate “loaner” account. This account will be tied to your identity but have its own separate credentials. Logon restrictions tied to your old account won’t carry over.


Use Elevated Privileges

In certain cases, you may be able to bypass logon restrictions by elevating your privileges. Options include:


Run As Administrator

Right-click on the application shortcut and select “Run as administrator“. This will launch the program with admin rights, ignoring some logon locks.


Use RunAs

The Windows RunAs command allows you to run a program under alternate credentials. You’ll need an available admin username/password.


PsExec from Sysinternals

PsExec is a powerful utility that can run programs on remote computers with substituted user rights. Have your system admin set this up for you.

Use caution with these elevation methods – don’t try to circumvent security policies intentionally put in place by your organization.


Reset Your Profile

As a last resort, your system administrator can reset your user profile if it has become corrupted and is preventing logon. This will wipe your profile settings and restore defaults. Make sure to backup any data in your profile first!



Dealing with system administrator logon restrictions can be a headache, but using the right troubleshooting steps will help you get back into your account. Confirm your credentials are correct, try alternate logon methods, work with your system admin to review policies, and elevate privileges carefully. Resetting your user profile is also an option if all else fails. With some targeted effort, you should be able to overcome most logon limitation issues.



Q: What are some common reasons for logon restrictions?

A: Typical reasons include account security lockouts, disabled accounts, expired passwords, policy changes, missing group memberships, multi-factor authentication issues, and corrupt profiles.


Q: Can I reset the administrator password myself?

A: No, only a user with administrator privileges can reset the admin password. Standard users do not have access.


Q: Will using RunAs or Run As Administrator work on all logon restrictions?

A: No, elevated privileges may still be blocked by certain domain policies. But it’s worth trying on a case by case basis.


Q: Is there risk with resetting my user profile?

A: Yes, resetting your user profile will wipe all settings and data stored in the profile. Make sure to backup anything important first.


Q: If logon restrictions are in place for security reasons, could I get in trouble for bypassing?

A: You need to proceed with caution. Never intentionally try to circumvent corporate security policies. Always work with your system admin.

Leave a Reply