This issue seems to have cropped up specifically with the 0.11.5 client, and I can confirm that it is also present on Windows 10 if sysprepped. Disabling the service prior to capturing and setting via script to auto very consistently causes the service not to start even when set back to automatic. There might be 1 out of 15 clients that have the service actually start after the scripted reboot.