Browser Election Failed: Fixing 0XC000021C Fast

Yeah, that error is a pain — especially when you're mid-troubleshooting and the network list just goes blank.

Here's the deal: 0XC000021C means your server couldn't find any browser servers on the network. The Computer Browser service (yes, the ancient one from Windows 95 days) failed an election or can't see a master browser. Happens a lot on isolated subnets or after a network split. Had a client last month whose entire print server stopped showing up in Network — same error.

The Fast Fix: Force the Browser

Run this from an elevated PowerShell or Command Prompt. It'll stop the browser service, tweak the registry to make your server announce itself as a browser, then restart everything.

net stop browser
sc config browser start= disabled
reg add "HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v MaintainServerList /t REG_SZ /d Yes /f
reg add "HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters" /v IsDomainMaster /t REG_SZ /d True /f
sc config browser start= demand
net start browser

If the browser service won't start, check that the Server service is running (net start server) and that TCP/IP NetBIOS Helper is enabled (sc start lmhosts). After that, run net view — you should see other machines pop up within a couple minutes. If not, give it a minute and run nbtstat -n to verify your server is broadcasting as a browser.

Why This Works

The Computer Browser service uses elections to pick which machine holds the master list. When your server can't find a master browser (or loses the election), you get 0XC000021C. By setting MaintainServerList to Yes and IsDomainMaster to True, you're forcing your server to become the master browser — it's like saying "I'm the boss here." But don't leave IsDomainMaster on True permanently — it's a hack. I only do this to force an election, then set it back to False after the network stabilizes. Otherwise you'll have multiple servers fighting for control.

When the Fix Doesn't Work

Sometimes the browser service is just dead. On Windows Server 2022 or 2019, the service might fail to start due to dependencies. Check these:

• NetBIOS over TCP/IP disabled: Go to network adapter properties → IPv4 → Advanced → WINS tab → enable NetBIOS over TCP/IP. I've seen this disabled by default on newer builds.
• Firewall blocking UDP 137-138 and TCP 139, 445: Windows Firewall usually allows this, but third-party ones (looking at you, Sophos) often block NetBIOS. Open those ports between machines.
• SMB1 disabled: Yes, the browser service depends on SMB1 in old environments. If you've disabled SMB1 (good for security), the browser service won't work. Alternative: enable SMB1 only for the browser role via Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol — but that's a security risk. Better to use WS-Discovery for modern network discovery.

If the service starts but you still get the error, run nbtstat -r to purge and reload the NetBIOS name cache. Then wait 5 minutes. Browser elections take time.

Preventing This Long-Term

The real solution is to phase out the old browser protocol. Microsoft replaced it with Function Discovery (WS-Discovery) back in Windows 10/Server 2016. But small businesses running legacy apps (like old accounting software that needs NetBIOS names) are stuck with it.

Here's what I do for clients:

1. Set one machine as the permanent master browser on each subnet. Usually the domain controller or a file server. Set IsDomainMaster to True only on that machine, False on all others. Keeps elections quiet.
2. Check that all machines are in the same subnet or have WINS server configured. Cross-subnet browsing needs a WINS server. Without one, elections fail.
3. Use net config server /autodisconnect:-1 to prevent session drops that confuse the browser list.
4. Schedule a weekly restart of the Browser service via Task Scheduler. net stop browser && net start browser. Keeps it fresh.

If you're on a client network that's all Windows 10/11 and Server 2022, consider disabling the browser service entirely and relying on WS-Discovery. But test first — some old printers and NAS boxes still need NetBIOS.

One last thing: never run two servers with IsDomainMaster=True on the same broadcast domain. They'll fight, constantly re-electing, and you'll get that error bouncing back and forth. I spent an afternoon at a client's office once because their DC and a file server both had it set to True. Sad time.