| Previous | Next |
| ERROR_ENCRYPTION_POLICY_DENIES_OPERATION | SCHED_E_SERVICE_NOT_LOCALSYSTEM |
ERROR_NO_BROWSER_SERVERS_FOUND
The list of servers for this workgroup is not currently available
ERROR_NO_BROWSER_SERVERS_FOUND is Win32 error 6118 (0x17E6) and belongs to legacy Computer Browser server-list discovery. The system description identifies the immediate condition but does not identify the caller, object, policy, device, service instance, or transition that produced it.
Interpret this result at the API boundary that returned it. Capture it before logging, cleanup, or another Windows call can replace the thread-local last-error value. Compare the recorded inputs with the documented precondition for legacy Computer Browser server-list discovery rather than starting with a broad system repair.
Where the result appears
- This result can surface during enumerating servers in a workgroup or legacy Windows domain.
- This result can surface during applications using old browse-list APIs.
- It can surface during mixed networks that still depend on NetBIOS broadcasts.
- It can surface during a subnet without an available master browser.
Likely causes
- no browser server supplied a current list for the workgroup.
- the Computer Browser mechanism is absent on modern Windows.
- broadcast, NetBIOS over TCP/IP, firewall, or subnet boundaries prevent discovery.
- the master-browser election or browse list is stale.
Diagnostic sequence
Diagnosis of it starts with the exact request type: read, write, create, transition, validation, cancellation, or administrative action. Identify the object generation and subsystem owner, then decide whether the failure happened before side effects, during a partial transition, or after completion. This ordering matters in legacy Computer Browser server-list discovery because a blind retry can hide stale state or repeat a non-idempotent change.
- record workgroup or domain name and client subnet.
- record API used to enumerate servers.
- record NetBIOS over TCP/IP and SMB configuration.
- record packet capture for browser elections and announcements.
- record whether DNS, Active Directory, or explicit server names work.
Correlate it with the owning component’s operational log, the Windows System log, and any subsystem trace. Telemetry for it should preserve native identifiers such as a path or file ID, handle generation, node or peer identity, policy ID, object version, offset and length, or transaction token. Retain decimal 6118, hexadecimal 0x17E6, and the producing API even when a localized message is also shown.
State boundary to prove
The decisive boundary for it is whether no browser server supplied a current list for the workgroup. Prove or disprove that proposition using workgroup or domain name and client subnet together with API used to enumerate servers. When observations for it disagree, preserve both and inspect the transition between them instead of choosing the more convenient value.
A focused validation for it should recreate the relevant part of this situation: an old inventory tool shows an empty workgroup after SMB1-era browser functionality is removed. Querying directory services replaces unreliable broadcast enumeration. The negative case should keep the responsible condition unchanged and confirm error 6118; the recovery case should change only that condition and verify a successful result without an unrecorded side effect.
Handling, retry, and recovery
Do not build new discovery logic around the Computer Browser service. Use DNS, Active Directory, explicit configuration, or a supported service-discovery mechanism; troubleshoot browse lists only for unavoidable legacy dependencies.
Retry it only after evidence shows a change in legacy Computer Browser server-list discovery. Initialization, asynchronous completion, recall, or service readiness can justify bounded backoff; malformed metadata, invalid identifiers, policy rejection, unsupported versions, and integrity failures require correction. Before repeating a write or configuration operation after it, query completion state explicitly.
What to log for support and telemetry
- log decimal 6118, hexadecimal
0x17E6, and the producing API. - log the target object and observed legacy Computer Browser server-list discovery state.
- log caller identity, process and thread IDs, machine or node identity, and UTC time.
- log attempt number, elapsed time, previous result, and any partial side effect.
- retain the first lower-level or component-specific error before Win32 translation.
Difference from nearby codes
The code says the legacy browse list is unavailable, not that every server is offline or unreachable by name.
Practical example
An old inventory tool shows an empty workgroup after SMB1-era browser functionality is removed.
Developer and administrator guidance
Code that handles it should keep its Win32 domain visible across exceptions, RPC responses, and JSON or REST wrappers. Administrators should verify the subsystem evidence before changing policy, deleting state, forcing failover, or replacing storage. Recovery is demonstrated only when a test observes 6118, changes the responsible condition, and confirms that the same operation succeeds without hidden data loss.
References
- Microsoft: System Error Codes (6000–8199) — reference for error 6118.
- Microsoft: Computer Browser service — reference for error 6118.
- Microsoft: Network discovery troubleshooting — reference for error 6118.
Looking for a different code? Search another status or error code.