How to Set Up Proxy for Multiple Telegram P2P Windows

Setting Up Proxying for Multiple Telegram P2P Windows with Different Proxy Servers

To configure proxying for multiple Telegram P2P windows with different proxy servers, it’s necessary to solve the msedgewebview2.exe process isolation problem, which prevents binding a separate proxy to each instance. There are several approaches to achieving full isolation between accounts.

Table of Contents

• Main Methods for Solving the Isolation Problem
• Using Portable Versions of Telegram with Separate TData
• Setting Up WebView2 Process Isolation
• Proxy Solutions with Virtual Machines
• Tools for Automating Isolation
• Practical Implementation
• Performance Optimization

Main Methods for Solving the Isolation Problem

The problem is that all instances of Telegram Desktop use the same msedgewebview2.exe process, which results in the same proxy being detected for all P2P platforms. To solve this problem, it’s necessary to ensure complete isolation of each instance.

According to research, there are several approaches:

• Running separate instances with unique TData folders
• Using isolated environments for each account
• Setting up different proxies at the operating system level
• Virtualization for maximum isolation

Important: As noted in the sources, for maximum account separation, virtual machines should be used, providing the highest level of isolation.

Using Portable Versions of Telegram with Separate TData

The portable version of Telegram allows running multiple instances with isolated data. To do this:

1. Create separate folders for each account:

   Telegram_Account1\
   Telegram_Account2\
   Telegram_Account3\
   

2. Copy the portable version of Telegram into each folder

3. For each instance, configure individual proxies through system settings or Proxifier

Research shows that this method allows running multiple independent Telegram instances, but the problem with the shared msedgewebview2.exe process remains.

Setting Up WebView2 Process Isolation

The msedgewebview2.exe process is a component of Microsoft Edge WebView2 that uses a site-isolated process model. To solve the isolation problem:

1. Separation of user data: Each Telegram instance should correspond to a separate WebView2 user data store

2. Startup parameter configuration: Use isolation flags when launching:

   --user-data-dir="C:\path\to\unique\data\folder"
   --disable-web-security
   --disable-features=IsolateOrigins,site-per-process
   

3. Process isolation: According to Microsoft documentation, WebView2 uses a multi-process model for improved reliability, security, and performance

Research shows that when running multiple WebView2 instances with different user data folders, processes should be isolated, but in practice, this doesn’t always work correctly.

Proxy Solutions with Virtual Machines

The most reliable solution is to use virtual machines for each account:

1. VM Setup: Create a separate virtual machine for each Telegram account

2. Network Isolation: Configure a different proxy server for each VM

3. Hardware Acceleration: Use GPU virtualization for improved performance

4. Automation: Set up automatic startup and management of VMs

As noted in research, virtual machines provide the highest level of isolation and allow Telegram to avoid detecting that it’s running under the same proxy.

Tools for Automating Isolation

To automate the isolation process, you can use the following tools:

1. Batch scripts with process isolation

@echo off
setlocal

:: Launch first instance with proxy 1
start "" "Telegram1\Telegram.exe" --msedge-path="Telegram1\msedgewebview2.exe" --user-data-dir="Telegram1\userdata"

:: Launch second instance with proxy 2
start "" "Telegram2\Telegram.exe" --msedge-path="Telegram2\msedgewebview2.exe" --user-data-dir="Telegram2\userdata"

endlocal

2. Proxy managers

• Proxifier: Configure routing rules for each instance
• ProxyCap: Create separate tunnels for each process
• Clash for Windows: Use multi-port mode for isolation

3. Containers and sandboxes

• Docker: Run each instance in a separate container
• Sandboxie: Isolate each process in a sandbox

Practical Implementation

Here’s a step-by-step guide for setting up isolated instances:

1. Environment Preparation:

   • Install the portable version of Telegram
   • Create a folder structure for each account
   • Set up proxy servers for each instance

2. Launch Configuration:

   batch

   @echo off
   REM Telegram Account 1
   start "" "Telegram1\Telegram.exe" --user-data-dir="Telegram1\userdata" --msedge-path="Telegram1\msedgewebview2.exe"
   
   REM Telegram Account 2
   start "" "Telegram2\Telegram.exe" --user-data-dir="Telegram2\userdata" --msedge-path="Telegram2\msedgewebview2.exe"
   

3. Proxy Configuration:

   • For each instance, configure a separate proxy in Proxifier
   • Use different ports for each process

4. Isolation Verification:

   • Launch Task Manager and check for separate msedgewebview2.exe processes
   • Ensure each process is using its own proxy

Performance Optimization

To optimize the operation of multiple instances:

1. Resource Management:

   • Limit the number of simultaneous instances
   • Configure process priorities
   • Use SSD disk space for faster operation

2. Monitoring:

   • Use Process Hacker to monitor process isolation
   • Set up alerts when shared resources are detected

3. Automatic Recovery:

   • Set up restarting of frozen instances
   • Use scripts to automatically verify isolation

Conclusion

To set up proxying for multiple Telegram P2P windows with different proxy servers, it’s necessary to:

1. Use portable versions of Telegram with completely isolated TData folders for each account
2. Configure separate msedgewebview2.exe instances with different paths to executable files
3. Apply system proxy managers to route traffic for each instance through a separate proxy
4. For maximum isolation, it’s recommended to use virtual machines
5. Automate the launch and monitoring process to ensure stable operation

The key factor for success is the complete separation of msedgewebview2.exe processes between accounts, which allows Telegram to avoid detecting that it’s running under the same proxy and ensures independent operation of each P2P platform.

Sources

1. How to Run Multiple Telegram Accounts on One Device: A Step-by-Step Guide
2. Process model for WebView2 apps - Microsoft Edge Developer documentation
3. WebView2 end-user FAQ - Microsoft Edge Developer documentation
4. Multiple WebView2 instances of different processes that share user data folders cannot run at the same time!
5. Multiple instances of “Microsoft Edge WebView2” constantly running while MailWasher is in the background
6. msedgewebview2.exe Windows process - What is it?
7. How can I run multiple instances of Telegram? - Ask Ubuntu
8. Multiple instances · Issue #533 · telegramdesktop/tdesktop