Please look also here for information about start/stop the JobScheduler service on Windows
If you use the Windows services dialog (services.msc) to start the JobScheduler service then please note:
Windows only gives a service 30 seconds to start.
Normally, it is enough time for the JobScheduler to start.
It is possible that the Windows services dialog displays the status paused when the JobScheduler needs more time to start.
Wait some seconds and refresh the Windows services dialog.
In almost all case the JobScheduler gets the status running.
If the JobScheduler service still paused then please look into the ./logs/scheduler.log to find a reason.
The most common reason is that the JobScheduler has problems to get the database connection.