Mihomo Party Windows 11 Install And Setup Guide For Beginners

Mihomo Party is a Windows desktop client built around the Mihomo proxy kernel. On Windows 11, it can manage subscription profiles, proxy groups, system proxy settings, connection logs, DNS options, and TUN mode from one interface. The installation itself is usually quick, but the first launch can be confusing because the client, the Mihomo core, the subscription provider, and Windows network settings all perform different jobs.

This guide explains a practical first-time setup: how to choose the correct installer, complete the installation, import a subscription, select a usable proxy, enable the appropriate traffic mode, and verify that applications are actually using Mihomo Party. It also covers common Windows 11 issues such as SmartScreen warnings, missing permissions, occupied ports, failed profile updates, and TUN mode not starting.

Understand the Components Before Installing

A beginner can easily treat Mihomo Party as a single all-in-one proxy service, but several independent components are involved. The graphical client is the application window you operate. The Mihomo core is the process that opens local listening ports, resolves domains, matches routing rules, and connects to the selected proxy node. Your subscription service supplies configuration data, while Windows 11 provides system proxy controls, firewall rules, and permission management.

This separation is useful when troubleshooting. If Mihomo Party opens but no proxy group appears, the problem is probably with the imported configuration or subscription. If the profile loads but no traffic is visible, the system proxy or TUN mode may not be enabled. If the client displays a port error, another application may already be using the configured port. Reinstalling the program does not solve every problem because the failure may be outside the program files.

Component Main responsibility Typical first-use problem
Mihomo Party Provides the Windows interface and controls profiles, modes, logs, and permissions. The client is running, but the system proxy switch is still disabled.
Mihomo core Handles local ports, DNS, proxy connections, rules, and traffic processing. The core cannot start because of invalid YAML, a missing component, or a port conflict.
Subscription provider Returns nodes, proxy groups, rules, and other configuration data. The URL has expired, reached a traffic limit, or returns an unsupported format.
Windows 11 Controls application permissions, firewall access, and the operating system proxy. Another proxy application or security tool overrides the expected network path.

Mihomo configurations generally use YAML and may contain sections such as proxies, proxy-groups, rules, dns, and proxy-providers. A subscription may generate these sections automatically. Do not assume that every Clash configuration supports every Mihomo feature. A profile designed for another core may import successfully while still producing unsupported options or incomplete behavior.

Choose and Download the Windows Installer

Start from a trusted distribution source and select the current Windows build intended for your computer. Most Windows 11 systems use a 64-bit Intel or AMD processor, so an x64 installer is normally the correct choice. Windows devices using ARM processors require an ARM64-compatible build if one is provided. The file extension also matters: an installer package and a portable archive have different setup procedures.

Before opening the downloaded file, check its filename, file size, and digital signature when available. Avoid repacked installers that add unrelated utilities, browser extensions, or “activation” tools. Mihomo Party should not require you to enter a license key to enable ordinary local proxy functions. If a download page offers several similarly named files, compare the architecture and package type rather than choosing the largest file automatically.

Windows 11 Mihomo kernel x64 or ARM64

Windows Defender SmartScreen may display a warning for a newly published or less frequently downloaded application. A warning does not prove that the installer is malicious, but it is a reason to verify the source and signature before continuing. Do not bypass every warning without checking the file. If the publisher information is missing, the checksum differs from the value published by the distributor, or the package contains unexpected executables, delete it and obtain a clean copy instead.

If you already have another Clash-compatible client installed, do not run both clients with the same local ports. Two clients may compete for the system proxy switch, controller port, TUN adapter, or profile files. You can keep the old client installed during migration, but close it completely before starting Mihomo Party and disable its automatic startup temporarily.

Install Mihomo Party on Windows 11

After downloading the installer, close other proxy clients and save any unsaved work. Double-click the package and follow the installation wizard. The exact wording can differ between releases, but the important choices are the installation directory, whether a Start Menu shortcut is created, and whether the application should start with Windows. Automatic startup is convenient after the configuration is confirmed, but it is better to postpone it if you are still testing ports or comparing clients.

When Windows requests administrator permission, confirm that the application came from the source you intended to use. Administrator access may be required for system integration, service installation, or TUN mode. If the installer is blocked, right-click it, open Properties, and check whether Windows has marked the file as downloaded from another computer. Only remove an unblock flag after verifying the installer’s origin. Do not disable Windows security protection globally just to complete a proxy client installation.

Launch Mihomo Party after installation and allow it to finish its first-run initialization. The main window may initially show no profile, no proxy group, or an inactive core. That is normal until you import configuration data. Locate the application’s profile or configuration area and note the displayed local ports. Common values include an HTTP port, a SOCKS port, or a mixed port, but the exact defaults vary by build and may change after importing a profile.

A mixed port can accept both HTTP and SOCKS5 connections through one local port, which is useful for general desktop testing. It does not mean that every application will automatically use the port. Applications must either follow the Windows system proxy, be configured manually, or have their traffic captured by TUN mode. Keep this distinction in mind when a browser works but a terminal or game does not.

mixed-port: 7890
allow-lan: false
mode: rule
log-level: info

The example above is only a structural illustration, not a complete profile. Do not replace a subscription-generated configuration with this short snippet. In particular, it contains no proxy nodes, proxy groups, DNS settings, or routing rules and therefore cannot provide a complete browsing setup.

Import a Subscription or YAML Profile

Open the profile management page in Mihomo Party and choose the option for adding a remote subscription or importing a local configuration. For a subscription, paste the URL supplied by your provider and assign a clear local name, such as “Home subscription” or “Travel profile.” The local name is only a label inside the client; it is not a replacement for the actual subscription URL.

For a local file, select the complete YAML file rather than copying only the proxy list. A working configuration normally connects nodes, proxy groups, and rules together. The proxy-groups section may refer to proxy names under proxies, while the rules section may refer to group names. If you import only one section, the profile may load with empty groups or fail validation.

Check the Subscription Input

Subscription URLs are sensitive credentials. Anyone who obtains the URL may be able to consume traffic quota or retrieve your configuration, depending on the provider. Do not publish the URL in screenshots, support forums, public issue reports, or browser history shared with another person. If the provider supports resetting or rotating the URL, use that option after accidental disclosure.

After saving the profile, start an update and wait for the client to report the result. A successful HTTP request does not always mean that the returned content is a valid Mihomo configuration. The response might be an HTML error page, a quota notice, a login page, or an encoded format that requires a conversion option. Check whether the client shows actual proxy names and proxy groups after the update.

If the profile loads but some nodes are missing, compare the provider’s expected format with the core used by Mihomo Party. A provider may return a configuration intended for a different client or core. Also check whether the subscription has expired, whether the account has reached its traffic limit, and whether Windows Firewall or security software is blocking the update request.

Select a Proxy and Enable the Correct Mode

Once the profile is active, open the proxy or group view and select a node or policy group. Many configurations contain groups such as automatic selection, regional selection, streaming, or direct connection. The group name and available choices come from the profile, so the labels will differ between providers. If a group is set to automatic testing, let the latency check finish before judging the result. A low latency value measures the test endpoint and does not guarantee that every website or service will work through that node.

For a first test, choose a known working node manually or select the provider’s recommended group. Avoid changing several settings at once. If you switch the node, DNS mode, TUN mode, and rule mode simultaneously, it becomes difficult to identify which change affected the result.

Mode What it affects Good first use Important limitation
Rule Routes traffic according to the profile’s ordered rules. Normal daily browsing and service-specific routing. Incorrect or outdated rules can send traffic directly or to the wrong group.
Global Sends matching application traffic through one selected proxy choice. Testing whether a selected node works independently of rule matching. It may route destinations that should remain direct through the proxy.
Direct Bypasses proxy routing for ordinary connections. Confirming that the underlying Windows network works without Mihomo. It is not a proxy test and may expose your normal network path.

Enable the Windows system proxy only after a profile and proxy choice are ready. This setting affects applications that respect the Windows proxy configuration. Many browsers, HTTP tools, and desktop applications do so, but command-line programs, games, services, and applications with their own network stack may ignore it.

Use TUN mode only when you need broader traffic interception. TUN creates a virtual network interface and requires additional permissions and compatible DNS or routing behavior. It can capture applications that do not read the system proxy, but it may also affect local services, virtual machines, corporate VPN software, network printers, and other special routes. Begin with system proxy mode for basic browsing, then add TUN after the simpler path is verified.

Perform a Hands-On First Connection Test

Use the following sequence rather than enabling every feature immediately. This gives you a clear baseline and makes later troubleshooting easier.

  1. Close other proxy clients, VPN applications, and network acceleration tools that may control the same system settings.
  2. Open Mihomo Party and confirm that the intended profile is selected and that the Mihomo core is running.
  3. Choose one known working proxy node or a stable proxy group.
  4. Set the operating mode to Rule unless the provider specifically recommends another mode.
  5. Enable the Windows system proxy switch in Mihomo Party.
  6. Open a new private browser window and visit a service that shows the public network address or region.
  7. Open the client’s connection log and confirm that the browser request appears with a matched rule and selected policy.
  8. Test a second domain that uses a different service, because one successful page does not prove that all routes work.

The connection log is more useful than a general “connected” label. Look for the requested domain, destination address, rule or rule provider that matched, the selected proxy group, and whether the connection was accepted or rejected. If the page loads but no corresponding connection appears in Mihomo Party, that browser request may be using a separate extension, a built-in secure proxy, cached content, or another running client.

After the browser test succeeds, test a terminal separately. PowerShell and command-line tools often do not inherit the same proxy behavior as a browser. You can inspect the Windows environment for proxy variables and configure a tool-specific proxy when required. For example, an HTTP-aware tool may need an explicit local HTTP proxy, while a SOCKS-capable tool may need the local SOCKS port. Do not use an HTTP port as a SOCKS5 endpoint or assume that every tool supports both protocols.

netstat -ano | findstr :7890

The command above checks whether a process is listening on port 7890. Replace the port with the actual mixed, HTTP, or SOCKS port displayed by Mihomo Party. If a process is listening but the client cannot use the port, compare the process ID with the application that owns it. A different proxy program may have claimed the port first.

Configure TUN Mode and Windows Permissions

TUN mode is not required for every Windows 11 installation. System proxy mode is usually easier to understand because it changes the operating system proxy destination and affects applications that honor that setting. TUN mode works at a lower network level by creating a virtual interface, allowing the core to process more traffic from applications that ignore ordinary HTTP proxy settings.

Before enabling TUN, make sure the Mihomo core is running and that the selected profile includes compatible DNS and routing settings. Approve the administrator request when prompted. If the TUN adapter cannot be created, restart Mihomo Party with the required permissions, check whether another VPN has installed a conflicting virtual adapter, and review the runtime log for a precise error.

Use TUN carefully on managed networks. Corporate VPN clients, endpoint security software, Hyper-V virtual switches, WSL networking, and virtualization tools may depend on their own routes. A TUN interface can change route priority or DNS behavior and may cause internal company domains or local devices to stop responding. If this happens, disable TUN temporarily and return to system proxy mode while you identify the conflicting route.

Do not enable allow-lan merely because a local network option is visible. When enabled, the core may accept proxy connections from other devices depending on the bind address and firewall rules. For a personal Windows 11 computer, keeping LAN access disabled is the safer default. If LAN sharing is genuinely required, restrict the bind address, create a narrow firewall rule, and use authentication where supported.

Fix Common First-Launch Problems

The installer does not open

Confirm that the file matches your processor architecture and was downloaded completely. Check Windows Security protection history, file properties, and the installer signature. If the file is blocked, obtain a fresh copy from the trusted download source rather than downloading random “fixed” versions from an unofficial mirror. A damaged installer can also fail silently when launched from a temporary folder, so move a verified copy to a normal local directory and try again.

The subscription update fails

First test whether Windows has normal internet access without Mihomo Party. Then verify the URL, account status, traffic quota, expiration time, and required conversion parameters. A provider may limit the number of updates or reject requests from an unusual network. If the response is successful but the client reports invalid YAML, inspect the returned content type and profile format. An HTML error response should not be imported as a configuration.

The core will not start

Read the startup log instead of guessing. Invalid indentation, duplicated keys, unsupported fields, missing proxy-group references, and an occupied local port are common causes. Temporarily switch to a minimal known-valid profile if one is available, then reintroduce custom settings gradually. Do not delete the entire application data directory before exporting your subscription URL and local customizations.

The system proxy has no effect

Check that the Windows system proxy switch is enabled inside Mihomo Party and that the displayed address and port point to the active core. Open Windows 11 proxy settings and look for a conflicting manual proxy or setup script. Close other clients and browser proxy extensions, then restart the browser so it reads the current settings. If only one application fails, that application may deliberately ignore system proxy settings and may require TUN or its own proxy configuration.

TUN mode fails or breaks local networking

Check administrator permissions, virtual adapter status, firewall rules, and conflicts with VPN software. Disable TUN and confirm whether system proxy mode works. If ordinary browsing succeeds without TUN, the subscription and core are probably functional; focus on the Windows route, DNS, or adapter conflict. Re-enable TUN only after removing the conflicting VPN or adjusting the relevant exclusions.

Secure and Maintain the Setup

Once Mihomo Party works, record which profile is active, which mode is enabled, and which local ports are in use. This small amount of documentation prevents confusion when Windows updates, another client, or a new subscription changes the environment. Keep a backup of manually maintained YAML files and custom rule providers, but do not store subscription URLs in public cloud notes or screenshots.

Update the client and Mihomo core through trusted release channels. A newer core may add protocol support or change configuration behavior, while a newer GUI may change permission or TUN integration. After an update, test the profile, system proxy, DNS resolution, and TUN mode separately. If a new release causes problems, preserve the error log and revert only after confirming that the previous version is compatible with your configuration.

Use the least powerful mode that meets your needs. System proxy mode is often enough for browsers and standard desktop applications. TUN mode is useful for applications that ignore system proxy settings, but it deserves more careful testing. Keep allow-lan disabled unless you intentionally share the proxy with another device, and review the connection log periodically for unexpected applications or direct routes.

With this order, Mihomo Party on Windows 11 becomes easier to manage. The client controls the interface, Mihomo performs the routing, the subscription supplies the data, and Windows determines which applications use the local proxy. Separating those responsibilities makes both first-time setup and later troubleshooting much more predictable.

Download Clash