Windows 10 has no built-in DHCP server feature; enable it using Windows Server’s role installation or a third-party tool on Windows 10.
Most people searching for “enable DHCP server in Windows 10” assume the setting lives inside the adapter properties alongside the client configuration. It doesn’t. The Obtain an IP address automatically toggle is client-side only — it tells your PC to ask for an address, not to give one out. If you need a Windows machine to hand out IP leases, you have a few real options: install the DHCP Server role on Windows Server, or run a lightweight third-party server on Windows 10 itself. This article walks through all three routes, their limits, and when each makes sense.
Can You Turn Windows 10 Into a DHCP Server?
Yes, but not through any built-in Windows 10 menu or setting. Microsoft only includes a DHCP server role in Windows Server editions, not Windows 10. The Obtain an IP address automatically option you see in your adapter’s IPv4 properties is strictly a DHCP client setting — it makes your PC request an IP, not serve one to others. Enabling a DHCP server on Windows 10 requires either a third-party application or a Windows Server installation.
The most common shortcut that people try leads nowhere: opening Network and Sharing Center > Change adapter settings and clicking through adapter properties will not reveal a server toggle. That path configures your machine as a client, not as the network’s address authority.
Method 1: Install the DHCP Server Role on Windows Server
The official, fully supported method requires a machine running Windows Server, not Windows 10. Microsoft’s own quickstart guide shows the exact steps to add the server role, authorize it in Active Directory, and create a scope.
After opening Server Manager, go to Manage > Add Roles and Features. Choose Role-based or feature-based installation, select your destination server, check the DHCP Server role, and click Install. Once installed, authorize the server in Active Directory using the DHCP console: right-click the server name and select Authorize, or run Add-DhcpServerInDC -DnsName DHCP1.corp.contoso.com -IPAddress 10.0.0.3 in PowerShell.
After authorization, right-click IPv4 under the server in the DHCP console and choose New Scope. The wizard walks you through naming the scope, setting an IP range, and configuring lease duration. Finish the wizard and choose Yes, I want to activate this scope now — without activation, the server won’t begin handing out addresses.
Method 2: Use a Third-Party DHCP Server on Windows 10
When you don’t have a Windows Server license and need a lightweight DHCP server on your existing Windows 10 machine, a third-party tool is the only built-in alternative. One widely used free option is DHCP Server for Windows from dhcpserver.de. It runs as a single executable, configures itself through a wizard or an INI file, and can operate as a background tray application or Windows service.
After downloading the tool, extract it and run dhcpwizard.exe. The wizard asks you to select the network interface that will serve DHCP traffic — this must be an interface with a static IP address. Choosing a DHCP-configured adapter creates conflicts because the server software and your PC’s own client request collide on the same segment. The tool writes a configuration file automatically, then runs in the system tray (the dp icon) where you can right-click to pause or exit the service.
One critical safety note: before enabling a third-party DHCP server, scan your network for any existing DHCP server (often your router). Two active DHCP servers on the same subnet can assign duplicate or conflicting addresses, which instantly breaks connectivity for all devices. If your router already acts as a DHCP server, you can either disable it or adjust the third-party server’s scope to avoid overlap.
Method 3: Configure Windows 10 as a DHCP Client
If your actual goal is to make your Windows 10 machine receive an IP address from a network’s DHCP server — which is how most home and office connections work — you enable the client setting, not a server. Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active Ethernet adapter, select Properties, double-click Internet Protocol Version 4 (TCP/IPv4), and choose Obtain an IP address automatically with Obtain DNS server address automatically. The your PC shows a valid IP in the adapter’s status window without you having typed one.
This setting is the one documented in KVH’s Windows 10 networking guide and applies to all standard Ethernet connections. It has nothing to do with running a server — and that confusion is the most common mistake people make.
Windows Server vs. Third-Party DHCP Tool: Which One Fits Your Situation?
| Criteria | Windows Server DHCP Role | Third-Party Tool on Windows 10 |
|---|---|---|
| Operating system required | Windows Server (2016, 2019, 2022, etc.) | Windows 10 or 11 |
| Setup complexity | Moderate (add role, authorize, create scope) | Low (run wizard, select interface) |
| Domain / AD dependency | Requires Active Directory authorization | None |
| Lease management | Full GUI and PowerShell support | INI file edits or basic tray controls |
| Scalability / reliability | Enterprise-grade, high availability options | Small network / temporary use |
| Cost | Windows Server license required | Free for personal use |
| Official Microsoft support | Yes | No (third-party software) |
Common Mistakes That Derail a DHCP Setup
Most DHCP problems come from a few predictable pitfalls. First: confusing the client setting with a server toggle — the Obtain an IP address automatically checkbox does not enable server functionality. Second: forgetting to authorize the DHCP server in Active Directory when using the Windows Server role; an un-authorized server won’t start leasing addresses. Third: creating a scope but not activating it during the wizard — the scope must be set to active before the server hands out IPs.
With third-party tools, the biggest mistake is choosing an interface that itself receives DHCP. When the server machine’s own adapter requests a dynamic IP on the same segment it serves, you get address conflicts and erratic behavior. Always set that adapter to a static IP before enabling the DHCP server on it.
Third-Party DHCP Server: What to Watch For
| Element | Details |
|---|---|
| Interface selection | Must have a static IP; conflicts occur with DHCP-assigned adapters |
| Configuration method | Wizard (dhcpwizard.exe) or manual INI file editing |
| Running mode | System tray icon or Windows service for background operation |
| Firewall | May need an exception for UDP ports 67/68 |
| Network caution | Check for existing DHCP server first to avoid conflicts |
Final Checklist: Enabling DHCP Server on Windows 10
Here’s how to pick the right route and avoid frustration:
- Run an existing router? Your router almost certainly has a built-in DHCP server. Log into its admin panel and enable it there — no Windows server needed.
- Need a Windows-based DHCP server in production? Install the DHCP Server role on a Windows Server machine. It’s the only fully supported route and includes features like failover and scope management.
- Need a quick temporary DHCP server on Windows 10? Download a trusted third-party tool like DHCP Server for Windows. Use the wizard, pick a static-IP adapter, and activate the service.
- Never use the adapter’s “Obtain an IP address automatically” as a server toggle. That setting makes your PC a client — it won’t assign addresses to other devices.
- Always activate the scope after creation. An inactive scope does nothing.
- Avoid running two DHCP servers on the same subnet. Disable your router’s DHCP server if you switch to a Windows-based one, or adjust scopes carefully to prevent overlap.
References & Sources
- Microsoft Learn. “Quickstart: Install and Configure DHCP Server” Official Microsoft guide for installing the DHCP Server role on Windows Server, including authorization and scope creation.
- KVH. “Windows 10 DHCP Settings” Documents the client-side DHCP configuration path for Windows 10 adapters.
- dhcpserver.de. “Running the Server” Guide for the third-party DHCP Server for Windows tool, covering interface selection and service mode.
- Atlona Support. “KB01257: How to turn your computer (Windows) into a DHCP server” References the use of a third-party DHCP server utility and a release version around 2.5.2.
