When a slave is attempted to be started via the Jenkins master, the slave fails to come back up, and hangs at the 'Starting slave' stage.

When logging into the Windows slaves, trying to start the WIndows service manually fails with a "Logon failed' message. When I manually change the service's password, I can start the service via the master. I've verified repeatedly the right password was entered in the masters configuration via the 'Let Jenkins control this Windows slave as a Windows service'. It seems though that when Jenkins is setting up and deploying the Windows service, it's providing an incorrect password.

I couldn't find any logs related to this.
Using Jenkins 1.450