Fix 0X00000700 Netlogon Not Started Error Fast
The network logon service isn't running. This usually happens after a reboot or domain join failure. Here's how to fix it in three steps.
The 30-Second Fix: Restart the Netlogon Service
Open the Run dialog. Press Win + R on your keyboard. Type services.msc and press Enter. The Services window opens.
Scroll down until you see Netlogon. The Status column should say Blank (not Started) and the Startup Type should be Automatic. If it's anything else, double-click it. In the Properties window, set Startup type to Automatic. Click Apply. Then click Start. You'll see the service status change to Running.
After starting it, try your logon again. If the error's gone, you're done. If you see the error again after a reboot, move to the next section.
The 5-Minute Fix: Check Dependencies and Event Logs
Step 1: Check what Netlogon needs
Netlogon depends on two other services: Remote Procedure Call (RPC) and Security Accounts Manager (SAM). If either of those is stopped, Netlogon won't start.
In the Services window, find Remote Procedure Call (RPC). It should be running. Same for Security Accounts Manager. If either is stopped, right-click it and choose Start.
Now try starting Netlogon again. Still failing? Let's check the Event logs.
Step 2: Check Event Viewer for clues
Open Event Viewer: hit Win + R, type eventvwr.msc, press Enter. Go to Windows Logs > System. Click on the header of the Level column to sort by Error. Look for events from source NETLOGON or NETWORK near the time you tried to start the service.
Common errors you'll see: "The Netlogon service failed to start due to the following error: The dependency service or group failed to start." That points back to RPC or SAM. Another one: "The Netlogon service failed to start because the workstation and primary domain controller trust relationship failed." That means a secure channel issue — often fixed with a domain rejoin or resetting the computer account in Active Directory.
If you see an error about the workstation service or TCP/IP NetBIOS Helper missing, then those services need to be started too. They're not direct dependencies, but Netlogon needs them for name resolution.
The 15-Minute Fix: Registry and Domain Rejoin
Step 1: Verify the startup type in Registry
Sometimes Services.msc lies. The registry tells the truth.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetlogonOpen Regedit (Win+R, type regedit, press Enter). Navigate to that path. On the right side, find Start. It should be a DWORD with value 2 (Automatic). If it's 4 (Disabled), double-click it and change it to 2. Click OK. Close Regedit. Restart the Netlogon service.
Step 2: Check the Secure Channel
Open Command Prompt as Administrator. Hit Win + X, then choose Command Prompt (Admin) or Windows Terminal (Admin). Run this command:
nltest /sc_query:YOURDOMAINReplace YOURDOMAIN with your actual domain name. If you see error 0x0 or STATUS_SUCCESS, the secure channel is fine. If you see 0x0 SC_DOMAIN_DISCONNECT or 0x0 NERR_JobNotFound, the trust is broken.
To fix a broken trust, run this:
nltest /sc_change_pwd:YOURDOMAINIf that fails, or if you get access denied, you'll need to reset the computer account from a domain admin account. On the domain controller, open Active Directory Users and Computers. Find the computer object. Right-click it, choose Reset Account. Then on the workstation, run:
netdom resetpwd /s:YOURDC /ud:YOURDOMAIN\ADMIN /pd:*You'll be prompted for the admin password. After that, reboot.
Step 3: Last resort — rejoin the domain
If nothing works, leave the domain and rejoin. This nukes the trust and rebuilds it fresh.
Go to Settings > System > About. Click Rename this PC (Advanced). Under Member of, select Workgroup and type WORKGROUP. You'll need to reboot. After reboot, go back and join your domain again. Make sure you have local admin credentials handy — you'll need them to log in while the machine is in a workgroup.
Once you're back on the domain, reboot again. The Netlogon service should start automatically, and the 0X00000700 error will be gone.
One more thing: if this machine is a domain controller itself — meaning it's running Active Directory — you can't rejoin it. You'd need to promote or demote it using
dcpromoor Server Manager. That's a whole different beast. The 0X00000700 error on a DC almost always means the KDC service isn't running, or the database is corrupt. That's a call to Microsoft Support territory.
Was this solution helpful?