Download PC Repair Tool to quickly find & fix Windows errors automatically
From unexpected freezing to annoying notifications, Windows 10 has such little quirks, but you can fix them with some help. For example, when you install or launch a service application in Windows, an error message is displayed with the following description –
Windows could not start the Service on Local Computer.
Error 1069: The service did not start due to a logon failure
The issue usually occurs when one of the following happens.
- A user provides a wrong account password when configuring your service, or
- A user has changed the password of the account used by the service but failed to update the information in the service.
To fix it, you’ll need to take the following steps.
- Open Services snap-in.
- Right-click on the service having the issue.
- Select Properties.
- Switch to Log On tab.
- Check if the Local system account radio button is selected.
- Change it to This account.
- Enter the correct password.
- Press OK.
Let’s explore the above steps in a bit more detail!
Type services.msc in the Windows 10 Search box and select the Services option to open the Services snap-in.
Look for the service name that is having an issue. When found, right-click it and select the Properties option.
Next, under the service property sheet, switch to the Log On tab.
Here, check if the Local System account radio button is checked. If yes, you’ll need to deselect it.
Once done, check the ‘This account‘ radio button.
Enter the correct password.
When done, hit the OK button to save the changes and restart your computer.
Hereafter, when you try to run the service, you should not see the ‘The service did not start due to a logon failure’ message again in Windows 10.
Hope it helps!
TIP: More generic suggestions to troubleshoot Windows Services will not start issues.
A post-graduate in Biotechnology, Hemant switched gears to writing about Microsoft technologies and has been a contributor to TheWindowsClub since then. When he is not working, you can usually find him out traveling to different places or indulging himself in binge-watching.
Download PC Repair Tool to quickly find & fix Windows errors automatically
From unexpected freezing to annoying notifications, Windows 10 has such little quirks, but you can fix them with some help. For example, when you install or launch a service application in Windows, an error message is displayed with the following description –
Windows could not start the Service on Local Computer.
Error 1069: The service did not start due to a logon failure
The issue usually occurs when one of the following happens.
- A user provides a wrong account password when configuring your service, or
- A user has changed the password of the account used by the service but failed to update the information in the service.
To fix it, you’ll need to take the following steps.
- Open Services snap-in.
- Right-click on the service having the issue.
- Select Properties.
- Switch to Log On tab.
- Check if the Local system account radio button is selected.
- Change it to This account.
- Enter the correct password.
- Press OK.
Let’s explore the above steps in a bit more detail!
Type services.msc in the Windows 10 Search box and select the Services option to open the Services snap-in.
Look for the service name that is having an issue. When found, right-click it and select the Properties option.
Next, under the service property sheet, switch to the Log On tab.
Here, check if the Local System account radio button is checked. If yes, you’ll need to deselect it.
Once done, check the ‘This account‘ radio button.
Enter the correct password.
When done, hit the OK button to save the changes and restart your computer.
Hereafter, when you try to run the service, you should not see the ‘The service did not start due to a logon failure’ message again in Windows 10.
Hope it helps!
TIP: More generic suggestions to troubleshoot Windows Services will not start issues.
A post-graduate in Biotechnology, Hemant switched gears to writing about Microsoft technologies and has been a contributor to TheWindowsClub since then. When he is not working, you can usually find him out traveling to different places or indulging himself in binge-watching.
I have written my own windows service which interacts with a SQL database and updates it. The service was running fine and seems to be functioning correctly, however of late it seems to go down at random times and cannot restart due to the error designated in the question. I have tried various searches to fix this, but unfortunately I have come up with nothing. The aim is to eventually having this service running on my companies server, but I can’t adjust any server settings, I am but a user on the server, so I have restrictions to some settings.
Any quick fixes, would be helpful!
asked Sep 2, 2014 at 8:33
- Open the Services Manager. ( Win + R, then type services.msc )
- Then right click on the SQL Server process and click Properties
-
Then go to Log On, and select This account:
-
Then click Browse, and add your username in the box. (Notice it should contain the domain, in my case is ADmyusername), then Check Names and accept.
-
Finally type your password in the other two fields, and that’s it, you should have permission to start your process now.
Cheers!!
answered Jan 22, 2019 at 18:50
2
One issue for us was the format of the account user name, we initially used
domainusername
and got the 1069-logon error, then ultimately I tried validating the user name in the properties | logon tab of the Service (in Control Panel / Service Manager), using the «Browse» and «Search» for the user name and it turned it suggested and validated ok with the reverse format
username@domain
This also worked and resolved the 1069 error, and let us script the startup using sc.exe.
answered Aug 31, 2015 at 8:29
Mosca PtMosca Pt
4974 silver badges10 bronze badges
3
Error 1069 is vague and can have different causes. I am sharing my experience here.
I encountered this error when trying to get a service to run under my account (I am trying to get my services to see the same LocalDB as interactive processes running on my account for development purposes). I use an MSA (Microsoft Account) with Windows’s PIN login normally, so I rarely enter my Windows password. To resolve the issue, I locked my screen, selected Password input instead of PIN input, and then entered my password. I assume this somehow reminded Windows what my password was and made my local account more legit.
Before doing this, you need to configure the user account in question to have the Logon as Service privilege. To do this, open the Group Policy Editor. Expand Computer / Windows Configuration / Security Configuration / Local Policies / User Permissions Assignment and then open Login as Service. From there, you can add your user in question.
answered Feb 28, 2019 at 15:11
binkibinki
7,3365 gold badges65 silver badges104 bronze badges
3
also check for «Deny Logon service» policy.
user should not be added over there
answered Sep 26, 2019 at 14:31
varunvarun
411 bronze badge
1
We had this issue as well because the account was set so that the password expired. After we updated the account to not expire and set the password this error stopped.
answered Aug 15, 2017 at 2:53
campocampo
1,8521 gold badge17 silver badges19 bronze badges
1
The account could also be locked out. To unlock it, you only need to change that user’s password (new and old password can be the same).
What also worked for me was re-entering the password in the services->LogOn window. Even when you think the account and password is correct, re-entering it will re-grant the account permission to log on as a service.
answered Dec 6, 2022 at 11:14
FFFffffFFFffff
6567 silver badges17 bronze badges
When you try to run a service in MySQL or any other NT service you are facing, Error 1069 The Service Did Not Start Due To A Logon Failure error. This error is particular to user account details under which the service is running. Either the user credentials have been changed deleted, or the format of the username and domain is not appropriate. Today in this error solving guide on Error 1069 error, we will fix this error. We have gathered a couple of working methods that will fix this error in a few moments.
Causes of Error 1069 The Service Did Not Start Due To A Logon Failure Error:
Windows has some services that always run in the background called as NT services. These NT services use user credentials details and have their own security environment so that they independently use system resources and other service resources. When the user credentials are modified, changed, or deleted these services throw the Error 1069 The Service Did Not Start Due To A Logon Failure error. Let’s take a look at its possible cause.
- Windows Update
- Corrupted Hard Drive
- Program Update
- Virus or Malware Attack
- Multiple Program Processing Running at a time
- Older CPU
Similar Type of Error 1069 The Service Did Not Start Due To A Logon Failure Error:
- 0x8007042d
- Error 1068
- Event id 7000
- Pdq deploy
- Tableau
- Error 1069 logon failure oracle database
- Windows service logon failure
- Jenkins
In this section, we will go through some of the methods by which you can fix this Error 1069 The Service Did Not Start Due To A Logon Failure error easily.
1. Configuring the Service to Use Local System Account –
If you are logged in using a different user account, make sure that the service is using the current account; otherwise, it will, through the Error 1069 The Service Did Not Start Due To A Logon Failure 0x8007042d error. Follow the steps to use the current account.
In this Error 1069 The Service Did Not Start Due To A Logon Failure event id 7000 method, we will check for the authority of the user account and enable it.
- STEP 1. Click on Start, and type Run then hit Enter
- STEP 2. Type services.msc in the Run box and hit Enter
- STEP 3. Locate the service throwing error, right-click on and go to properties
- STEP 4. In General, tab firstly Stop the service, then move to Log on the tab
- STEP 5. Now kindly check on Local System Account
- STEP 6. Make sure not check Allow service to interact with the desktop
- STEP 7. Go back to General tab and Start the Service
- STEP 8. Click on Apply and then OK
2. Restoring the User Right’s to Use Log on Service –
Some users are unable to access and make changes in the services due to revoked permissions, and this can be done using domain controllers.
- STEP 1. Click on Start, type Run, and hit Enter
- STEP 2. Now in the run box type Control Panel and hit Enter
- STEP 3. Change View to Small and Go to Administrative Tools
- STEP 4. In Administrative Tools Go to Active Directory Users and Computers>users
- STEP 5. On the right, Right Click on Domain Controllers and go to Properties
- STEP 6. Move to Group Policy Tab > Default Domain Controllers Policy
- STEP 7. Click on Edit, and navigate to,
Computer Configuration> Windows Settings> Security Settings> Local Policies
- STEP 8. Go to User Rights Assignment & Right-click Log on as a service on the right
- STEP 9. Click on Add User or Group, type the username you want to add to the policy
- STEP 10. Click Apply then OK
- STEP 11. Close all the windows and Restart System
3. Taking Control of the Service –
In this Error 1069 The Service Did Not Start Due To A Logon Failure BizTalk method, we will check for the authority of the user account and enable it.
- STEP 1. Click on Start, and type Run then hit Enter
- STEP 2. Type services.msc in the Run box and hit Enter
- STEP 3. Locate the service throwing error, right-click on and go to properties
- STEP 4. In General, tab firstly Stop the service, then move to Log on the tab
- STEP 5. Now click on Browse, Under ‘Enter the object name to select.’
- STEP 6. Type your user account name and click on the check
- STEP 7. Wait till you user name appears and then click OK
- STEP 8. It may ask for your user password so enter it and click OK
- STEP 9. After setting and Start the service by going to the General tab
- STEP 10. Now you can run your program or service without any error
4. Changing the Password –
Make sure to have the password for the specified user account matches the current password for the same user.
**NOTE: Follow the STEP 1-4 in Method 3
- STEP 1. Now in type in the Password
- STEP 2. Start the service by going to the General tab
- STEP 3. Click Apply and then OK
- STEP 4. Now you can run your program or service without error
Conclusion:
With this being the end of the article on fix Error 1069 The Service Did Not Start Due To A Logon Failure error. We have demonstrated you all the methods with step by step approach. In this Error 1069 article, we have discussed the error, its effect, cause, and ways to fix.
We hope this Error 1069 The Service Did Not Start Due To A Logon Failure error article is helpful and fixes your issue. For more articles on error, fixing, follow us. Thank You!
31.03.10 — 10:25
Windows Server 2003 SP2
Там уже уже работает сервер 8.1
Установил 8.2, при установке указал юзера как Administrator , а не как Users1C.
Теперь хочу параллелно с сервером 8.1 запускатьсервер 8.2, выдает ошибку :
Error 1069: The service did not start due to a logon failure
Вроде сервера 8.1 и 8.2 могут вместо работать, в чем может быть проблема?
1 — 31.03.10 — 10:26
могут, если для одного из них порты менять
2 — 31.03.10 — 10:26
3 — 31.03.10 — 10:27
«The service did not start due to a logon failure» — пароль надо вводить какой надо, а не какой хочется.
4 — 31.03.10 — 10:33
(3) Спасибо, пароль помнял, вроде пошло. Но появилась другая ошибка:
The Агент сервера 1С: предприятие 8.2 service on local Comuter started and then stopped. Some services
stop automatically if the have no work to do? for example, the performance logs and alerts service
5 — 31.03.10 — 10:34
(4) см (2)
6 — 31.03.10 — 13:13
Что-то не смог решит проблему, помогите плиз
7 — 31.03.10 — 13:15
(6) что делал?
8 — 31.03.10 — 13:27
(7) Оба сервера использую 1 порт. Как назначить другой порт для агента сервера 8.2? в консоли сервисов не могу
9 — 31.03.10 — 13:29
(8) в ветке реестра прописать порт например вместо 1541 1641 и т.п.
какая ветка не помню, можно поискать.
Посте правки реестра, просто запустить сервис и всё.
10 — 31.03.10 — 13:31
HKEY_LOCAL_MACHINESYSTEMControlSet001Services1C:Enterprise 8.2 Server Agent
в нем:
«C:Program Files1cv828.2.10.77binragent.exe» -srvc -agent -regport 1641 -port 1640 -range 1660:1691 -debug -d «C:Program Files1cv82srvinfo»
кактотак
11 — 31.03.10 — 13:31
(9) Ты имеешь ввиду regedit.exe ?
12 — 31.03.10 — 13:33
в общем, смотреть только на порты и можно еще -debug дорисовать… тоже кошерно
13 — 31.03.10 — 13:35
+(10) е-мае, конечно же вместо ControlSet001 должно быть CurrentControlSet
14 — 31.03.10 — 13:36
Спасибо всем, помогло
15 — 31.03.10 — 13:37
(11) да. Ты вообще искал что-нибудь по форуму? Или ограничился прочтение ветка, ссылку на которую я дал? Попробуй. полезно бывает.
16 — 31.03.10 — 13:43
(15) Блин, время сжигает, план горить. Поэтому времени не было для поиска 🙂
17 — 31.03.10 — 14:01
(11) да
После обновления платформы на сервере, указанные правки в реестре повторить, сервис запустить.
А потом как-нибудь сервер 1С 8.1 перевести на нестандартный порт, а 8.2 перевести на стандартный. Т.к. по моему 8.1 прекратили обновлять.
18 — 31.03.10 — 14:05
(17) Всем на 8.2!!! Срочно!!!
19 — 31.03.10 — 14:11
(17) т.е без переноса порта 8.1 на другой не получится? у меня 50 юзеров сидят на 8.1. Они же меня растопчуть просто!
20 — 31.03.10 — 14:16
(19) получится, конечно.
Пользователей нужно постепенно переводить на 8.2.
т.к. стартер 8.2 умеет запускать базы 8.1. Нужно в настройках базы указать версию 8.1.
Сделать средствами 1С 8.2 файлик например Базы1С.v8i где прописать все базы 8.1 с нужным портом. И раздать ссылку на него всем.
Приложением по умолчанию для v8i должно быть 8.2, т.е. 1cv82common1cestart.exe
21 — 31.03.10 — 14:19
+ (20)
Если 8.2 заглючит, и не захочет запускать 8.1, срочно поменять ссылку например на такую:
«C:Program Files1cv81bin1cv8.exe» /RunShortcut «c:Documents and SettingsAll UsersДокументыБазы1С.v8i»
22 — 31.03.10 — 14:22
(20) В консоли кластера 8.2 создал новую базу. Все успешно.
Но в стартере 8.2 не могу подключить эту базу, пишет типа : Различаются версии клиента и сервера (8.2.10.82 — 8.1.15.14)
23 — 31.03.10 — 14:25
(22) новую? или подключил существующую?
Если новую, то нужно в настройках подключения писать
server:1641
Если подключил старую, то в настройках указать Версия 8.1.
24 — 31.03.10 — 14:28
(23) Огромное спасибо! Выручал!
25 — 31.03.10 — 14:31
Как рекомендовать в базу знаний?
26 — 31.03.10 — 14:32
(25) не стоит.здесь эта тема обмусолена 100 раз. ты не умеешь пользоваться поиском
27 — 31.03.10 — 14:36
(26) Понятно
28 — 31.03.10 — 14:36
(25) Такой куйнит в БЗ не нужно.
29 — 31.03.10 — 14:37
(28) )))
30 — 31.03.10 — 14:39
(28) Все когда-то начинали с первого шага, такчто не стоит издеваться 🙂
MaxS
31 — 01.04.10 — 09:09
Наверное это будет в тему топика. Т.к. некоторого эффекта от установки 1С 8.2 не достигнуто.
На терминале на общем рабочем столе лежит например Базы1С.v8i, где средствами 1С 8.2 прописаны базы 1С 8.1. У некоторых пользователей этого терминального сервера всё нормально. Выбираем базу, запускается 1С 8.1. У некоторых после выбора базы ничего не происходит. Подвисает ненадолго и тишина. У них же запуск по варианту (21) происходит без проблем.
В чем проблема? Кто-нибудь сталкивался? Почему программа запуска 1С 8.2 не запускает 8.1?
- Remove From My Forums
-
Вопрос
-
Every time I start the Update Services on my Windows Server 2003, I get the following error:
Error 1069: The service did not start due to a logon failure.
I applied the suggested fix from this article: http://support.microsoft.com/kb/555989 but problem remains.
-
Перемещено
24 августа 2012 г. 5:39
(From:Directory Services)
-
Перемещено
Ответы
-
Every time I start the Update Services on my Windows Server 2003, I get the following error:
Error 1069: The service did not start due to a logon failure.
I applied the suggested fix from this article: http://support.microsoft.com/kb/555989 but problem remains.
There can be many reason for error 1069, antivirus, dependent services, corrupt dll file or anything else.You can look for the virus/worm infection on the system or it can other software installed on the system might be the cause. You can also use sfc /scannow
to repair the corrupt system file. Make sure system is running with latest SP & Patches.Frankly, this post has nothing to do with the directory services & its better suitable for the general forum.
http://social.technet.microsoft.com/Forums/en-US/winservergen/threads
Awinish Vishwakarma — MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.
-
Изменено
Awinish
23 августа 2012 г. 14:29 -
Помечено в качестве ответа
Cicely Feng
29 августа 2012 г. 7:31
-
Изменено
-
-
Помечено в качестве ответа
Cicely Feng
29 августа 2012 г. 7:31
-
Помечено в качестве ответа
-
Hi,
Please also check is there any policy set that only some allowed domain accounts could be used as logon services?
The setting is located: Computer configurationWindows settingssecurity settingsLocal policiesUser rights assignmentLog on as a service, details you can refer to:
Add the Log on as a service right to an account
http://technet.microsoft.com/en-us/library/cc739424(v=ws.10).aspxRegards,
Cicely-
Изменено
Cicely Feng
24 августа 2012 г. 6:37 -
Помечено в качестве ответа
Cicely Feng
29 августа 2012 г. 7:31
-
Изменено
- Remove From My Forums
-
Question
-
Hi All,
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it’s password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it’s original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We’re using SQL2k with SP3a. Thanks!
Error:
An error 1069 — )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
Regards,
Joseph
Answers
-
I was getting the same error since I had changed the password. I found a work around for it to connect to SQL server.
Go to Run—>services.msc—> MSSQLSERVER . On the «log on as» tab right click and check your login information. i suggest delete the password and retype it again. It works !!
-
Proposed as answer by
Wednesday, February 1, 2012 8:03 PM
-
Marked as answer by
Joseph Ollero
Wednesday, July 18, 2012 7:42 AM
-
Proposed as answer by
-
-
Edited by
John Guilbert
Monday, December 12, 2011 10:06 AM -
Proposed as answer by
John Guilbert
Tuesday, January 10, 2012 9:12 AM -
Marked as answer by
Joseph Ollero
Wednesday, July 18, 2012 7:43 AM
-
Edited by
This solution applies to all those services, with which you’re facing Error 1069.
In Windows operating system, there are various services running in the background. The services are important because in their absence, related features will not work as expected. Usually, some services are configured to start when Windows need them. These services have manually Start up type. Sometimes, while starting these services, you may receive some error. In this article, we will talk about one such error and learn how to resolve it. So it is the error 1069: The service did not start due to a logon failure. It may appear with any of the services listed in Services snap-in.
As shown in the screenshot below, I receive this error with WLAN AutoConfig service. Here is the complete message I got in this case:
Windows could not start the WLAN AutoConfig service on Local Computer.
Error 1069: The service did not start due to a logon failure.
So as I said above, this warning message may appear with any of the services. It clearly mentioned that service did not started because of a logon failure. If you’re able to correct that logon failure, you should be able to resolve this issue. Basically, each service in Windows uses an account to operate. Most of times, it is a system or network local account. If a service is configure to run with user created accounts, this issue may occur. To resolve it, you need to reconfigure the service to use default system account or service favourable account.
Here’s how you can fix this problem.
Fix Error 1069: The service did not start due to a logon failure
1. Open Services snap-in by running services.msc command.
2. In Services, right click on the service with which you are getting this issue and select Properties.
3. On the service property sheet, switch to Log On tab. As you’re facing this issue, you might have This account selected with your own user name. All you need to do is to select Local System account here. Click Apply followed by OK.
After this, try to restart the service and it will work without any error now.
If you have any queries, you can check out following video for more information:
Hope this helps!
Related: Error 1079: The Account Specified For This Service Is Different.
READ THESE ARTICLES NEXT
- How to Disable Antimalware Service Executable in Windows 11
- The Windows Installer Service could not be accessed in Windows 11
- How to delete services in Windows 11/10
- Fix: Error 1058 The service cannot be started in Windows 10
- The Delayed Auto-start Flag Could Not Be Set
- Error 1061: The Service Cannot Accept Control Messages At This Time
- FIX: Windows Wireless Service Is Not Running On This Computer
- Update Orchestrator Service In Windows 10
- FIX: Windows Defender Antivirus Inspection Service On Local Computer Started And Then Stopped
- FIX: Windows Couldn’t Connect To The ProfSvc Service
by Milan Stanojevic
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more
Updated on March 14, 2022
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
- Download DriverFix (verified download file).
- Click Start Scan to find all problematic drivers.
- Click Update Drivers to get new versions and avoid system malfunctionings.
- DriverFix has been downloaded by 0 readers this month.
When you are plagued by the service did not start due to a logon failure error, especially when you restart your Windows server, the problem is usually attributed to a password change for the profile being used by the SQL Server Agent.
However, sometimes the password may have remained the same, and you’re sure you didn’t make any changes whatsoever.
In addition to this, you’re tired of changing the login used and returning it back to its original domain login all the time, which you cannot keep doing every time something goes wrong.
The above may happen due to:
- Password change on the account with which the service is configured to log on
- Password data is damaged (in the registry)
- The right to log on as a service has been revoked for the specified user account
No need to worry about this as we have just the right solutions to resolve the issues that bring up the service did not start due to a logon failure error, check out the solutions below.
How to fix the service did not start due to a logon failure error
- Configure the service to use the built-in system account
- Change the password for the specified user account to match the current password for the same user
- Restore user’s right to log on as a service
1. Configure the service to use the built-in system account
If the service did not start due to a login failure, configure it to start up with a built-in system account by doing the following:
- Press Windows key + R to open the Run elevated command line.
- Type services.msc and press Enter.
- Locate the Application Identity service, right-click on it, and open Properties.
- Click Log On tab.
- Click Local System Account
- Do not select the Allow service to interact with the desktop check box
- Click Apply
- Click General tab
- Click Start to restart the service
- Close the Services tool.
Note: When you try to open the properties of service by using the Services tool in Control Panel, the computer may stop responding, and get the error message that says: The RPC Server is unavailable.
Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
This may occur if the RPC service isn’t started due to login failure with the service, or a dependency service because some have to wait until their dependency services start before they themselves start.
2. Change the password for the specified user account to match the current password for the same user
Here’s how to configure the password for the specified user account to match the current password for that user:
- Navigate to Services again by following the steps from the previous solution.
- In the search box, type Administrative Tools and click on it
- Click Services
- Right-click the service you want and select Properties
- Click Log On tab
- Change the password then click Apply
- Click the General tab
- Click Start to restart the service
- Click OK and close the Services tool
- Event ID 7000: How to fix this Service control manager error
- Projector Not Turning On: Why & How to Fix [Epson, Dr.J]
- LogonUI.exe System Application Error: How to Fix & Main Cause
- Fix: You Have Been Denied Permission to Access This Folder
3. Restore user’s right to log on as a service
If the right to log on as a service is revoked for the user account, restore it on a domain controller or a member server (standalone) depending on your situation.
How to restore user’s right on a Domain Controller
Here’s how to do this if the user is in an Active Directory domain:
- Right-click Start
- Click Control Panel
- Type Administrative tools and select it
- Click Active Directory Users and Computers
- Right-click the organization unit in which the user right to log on as a service was granted (Domain Controllers organizational unit by default)
- Right-click the container you want then click Properties
- Go to Group Policy tab
- Click Default Domain Controllers Policy
- Click Edit to start Group Policy Manager
- Expand Computer Configuration
- Expand Windows Settings
- Expand Security Settings.
- Expand Local Policies
- Click User Rights Assignment
- Right-click Log on as a service from the right pane
- Click Add User or Group.
- Type the name that you want to add to the policy in the User and Group Names box
- Click OK.
- Exit Group Policy Manager
- Close Group Policy properties,
- Exit the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in
How to restore user’s right on a Member Server (stand-alone)
Here’s how to do this if a user is a member of a standalone member server:
- Start Local Security Settings MMC snap-in.
- Expand Local Policies.
- Click the User Rights Assignment.
- Right-click Log on as a service from the right pane.
- ClickAdd User or Group.
- Type the name that you want to add to the policy in the User and Group Names box.
- Click OK.
- Quit the Local Security Settings MMC snap-in.
Did any of the solutions above help fix the service that did not start due to a logon failure error? Let us know your experience in the comments section below.
