Hello BernAbb,
When these services become available once restarting WID service, usually means that the Logon account used on the service(s) related and dependencies may not be the same. Let's say that one service has a domain account, while the other has a System account. This could represent a vulnerability in the Authorization chain and there for ignored until there is an interactive action to start the service.
The recommendation would be to check the service's Logon accounts in use, and replace using the same account for all the related services.
----------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept as answer--