How do I allow WingHUD in my antivirus?

Windows Security: Firewall & network protection → Allow an app through firewall → Change settings → Allow another app… → choose WingHUD.exe (usually C:\Users\<you>\AppData\Local\Programs\WingHUD\WingHUD.exe ) and tick Private and Public. Kaspersky: Settings → Security settings → Firewall → Configure applications → find WingHUD and set its network access to Allow (or move it to Trusted).

How do I allow WingHUD in ESET, Bitdefender or McAfee?

ESET: Setup → Network protection → Firewall → Configure → Rules → add a rule allowing WingHUD.exe, or choose Allow when ESET asks about WingHUD. Bitdefender: Protection → Firewall → Settings → Rules → Add → choose WingHUD.exe and allow it.

Connection and startup

Applies to WingHUD 3.2 · Updated October 8, 2026 · English only

WingHUD doesn't open, or says it can't reach WingHUD#

WingHUD needs to reach its servers to sign you in and answer questions. When something on your PC blocks it, the Hub shows Can't reach WingHUD at the top, with the server it couldn't reach and why (timed out, refused, blocked, certificate not trusted). It keeps retrying on its own and the message goes away as soon as a connection gets through - you can also press Retry.

The usual cause is an antivirus or security suite with its own firewall. Windows' own firewall almost never blocks WingHUD: it only makes ordinary secure (HTTPS) connections out, and never needs incoming connections from the internet. Allow WingHUD in your security software (next section), then open WingHUD again or press Retry.

If nothing appears at all: WingHUD may already be running in the tray - right-click its icon by the clock and choose "Open WingHUD Hub". If it isn't running and opening it again does nothing, your security software is probably stopping it before it can start - check its quarantine and blocked-apps list.

Allow WingHUD in your security software#

Windows Security: Firewall & network protection → Allow an app through firewall → Change settings → Allow another app… → choose WingHUD.exe (usually C:\Users\<you>\AppData\Local\Programs\WingHUD\WingHUD.exe) and tick Private and Public.
Kaspersky: Settings → Security settings → Firewall → Configure applications → find WingHUD and set its network access to Allow (or move it to Trusted).
Norton: Settings → Firewall → Program Control → find WingHUD (or Add it) and set it to Allow.
Avast / AVG: Settings → Protection → Firewall → Application rules → find WingHUD and allow it. If WingHUD was held for analysis when you first opened it, allow it when the prompt appears.

More security suites#

ESET: Setup → Network protection → Firewall → Configure → Rules → add a rule allowing WingHUD.exe, or choose Allow when ESET asks about WingHUD.
Bitdefender: Protection → Firewall → Settings → Rules → Add → choose WingHUD.exe and allow it.
McAfee: My protection → Firewall → Internet connections for programs → Add → choose WingHUD.exe and give it full access.

Menu names change between versions of each product; look for "application rules", "program control" or "trusted applications". If your security software quarantined WingHUD, restore it from the quarantine and add it to the exclusions.

What WingHUD connects to#

All of WingHUD's connections are outgoing and encrypted - almost all of them HTTPS on port 443, plus secure WebSockets for voice; Steam sync for Dota 2 reaches Steam's servers the same way the Steam client does. WingHUD never needs incoming connections from the internet. The simplest fix is to allow WingHUD.exe in your security software rather than individual addresses: WingHUD talks to a few services (sign-in and chat, spoken replies and voice input, updates and game art on storage.googleapis.com, Steam for Dota 2 sync, YouTube for the YouTube widget, and winghud.com for these docs), and some of their addresses can change.

If your network only lets you allow addresses, email guy@winghud.com for the current list. The Can't reach WingHUD message also shows the first address that failed.

Continue with Google opens your browser and then hands the sign-in back to WingHUD on your own PC (127.0.0.1, ports 47811-47813). If your security software asks whether WingHUD may accept that local connection, allow it.

Sending startup logs to support#

If WingHUD fails while starting, it saves a short report and sends it automatically the next time you open WingHUD and are signed in - you don't have to do anything. If it keeps failing and never gets that far, the files are in %LOCALAPPDATA%\WingHUD\logs (paste that into File Explorer's address bar): last-launch.json and any crash-….json. Email them to guy@winghud.com with the name of your antivirus or security software. They contain the app version, your Windows version and what WingHUD was doing - no chats, passwords or personal files.