Basically we have a service where we use a local account as its logon. it has all the proper permissions, and everything is working fine, service starts and runs and all is good. Then one day, after rebooting, the service fails to start. Logs show incorrect password. Our technicians resolve the issue by simply retyping the password into the "Log On" tab from the services.msc. Unfortunately we have not been able to root cause. I suspect that the password that is stored for the service is lost somehow. Does anyone know where the password hash might be stored so we can check it? The only activities that seem to be possibly related are patching with Microsoft security patches, but we have multiple servers running the same service, and we have never seen more than one at a time, and its usually a different one each time when this occurrs.

I believe this to be the same issue as this: [Windows service fails to start with custom user until started once with local user](https://superuser.com/questions/123903/windows-service-fails-to-start-with-custom-user-until-started-once-with-local-us?answertab=active#tab-top) But i was unable to add comments, and its really old.

UPDATE: We have linked this issue to the Logon as Service policy. The account is removed somehow from this setting. Retyping the password in the services console re-adds the account to this policy. We will now want any suggestions on how to root cause why the account is removed. We have enabled "audit policy change" and set to audit for both success and failure.