Error Could not start the DHCP Client service on Local Computer. Error 5: Access is denied.typically pops up after you start your computer, or when you try to start the DHCP service.
This problem may occur after an upgrade from Windows 2003 to 2008, or after you’ve changed permissions in the registry. The error may also popup after your pc has been infected by malware.
In most cases, this error can easily be solved by granting extra permissions in the registry.
Fix Error 5: Access is denied. in Command Prompt
To make the permission changes in the registry, do the following:
- Click Start, click Run, type regedit and click OK
- Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp
- Right click the key DHCP and click Permissions. Click Add, type network service and click OK
- Select NETWORKSERVICE and check the Full control box to grant NETWORKSERVICE full control on the DHCP key.
- Click OK to apply the changes and to close the window
Do the same for the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TcpIp:
- Click Start, click Run, type regedit and click OK
- Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TcpIp
- Right click the key TcpIp and click Permissions. Click Add, type network service and click OK
- Select NETWORKSERVICE and check the Full control box to grant NETWORKSERVICE full control on the TcpIp key.
- Click OK to apply the changes and to close the window
All permissions are now set up. To verify the problem is fixed, do the following:
To start the service, click Start, click Run, type services.msc and click OK
Right click DHCP client and click Start
Alternatively, you could click Start, click Run, type net start dhcp and click OK
The DHCP client service should now start.
Fix Error 5: Access is denied. with Powershell
- Open a Powershell window as admin
- Type the following command to add the Local Service to the administrators group:
NET LOCALGROUP administrators “NT Authority\Local Service” /add - Reset the Winsock Catalog
netsh winsock reset catalog - Reboot your pc
The DHCP Client service error 5 should now be resolved.
I have the problem described. Several Windows 2003 Servers use static IPs 192.168.x.x, and report this error to event log. I followed the procedure, but it did not help. Anybody knows some other solutions?
Had exactly this problem, and your solution fixed it for me.
Thanks!
Just wanted to add to this thread as I had the exact same symptoms and tried all of these suggestions to no avail. As it turned out, I needed to run a CHKDSK /F as there were errors and corrupt sectors on the drive that were obviously affecting registry hives. After much searching and manipulating of registry permissions, GPO, etc, the CHKDSK /F resolved my issues instantly.
Just wanted to share this in case it too is the root cause of someone’s woes.
1.Click Start, click Run, type regedit and click OK
2.Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Parameters
3.Right click the key DHCP and click Permissions. Click Add, type network service and click OK
4.Select NETWORKSERVICE and check the Full control box to grant NETWORKSERVICE full control on the DHCP key.
5.Click OK to apply the changes and to close the window.
6. Restart the DHCP Client service.
That´s all.
You are a GOD! I spent way too long on this problem (started right after uninstalling McAfee). They told me to call my ISP.
THANKS!
No joy from the above. Failed step #2. Copy permissions from DHCP and TCPIP to their children (right-click, choose Permissions, click on the Advanced button at lower-right, check the box “Replace all child object permissions with inheritable permissions from this object” and confirm that choice). Still no joy. Failed step #3. Add new permission for COMPUTERNAME\Users (replace COMPUTERNAME with your own). Give Full Control to Users. Correct step #4. Do step 3. Then do step 2. So the “Users” id will have full control, and it will be copied to all the children of DHCP and TCPIP, to be identical… Read more »
Awesome answer. cured my tale of woe!
Thanks, It worked!
Thanks a thousand ton man, that worked.
YES! This is the missing step!
You are awesome! This worked nothing else did!
thank you so so much rusty shack. i tried everything for months at end and finally your solution worked. all my keys were ok except i didnt propagate the permissions through inheritance.
I had been experiencing problems connecting to my wired and wireless networks, later that I figured out that it was the autoIP configuration problem ( I had sticked to static IP), it was the DHCP problem. Your solution really worked for me, starting the DHCP service. Now I am to check whether the internet would start up using AutoIP configuration.
Cheers.
also need to add “nt service\dhcp” with full permissions to dhcp and tcpip keys
You are awesome
That helped me in Windows 10
Your solution fixed it for me.
I did all those things, but I still have that error. :s Any ideas?
I see this is a fairly old post but it’s just solved this issue for me today so thanks for posting this info…
Thank you so much for posting. Got it to work I had the same issue, and your approach solved it for me.
That fix was amazing !! Every single one of the network interfaces mysteriously had DHCP disabled, and it was impossible to start the service. Thank you soooo much John !!!!
Thank you John for this brilliant fix !!
thanks it worked.