Clash Verge Rev: Fix Multi-User Windows 10 Bug

Hey guys!

Let's dive into a peculiar problem encountered by a Windows 10 user. This article addresses the issue where the Clash Verge Rev app fails to launch for other users in a multi-user environment if one user has already started it. We will explore the user's description, software version, steps to reproduce, OS details, and relevant logs to provide a comprehensive understanding of the problem.

Problem Description

The user, operating on Windows 10 22H2, has both an administrator and a standard user account. The issue arises when one user launches the Clash Verge Rev application. If they then switch to another user account, attempting to launch the app again results in no response. In essence, the app refuses to start for the second user. The user recalls that a previous Clash application offered an installation option for all users, allowing each to use it independently. They're curious whether this behavior is a bug or a feature that might be implemented in the future.

When you are using Windows 10 in a multi-user setup, the application's behavior can be quite frustrating. Imagine setting up different user accounts for your family or colleagues, each expecting to run the Clash Verge Rev app seamlessly. However, the reality is that only the first user to launch the app gets to use it, while subsequent users are locked out. This is not just an inconvenience; it disrupts workflow and reduces productivity. The ability to have each user independently access and utilize the application is crucial for a smooth and efficient multi-user experience. The user's previous experience with a Clash application that allowed installation for all users highlights the expectation that such functionality should be standard, especially in a multi-user environment. Understanding the root cause of this issue is essential for developers to address it effectively. Is it a matter of configuration, permissions, or an inherent limitation in the application's design? Addressing this problem will significantly enhance the usability and appeal of Clash Verge Rev, making it a more versatile and user-friendly tool for Windows 10 users.

Software Version

The user reports using Clash Verge Rev version v2.4.0.

Steps to Reproduce

1. Log in to User A on a multi-user Windows system.
2. Launch the Clash Verge Rev application.
3. After the app is running, switch to User B.
4. Attempt to launch the Clash Verge Rev application again.
5. Observe that the app does not respond or start.

To reproduce the issue, you need a Windows 10 system with multiple user accounts. First, log in to one of the accounts, say User A, and start the Clash Verge Rev application. Make sure it's running correctly. Next, switch to another user account, User B, without closing the application in User A's session. Now, try to launch the Clash Verge Rev application from User B's account. If the bug is present, you'll notice that the application fails to start. There's no error message, no sign of activity – it simply doesn't launch. This behavior is consistent and easily reproducible, making it straightforward to confirm the issue. This is very important for the developers to reproduce, test and fix. By following these steps, anyone with a similar setup can quickly verify whether they are experiencing the same problem. This helps in gathering more information about the bug and understanding its prevalence across different systems and configurations. It also aids in ensuring that any proposed solutions are thoroughly tested and effective in resolving the issue for all affected users. The clarity and simplicity of these steps are crucial for efficient bug reporting and resolution.

Operating System

• Operating System: Windows
• OS Version: Windows 10 Professional 19045.6216

Knowing the specifics of the operating system and its version is essential for troubleshooting and resolving software issues. In this case, the user is running Windows 10 Professional, version 19045.6216. This information helps developers understand the environment in which the bug is occurring. Different versions of Windows can have variations in their system architecture, security settings, and compatibility layers, which can influence how applications behave. For example, a bug that appears in version 19045.6216 might not be present in an earlier or later version due to underlying system changes or updates. Additionally, the Professional edition of Windows includes features and policies that are not available in other editions, such as Windows 10 Home. These differences can affect how applications interact with the operating system, especially in multi-user scenarios. By pinpointing the exact version, developers can focus their testing and debugging efforts on the specific environment where the problem is reported. This targeted approach increases the efficiency of the debugging process and ensures that the fix is tailored to the user's system configuration. Accurate OS information is therefore a critical component of any bug report, providing valuable context for developers to diagnose and resolve the issue effectively.

Log Content

2025-08-27 23:39:17 INFO - try to delete log files, day: 7
2025-08-27 23:39:17 INFO - [Config] clash_core配置验证通过: Some("verge-mihomo")
2025-08-27 23:39:17 INFO - [Setup] 初始化资源...
2025-08-27 23:39:17 INFO - [Setup] 核心组件初始化完成
2025-08-27 23:39:17 INFO - [Setup] 初始化完成，继续执行
2025-08-27 23:39:17 INFO - [System] 应用就绪或恢复
2025-08-27 23:39:17 INFO - [Config] 开始初始化配置... 线程ID: ThreadId(9)
2025-08-27 23:39:18 INFO - [Config] 生成运行时配置成功
2025-08-27 23:39:18 INFO - [Config] 开始验证配置
2025-08-27 23:39:18 INFO - [Config] 生成临时配置文件用于验证
2025-08-27 23:39:18 INFO - [Config] 开始验证配置文件: C:\Users\joons.DESKTOP-DP54NF0\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\clash-verge-check.yaml
2025-08-27 23:39:18 INFO - [Config] 使用内核: verge-mihomo
2025-08-27 23:39:18 INFO - [Config] 验证目录: C:\Users\joons.DESKTOP-DP54NF0\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev
2025-08-27 23:39:18 INFO - [Config] -------- 验证结果 --------
2025-08-27 23:39:18 INFO - [Config] 验证成功
2025-08-27 23:39:18 INFO - [Config] -------- 验证结束 --------
2025-08-27 23:39:18 INFO - [Config] 配置验证成功
2025-08-27 23:39:18 INFO - [Config] 配置初始化完成
2025-08-27 23:39:18 INFO - [Setup] 开始清理冗余的Profile文件...
2025-08-27 23:39:18 INFO - Profile 文件清理完成: 总文件数=8, 删除文件数=0, 失败数=0
2025-08-27 23:39:18 INFO - [Setup] 启动时Profile文件清理完成
2025-08-27 23:39:18 INFO - [Core] 开始清理多余的 mihomo 进程
2025-08-27 23:39:18 INFO - [Service] 开始检查服务是否正在运行
2025-08-27 23:39:18 INFO - [Service] 开始检查服务状态 (IPC)
2025-08-27 23:39:18 INFO - [Service] 正在连接服务 (Windows)...
2025-08-27 23:39:18 ERROR - [Service] 连接到服务命名管道失败: 系统找不到指定的文件。 (os error 2)
2025-08-27 23:39:18 ERROR - [Service] IPC通信失败: 无法连接到服务命名管道: 系统找不到指定的文件。 (os error 2)
2025-08-27 23:39:18 ERROR - [Service] 检查服务运行状态失败: 无法连接到Clash Verge Service: 无法连接到服务命名管道: 系统找不到指定的文件。 (os error 2)
2025-08-27 23:39:18 INFO - [Core] 服务初始不可用 (is_service_available 调用失败)
2025-08-27 23:39:18 INFO - [Core] 核心未通过服务模式启动，执行Sidecar回退或首次安装逻辑
2025-08-27 23:39:18 INFO - [Core] 用户偏好Sidecar模式或先前服务启动失败，使用Sidecar模式启动
2025-08-27 23:39:18 INFO - [Tray] 创建系统托盘...
2025-08-27 23:39:18 INFO - 正在从AppHandle创建系统托盘
2025-08-27 23:39:18 INFO - 系统托盘创建成功
2025-08-27 23:39:18 INFO - [Tray] 系统托盘创建成功
2025-08-27 23:39:18 INFO - 已启用事件驱动代理守卫
2025-08-27 23:39:18 INFO - [Window] 开始创建/显示主窗口, is_show=false
2025-08-27 23:39:18 INFO - [Window] 静默模式启动时不创建窗口
2025-08-27 23:39:18 INFO - [Lightweight] 轻量模式已开启
2025-08-27 23:39:18 INFO - [Timer] Initializing timer...
2025-08-27 23:39:18 INFO - [Timer] Refreshing 1 timer tasks
2025-08-27 23:39:18 INFO - [Timer] Adding task: uid=RODZaA6OCkEa, id=1, interval=1440min
2025-08-27 23:39:18 INFO - [Timer] 已注册的定时任务数量: 1
2025-08-27 23:39:18 INFO - [Timer] 注册了定时任务 - uid=RODZaA6OCkEa, interval=1440min, task_id=1
2025-08-27 23:39:18 INFO - [Timer] Timer initialization completed
2025-08-27 23:39:18 INFO - [Setup] Hotkey initialized
2025-08-27 23:39:18 INFO - [Setup] 异步设置任务完成，耗时: 813.1436ms
2025-08-27 23:39:18 INFO - [Setup] 应用设置成功完成
2025-08-27 23:39:18 INFO - 事件驱动代理管理器启动
2025-08-27 23:39:18 INFO - 初始化代理状态
2025-08-27 23:39:18 INFO - 代理状态初始化完成: sys=false, pac=false
2025-08-27 23:39:20 INFO - [Frontend] 启动过程中发现错误，加入消息队列: config_validate::success - 
2025-08-27 23:42:56 INFO - Tray点击事件: 显示主窗口
2025-08-27 23:42:56 INFO - 当前在轻量模式，正在退出轻量模式
2025-08-27 23:42:56 INFO - [Lightweight] 轻量模式已关闭
2025-08-27 23:42:56 INFO - [Window] UI就绪状态已重置
2025-08-27 23:42:56 INFO - [防抖] 窗口操作被允许执行
2025-08-27 23:42:56 INFO - [Window] 开始智能显示主窗口
2025-08-27 23:42:56 INFO - [Window] 窗口不存在，创建新窗口
2025-08-27 23:42:56 INFO - [Window] 开始创建/显示主窗口, is_show=true
2025-08-27 23:42:56 INFO - [Window] 窗口创建成功
2025-08-27 23:42:56 INFO - [Frontend] 发送1条启动时累积的错误消息
2025-08-27 23:42:56 INFO - [Window] 窗口已立即显示
2025-08-27 23:42:56 INFO - [Window] 开始监控UI加载状态 (最多8秒)...
2025-08-27 23:42:56 INFO - [Window] 窗口显示流程完成
2025-08-27 23:42:56 INFO - 窗口显示结果: Created
2025-08-27 23:42:57 INFO - [Setup] IpcManager initialized
2025-08-27 23:42:57 INFO - [Cmd] 快速获取配置列表成功
2025-08-27 23:42:57 INFO - [Setup] TrafficMonitor initialized
2025-08-27 23:42:57 INFO - [Setup] MemoryMonitor initialized
2025-08-27 23:42:57 INFO - [IPC] IPC流式监控已激活
2025-08-27 23:42:57 INFO - UI加载阶段更新: Loading
2025-08-27 23:42:57 INFO - UI加载阶段更新: Loading
2025-08-27 23:42:57 INFO - UI加载阶段更新: DomReady
2025-08-27 23:42:57 INFO - UI加载阶段更新: ResourcesLoaded
2025-08-27 23:42:57 INFO - 前端UI已准备就绪
2025-08-27 23:42:57 INFO - [Window] UI已标记为完全就绪
2025-08-27 23:42:57 INFO - [Window] UI已完全加载就绪
2025-08-27 23:46:03 INFO - [Window] 开始创建/显示主窗口, is_show=false
2025-08-27 23:46:03 INFO - [Window] 静默模式启动时不创建窗口
2025-08-27 23:46:03 INFO - [Lightweight] 轻量模式已开启
2025-08-27 23:46:09 INFO - [Window] 开始创建/显示主窗口, is_show=false
2025-08-27 23:46:09 INFO - [Window] 静默模式启动时不创建窗口
2025-08-27 23:46:09 INFO - [Lightweight] 轻量模式已开启

Analyzing the log content can provide valuable insights into the application's behavior and potential causes of the bug. The log shows a sequence of events, including configuration validation, resource initialization, and service checks. Key points to note from the log include:

1. Configuration Validation: The log indicates that the Clash core configuration was validated successfully. This suggests that the basic configuration settings are correct and not the source of the problem.
2. Service Connection Errors: Several errors related to service connection failures are present. Specifically, the log shows that the application failed to connect to the service named pipe, with the error message "System cannot find the specified file." This error suggests that there might be an issue with the service component of the application or its ability to communicate with other parts of the system. This could be due to permission issues, incorrect installation, or missing dependencies.
3. Sidecar Mode: The log indicates that the application fell back to using Sidecar mode because the service mode failed to start. Sidecar mode is an alternative way of running the application, but it might not provide the same level of isolation or functionality as the service mode. This fallback could be related to the multi-user issue, as Sidecar mode might not be properly configured to handle multiple user sessions.
4. UI Readiness: The log shows that the UI was initialized and marked as fully ready. This suggests that the user interface components of the application are functioning correctly, but the underlying service or core logic might be failing.

By examining these log entries, developers can gain a better understanding of where the application is failing and what components might be involved. The service connection errors, in particular, point to a potential issue with the application's service component or its interaction with the operating system, which could be the root cause of the multi-user problem. Further investigation into the service setup and configuration is warranted to resolve this issue.

In summary, the user has encountered a significant issue with Clash Verge Rev in a multi-user Windows 10 environment. The application fails to launch for subsequent users if one user has already started it. The provided logs indicate potential problems with service connections and a fallback to Sidecar mode. Further investigation and debugging are needed to resolve this bug and ensure that the application functions correctly in multi-user scenarios.