For the next build of PDF24, can I suggest that when installing, if the service does not start but everything else has installed correctly, exit with code 3010 to require a reboot?
I've found that in some instances the Windows RestartManager service doesn't work, at least in the case of PDF24.
The work around I have to use for deploying via SCCM is to manually install the files with a copy command, and run the printerinstall.exe, and if pdf24.exe -start -install exits with anything other than 0 schedule a restart and re-run pdf24.exe -start -install on the next boot