If during normal loading you can open bind (via the task manager - file - execute) then execute -
net start netlogon
It will not start and the cause of the error must be registered in the logs (although it should be so anyway)
And show the output of commands
sc qc netlogon
sc qc LanmanServer
sc qc LanmanWorkstation
It is about the same as below, copy and change to what you have (if you can not copy from the server)
C: \ Users \ Administrator> sc qc netlogon
[SC] QueryServiceConfig: Success
ServiceName: netlogon
Type: 20 WIN32_SHARE_PROCESS
Start_type: 2 AUTO_START
Bug Management: 1 NORMAL
Binary_name: C: \ Windows \ system32 \ lsass.exe
Startup Group: MS_WindowsRemoteValidation
Tag: 0
Display_Name: Network Login
Dependencies: LanmanWorkstation
: LanmanServer
Service_start_name: LocalSystem
C: \ Users \ Administrator> sc qc LanmanServer
[SC] QueryServiceConfig: Success
ServiceName: LanmanServer
Type: 20 WIN32_SHARE_PROCESS
Start_type: 2 AUTO_START
Bug Management: 1 NORMAL
Binary_name: C: \ Windows \ system32 \ svchost.exe -k netsvcs
Startup Group:
Tag: 0
Display_name: Server
Dependencies: SamSS
: Srv2
Service_start_name: LocalSystem
C: \ Users \ Administrator> sc qc LanmanWorkstation
[SC] QueryServiceConfig: Success
ServiceName: LanmanWorkstation
Type: 20 WIN32_SHARE_PROCESS
Start_type: 2 AUTO_START
Bug Management: 1 NORMAL
Binary_name: C: \ Windows \ System32 \ svchost.exe -k NetworkService
Startup Group: NetworkProvider
Tag: 0
Display_name: Workstation
Dependencies: Bowser
: MRxSmb20
: NSI
Initial Service_Name: NT AUTHORITY \ NetworkService
C: \ Users \ Administrator>