7

Group policy client service failed the logon - Windows

Date of publication of the material 26.09.2019 Article views 16 Number of likes to article 0 Number of Comments

  

The problem with logging into your Windows account in the form of a message with the text “Group policy client service failed the logon” very often appears thereby upsets many users of this OS (at least earlier it appeared more often - currently the number of users asking for help on thematic forums on this subject have declined markedly).

At the same time, it is quite difficult to determine the causes of the error in question and to find the best option for troubleshooting.

Group policy client service failed the logon - Access is denied

What if the computer writes "Group Policy Client Service "

Unfortunately, it is practically impossible to unambiguously diagnose the cause of this problem; therefore, it is advisable to immediately begin to search for a suitable method for eliminating it, using the well-known "method of trying different methods."

Option 1

If the problem concerns a specific account and passes all the others (i.e., with a different username and password, the user can safely use the system), then the following steps should be taken:

  • To begin with, it will not be superfluous to check the system for errors: this can be done with the "sfc / scannow" command.

Firstly start scan your PC - sfc / scannow

  • Next, press the key combination “WIN + R” and enter and execute the command “regedit”.

Run Registry with command: regedit

  • In the opened window of the registry editor, go to the path "HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ ProfileList".

Next need find path to the ProfileList

  • All relevant accounts will be located in the ProfileList folder: find the problem by looking at each folder and paying attention to the ProfileImagePath file, the value of which contains the name of the problem account and its location. Check to see if the path there is valid.
  • In the folder where the data about the "problem" account is stored, the name will be "S-1-5-25-xxxxxxx.bak" (approximate contents).
  • Accordingly, rename this folder (by removing the extension “.bak”), and restart the computer for all changes to take effect.

If this method does not solve the problem with logging into Windows, proceed to the next option.

Option 2

The second way is to create a new account and transfer a specific file from it to the problem account. This will require:

  • When you turn on the computer, hold down the "F8" button and wait for the "Advanced Boot Options" window to appear, in which select the "Safe Mode" section (true for Windows 7).
  • If you did not succeed in entering safe mode, you can proceed to option 3, but if the download was successful, open “This PC”, press the “alt” key to display the main panel and select the “View” - “Options” - "Change folder and search options" tab.

Set parameters to show all hidden Folders and Files

A situation is possible when nothing will happen after choosing these parameters - this may indicate the presence of virus activity in the system, which could ultimately lead to the occurrence of the problem in question.

  • Here, in Safe Mode, open “Control Panel” - “User Accounts” - “Manage another account”.
  • Click on the “Add a new user in PC settings” button, specify a name and be sure to give the new account administrator privileges.

Add a new user in PC settings

This will open Settings, where you will need to complete the account creation..

Next, at the stage of choosing an account, pay attention to the newly created account and wait until the desktop settings are completed, after which you will need:

  • If the download of the new account was successful, then conduct a full scan for viruses, because the virus may interfere with viewing hidden files.
  • Open “This PC” - “Local Disk C” - “Users”.
  • Now the important point: if previously there were 2 accounts that were not available for user login, and based on the recommendations suggested above, you created a third account, then in the list of the Users section, select one of the problematic accounts and go into it.
  • In the list of files and folders that opens, we are interested in a file called "NTUSER.dat", which must be transferred with replacement to the same directory in all accounts that open the problem in question.

Option 3

This method in terms of meaning and end result is similar to the above, but involves the implementation of some alternative steps.

So, option No. 3 can be applied even if the user fails to enter Safe Mode.

For its implementation, you may need bootable media with an operating system image (if you cannot use the built-in system recovery tools).

  • Turn on the computer, press and hold the F8 key until the Advanced Boot Options window appears.
  • In the list of possible scenarios that opens, select the "Computer troubleshooting" section.
  • In the first steps, the system will prompt you to select the language and keyboard layout, as well as enter the login and password of the administrator account.
  • After entering and confirming the data, the "System Restore Options" window will appear, in which you must select the last line "Command Prompt".
  • You will see a console in which run two commands: “net user UserName / add” and “net localgroup administrators UserName / add” (depending on the OS, you may need to enter the second command completely in English, that is, “net localgroup administrators username / add ").

Next, you must repeat the steps to copy the file "NTUSER.dat", described in detail in the previous troubleshooting method.

Option 4

The final method is a good alternative in situations where the problematic account is administrative.

The first steps are performed similarly: you need to run the command line, it is better if you do this through the system recovery tools.

After starting the command line and opening the console, you need to run the command "secedit / configure / cfg% windir% \ inf \ defltbase.inf / db defltbase.sdb / verbose", the purpose of which is to reset the local Windows security policy.

run the command in the CMD - is to reset the local Windows security policy

Conclusion

In conclusion, it is worth noting that the most useful option is to transfer the file "NTUSER.dat", which in the vast majority of cases helps to solve the problem. However, sometimes even a newly created account remains inaccessible to enter the system, which complicates the way out.

In this case, you can try a tougher way - the physical removal of the problem accounting (using a drive and another computer) or in a trivial way to reinstall Windows.

Comments
Add comments
Top