Windows Service Error 1069, "The service did not start due to a logon failure"
Error 1069 means the account the service is set to log on with could not sign in. The password is usually wrong, changed, or expired, or the account lost the right to log on as a service.
The fix, in order
In Services, double-click the service and open the Log On tab. Check which account is selected.
If it uses "This account", retype the password in both password boxes and click Apply. A password changed elsewhere, or typed with a mistake, is the most common cause.
Check that the account is not locked out or expired, and that its password has not expired. A domain password change breaks every service that uses that account until the new password is entered here.
Confirm the account has the "Log on as a service" right. Open the Local Security Policy (secpol.msc), go to Local Policies, User Rights Assignment, and check that the account is listed under "Log on as a service". Add it if it is missing.
If the service can run as a built-in account, switch the Log On tab to "Local System account" and try starting it. If it starts, the problem is with the custom account, not the service.
Check the Security log in Event Viewer for logon failure entries at the same time. They name the account and the reason the logon was refused.
If it still happens
If the service keeps failing after the password is corrected, check whether a Group Policy is removing the "Log on as a service" right at each refresh. If so, the policy needs to grant the right to that account.
Common questions
Why does a service need a password? Services that run under a user account sign in with that account at startup. If the password changes and the service still has the old one, the logon fails and the service cannot start.
What is the 'Log on as a service' right? It is a Windows permission that allows an account to run as a service. Without it, the account cannot log on in the service context even with the correct password.